Which versions of @asyncapi/multi-parser are malicious?

The following npm versions of @asyncapi/multi-parser are flagged malicious: 2.2.1, 2.2.2. Treat any of these as compromised.

How do I remediate @asyncapi/multi-parser if I installed it?

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

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

Yes — @asyncapi/multi-parser is associated with the GHSA-63gg-qx3x-ph2j 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/multi-parser 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/multi-parser (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/multi-parser across your stack and pipelines.

Malicious package

@asyncapi/multi-parsernpm

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

MAL-2025-190661

Immediate action

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

npm uninstall @asyncapi/multi-parser

What this malware does

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

2.2.12.2.2

Indicators of compromise (SHA-256)

1bb5e990919cec43b91093e354ec31175f405dc1b2be344636e93137b5e4c297

8fca41600409d9446c4771677d000e0c23cb7f5a5d876cff66c762472d477bae

ae28d5a7633b326134b02c30980d93357f9b58e3143b0e83751e6369441a3034

b89b6d1bed8d33da0e2dd68217cdf7cb6b131b2e5d65bb4cce8b7af1389b6796

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

Campaign

GHSA-63gg-qx3x-ph2j

References

Credits

Amazon Inspector · finder

Detect & block this

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