UTC

Shai-Hulud npm worm (2025)

A self-spreading npm worm that stole publishing tokens and released infected versions of the victims' packages, in September 2025 and again in November 2025 ("The Second Coming"). The second wave hit MCP servers and AI SDKs from Postman, Zapier, Browserbase, PostHog, mcp-use and Voiceflow, among hundreds of other packages.

First seen
2025-09-15
Disclosed
2025-09-15
Affected packages
19
Attributed to
No public attribution

What to do

Check lockfiles and caches for the versions listed and reinstall clean ones. On any machine or runner that installed one, rotate npm, GitHub and cloud tokens and look for public repositories and workflows you did not create. CISA's alert of 2025-09-23 lists further steps.

Check a lockfile for these releases →
Affected releases
PackageRegistryVersions
@postman/postman-mcp-servernpm2.4.10, 2.4.11, 2.4.12
@postman/postman-mcp-clinpm1.0.3, 1.0.4, 1.0.5
@zapier/mcp-integrationnpm3.0.1, 3.0.2, 3.0.3
@zapier/ai-actionsnpm0.1.18, 0.1.19, 0.1.20
@browserbasehq/mcpnpm2.1.1
@browserbasehq/mcp-server-browserbasenpm2.4.2
@browserbasehq/stagehandnpm3.0.4
@posthog/ainpm7.1.2
@posthog/agentnpm1.24.1
mcp-usenpm1.4.2, 1.4.3
@mcp-use/clinpm2.2.6, 2.2.7
@mcp-use/inspectornpm0.6.2, 0.6.3
@mcp-use/mcp-usenpm1.0.1, 1.0.2
create-mcp-use-appnpm0.5.3, 0.5.4
@relyt/claude-context-mcpnpm0.1.1
@seezo/sdr-mcp-servernpm0.0.5
web-scraper-mcpnpm1.1.4
@voiceflow/anthropicnpm0.4.4, 0.4.5
@voiceflow/openainpm3.2.2, 3.2.3

Written up from the sources above and last checked on 2026-11-18. ShieldMap describes what was affected and what to do; it does not publish the malicious code or how it worked. Report a correction to [email protected].