Categories: Website

Phishing attacks with new domains likely to continue

Unfortunately the string of phishing attacks using domain-confusionand legitimate-looking emails continues. This is the same attack PyPI saw a few months agoand targeting many other open source repositoriesbut with a different domain name. Judging from this, we believe this type of campaign will continuewith new domains in the future.

In short, there’s a new phishing campaigntargeting PyPI users occurring right now. The email asks you to “verify their email address”for “account maintenance and security procedures” with a note that your account may be suspended.This email is fake, and the link goes to pypi-mirror.org

Sponsored
which is a domain not owned by PyPI or the PSF.

If you have already clicked on the link and provided your credentials, we recommend changing yourpassword on PyPI immediately. Inspect your account’s Security History for anything unexpected.Report suspicious activity, such as potential phishing campaigns against PyPI, to security@pypi.org.

Sponsored
Sponsored

What is PyPI doing to protect users?

There’s no quick-and-easy method for PyPI maintainers to completelyhalt this sort of attack short of requiring phishing-resistant 2FA (such as hardware tokens).Below are the following steps we’re taking to keep users safe:

  • Contacting the registrars and CDN of the malicious domains to have them taken down.
  • Submitting phishing domains to lists of known-malicious URLs. This makes browsers show a warning before visiting the website, hopefully triggering alarm bells for users.
  • Collaborating with other open source package managers to share strategies for quicker domain take-downs.
  • Exploring methods to make authenticating using TOTP-based 2FA more resistant to phishing.

What can you do as a maintainer?

If you are a maintainer of a package on PyPI, you can help protect your users by adopting the following practices:

  • Don’t trust or click on links in emails that you didn’t trigger yourself.
  • Use a password manager that auto-fills based on domain name and exclusively using this feature. If auto-fill isn’t working when it usually does, that is a warning sign!
  • Adopt a phishing-resistant 2FA method such as hardware keys.
  • When in doubt, ask for help before taking action. There is no shame in being cautious, share fishy-looking emails with others.
  • Share this warning within your own communities. PyPI is not the first or last open source service that will be targeted with phishing attacks.
cmsguru

Recent Posts

PyPI in 2025: A Year in Review

As 2025 comes to a close, it's time to look back at another busy year…

4 days ago

Y25 Cycle 6 Engineering Progress Report

Providing insight into our product roadmap and, subsequently, the projects being worked on in our…

2 weeks ago

Development Cycle Six

Providing insight into our product roadmap and, subsequently, the projects being worked on in our…

3 weeks ago

Independent Collectives are becoming Organizations

TL;DR: Independent Collectives are being converted to Organizations to make the platform more consistent. There…

3 weeks ago

PyPI and Shai-Hulud: Staying Secure Amid Emerging Threats

An attack on the npm ecosystem continues to evolve, exploiting compromised accounts to publish malicious…

1 month ago

New Login Verification for TOTP-based Logins

We've implemented a new security feature designed to protect PyPI users from phishing attacks: email…

2 months ago

This website uses cookies.