Which versions of @asyncapi/specs are malicious?

The following npm versions of @asyncapi/specs are flagged malicious: 6.8.2, 6.8.3, 6.9.1, 6.10.1. Treat any of these as compromised.

How do I remediate @asyncapi/specs if I installed it?

@asyncapi/specs is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @asyncapi/specs — how do I know if it already compromised me?

If @asyncapi/specs was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @asyncapi/specs part of a known attack campaign?

Yes — @asyncapi/specs is associated with the GHSA-5jj9-3vg7-7785 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @asyncapi/specs across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @asyncapi/specs (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @asyncapi/specs across your stack and pipelines.

Malicious package

@asyncapi/specsnpm

Malicious code in @asyncapi/specs (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190643

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @asyncapi/specs

What this malware does

The package @asyncapi/specs was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

4 flagged

6.8.26.8.36.9.16.10.1

Indicators of compromise (SHA-256)

5715faf8c80acf7c963aac8c332a2cffed06a23ca9663a2fdcb6fd11be4325e9

46e1904e729f9b51f22f0c24624af6ce0bfa9e7a02a0968c15469cd5ba665c2f

a7b05e7569027761c2ee32b0fa3f8d78a0246e62d32cb441512e6ef080bd4f7a

938ab70c817e26ed594a554747f21aa339e5a01f3daf999dead6c94fd2289490

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @asyncapi/specs (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @asyncapi/specs across your stack and pipelines.
If you installed it — respond
@asyncapi/specs is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @asyncapi/specs was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @asyncapi/specs before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @asyncapi/specs on npm has been identified as a malicious package (versions 6.8.2, 6.8.3, 6.9.1, 6.10.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-5jj9-3vg7-7785

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @asyncapi/specs-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring