Shai-Hulud 2.0
Named by 13 kept items in this workspace.
7 items name it under threat actors and 6 under classification.key entities.
Search every workspace for Shai-Hulud 2.0. It matches the name as written, so it can find other things that share it.
The items that name it 13
November 2025 return of the Shai-Hulud worm with refined tactics, compromising packages by major publishers including Postman, Posthog, Zapier, and others.
Campaign on Nov 23, 2025; used a Pwn Request against the asyncapi/cli repository to exfiltrate a CI token in under three minutes, then deployed the worm via a malicious OpenVSX extension, spreading to 25,000+ malicious repositories. Microsoft published guidance Dec 9. Attacker renamed GitHub account
Referenced as a 2025 incident that affected the same AsyncAPI team ('they got done in Shai Hulud 2.0 in 2025'), no confirmed relation to the new AsyncAPI compromise
Previous compromise of @asyncapi namespace; this new attack does not appear directly connected to it.
Worm wave whose first-blood event was the AsyncAPI compromise in November 2025; used stolen npm and OpenVSX publishing tokens to push malicious AsyncAPI npm packages and a malicious version of the AsyncAPI VS Code extension on OpenVSX.
Supply chain attack that compromised the npm ecosystem on November 24, 2025; installs setup_bun.js/bun_environment.js payloads via preinstall/postinstall hooks, steals credentials with TruffleHog, exfiltrates to attacker-controlled GitHub repos, self-propagates to up to 100 additional npm packages,
All threat actors in this workspace.