Which versions of @asyncapi/bundler are malicious?

The following npm versions of @asyncapi/bundler are flagged malicious: 0.6.5, 0.6.6. Treat any of these as compromised.

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

@asyncapi/bundler 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/bundler — how do I know if it already compromised me?

If @asyncapi/bundler 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/bundler part of a known attack campaign?

Yes — @asyncapi/bundler is associated with the GHSA-g63r-6vp8-gm3j 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/bundler 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/bundler (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @asyncapi/bundler across your stack and pipelines.

Malicious package

@asyncapi/bundlernpm

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

MAL-2025-190652

Immediate action

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

npm uninstall @asyncapi/bundler

What this malware does

The package @asyncapi/bundler 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

2 flagged

0.6.50.6.6

Indicators of compromise (SHA-256)

47d31b4cc36ee8c342471c6a61cc7ad42816f99ba2aa4bc825f7fc26c3b4e119

4772ec7022abe0375835d594a76a518350868bfe4630f4cf472962d4e6bdf2a9

a26a936e53bec6e0462445fb1b1e3c83b6052aab511256becf2f7e6d60906b15

e3e1c10e3b399564fe699536e207576f1afa6e52cef7b72ab40e34ca31896abf

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/bundler (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @asyncapi/bundler across your stack and pipelines.
If you installed it — respond
@asyncapi/bundler 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/bundler 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/bundler 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/bundler on npm has been identified as a malicious package (versions 0.6.5, 0.6.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-g63r-6vp8-gm3j

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @asyncapi/bundler-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