Criticalnpm2 affected versions

@asyncapi/specs

@asyncapi/specs has 2 versions on the npm registry flagged in 1 incident we track. Other versions of this package are not implicated - only the exact versions listed below were named by the source advisories.

Affected versions

Check what you actually have installed with npm ls @asyncapi/specs.

@asyncapi/specs@6.11.2-alpha.1
@asyncapi/specs@6.11.2

The incident that flagged it

Critical14 Jul 2026

AsyncAPI npm org compromised - 4 packages / 5 versions ship Miasma botnet loader via GitHub Actions `pull_request_target` pwn request

On 2026-07-14 an attacker exploited a pull_request_target misconfiguration in asyncapi/generator to steal a highly-privileged GitHub PAT, then published five malicious @asyncapi/* releases through the project's own trusted GitHub Actions release pipeline - valid npm OIDC provenance and all. The payload fires on require(), spawns a detached Node process, fetches an 8.25 MB IPFS loader (Miasma), and installs a 3.09 MB implant with six independent C2 channels (HTTP, Nostr, IPFS, BitTorrent DHT, libp2p GossipSub, Ethereum smart contract). Combined weekly downloads: ~2.9M.

Versions named here: 6.11.2-alpha.1, 6.11.2

What to do if you installed one of these

Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
2.Pin to a version not listed above, then reinstall from a clean lockfile.
3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
4.Read the incident write-up above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.

Check your whole project

@asyncapi/specs is one of many packages in these incidents, and it is usually pulled in as a transitive dependency rather than one you installed directly. Paste your package-lock.json to check every dependency at once - it runs in your browser and nothing is uploaded.

Check my package-lock.json All flagged npm packages

Other packages in the same incident

If @asyncapi/specs is in your tree, these are worth checking too - they were published by the same campaign.

See the full incident

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.