Post #2093717

2025-11-26 21:02 UTC

There&#39;s a nasty #OpenSource #SupplyChain worm going around named Shai-Hulud. It&#39;s also capable of exposing some projects&#39; long-lived PyPI API Tokens. Read more on what&#39;s happening, and what you can do to protect your projects. TL,DR: Adopt Trusted Publishing 🔐🚀📦 https://blog.pypi.org/posts/2025-11-26-pypi-and-shai-hulud/

Replies (3)

@kaleissin@wandering.shop 2025-11-26 21:11

@miketheman@hachyderm.io .. or you could *not* trust a third party to publish to PyPI for you.

Open ##2869144
@verbrecher@mastodon.social 2025-11-26 22:22

@claushoumann@mastodon.social , in case if this new malware strain fails to exfiltrate data or authenticate it attempts to wipe user’s home directory ! (Windows & Linux) ⚠️ aka Should be a real asshole : dead man’s switch. Somehow nasty and revengeful. Credential Harvest: Aggressively scrapes AWS, GCP, Azure, npm, and GitHub tokens. Self-Propagation: Uses stolen npm tokens to instantly republish malicious versions of packages Devs maintain.

Open ##2869146
@silmathoron@floss.social 2025-11-27 23:31

@miketheman@hachyderm.io it's not clear to me how trusted publishing helps in the case of something like Shai-Hulud: if your repo is corrupted, the corrupted package will be pushed to PyPi via the CI and propagated anyway, isn't it?

Open ##2869148