Which versions of @asyncapi/converter are malicious?

The following npm versions of @asyncapi/converter are flagged malicious: 1.6.3, 1.6.4. Treat any of these as compromised.

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

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

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

Yes — @asyncapi/converter is associated with the GHSA-3cr2-p3pg-xrhw 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/converter 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/converter (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/converter across your stack and pipelines.

Malicious package

@asyncapi/converternpm

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

MAL-2025-190654

Immediate action

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

npm uninstall @asyncapi/converter

What this malware does

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

1.6.31.6.4

Indicators of compromise (SHA-256)

b79b4d90792c3a8df5926407a70010c63bbc18c2551dcfa03a10b7700e3ecb85

391d5e53843731fb634a2f3811928f21e466b64aa48d1383b08f7f3708f603db

17a5cbea7fea784aad3933cba1d2a82a3a4283844747200bb4bb774f657e929a

c1e7e3aa9cb6b9c38379f160c782d961c62e74217466366dd4107163009c472f

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

Campaign

GHSA-3cr2-p3pg-xrhw

References

Credits

Amazon Inspector · finder

Detect & block this

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