Which versions of @asyncapi/diff are malicious?

The following npm versions of @asyncapi/diff are flagged malicious: 0.5.1, 0.5.2. Treat any of these as compromised.

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

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

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

Yes — @asyncapi/diff is associated with the GHSA-hc6m-f55c-m5w8 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/diff 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/diff (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/diff across your stack and pipelines.

Malicious package

@asyncapi/diffnpm

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

MAL-2025-190655

Immediate action

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

npm uninstall @asyncapi/diff

What this malware does

The package @asyncapi/diff 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.5.10.5.2

Indicators of compromise (SHA-256)

dfe913f8a298c7c2e8e2e4708025a868cba9d567779195881f90ba52bdc8d14c

afa55a72fa4b01b54926fbef60ac9ac0ece6a9128ddbdd3d883aa6ee7bb8c67c

1ea4f19b7572905e834b0ab7da5582b24ebb142327a62006d042f1f9b094a575

b6e16f69fbb5d82c90984f2191a0d19f532d0eb6d95e12d063d1b4a8987efd0d

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

Campaign

GHSA-hc6m-f55c-m5w8

References

Credits

Amazon Inspector · finder

Detect & block this

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