Which versions of @asyncapi/keeper are malicious?

The following npm versions of @asyncapi/keeper are flagged malicious: 0.0.2, 0.0.3. Treat any of these as compromised.

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

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

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

Yes — @asyncapi/keeper is associated with the GHSA-7pwg-fhvr-6h6v 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/keeper 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/keeper (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/keeper across your stack and pipelines.

Malicious package

@asyncapi/keepernpm

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

MAL-2025-190799

Immediate action

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

npm uninstall @asyncapi/keeper

What this malware does

The package @asyncapi/keeper 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.0.20.0.3

Indicators of compromise (SHA-256)

b4de90c140688e48a7bd263f6ce83227887405e7322154faa001d6bdf787cd2d

04b1620523a3ce8e3a6d91cc4b532723797a0cc56a36e303774caf14ef1acffd

109d76b8da376b2f93a35f7d4de8ae6f26cd0ad766337c4e4c204806ab279582

5828ec3e2bc7db603282e6dd6c3771d5ddb5cae64ee9ec17cf748a9efedc12fa

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/keeper (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/keeper across your stack and pipelines.
If you installed it — respond
@asyncapi/keeper 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/keeper 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/keeper 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/keeper on npm has been identified as a malicious package (versions 0.0.2, 0.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-7pwg-fhvr-6h6v

References

Credits

Amazon Inspector · finder

Detect & block this

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