Which versions of @asyncapi/problem are malicious?

The following npm versions of @asyncapi/problem are flagged malicious: 1.0.1, 1.0.2. Treat any of these as compromised.

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

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

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

Yes — @asyncapi/problem is associated with the GHSA-2rp9-v657-8w4r 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/problem 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/problem (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/problem across your stack and pipelines.

Malicious package

@asyncapi/problemnpm

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

MAL-2025-190664

Immediate action

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

npm uninstall @asyncapi/problem

What this malware does

The package @asyncapi/problem 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.0.11.0.2

Indicators of compromise (SHA-256)

1bd2a5ae5e63884d80bffd3195c99c9e9c2a1977eedac025fef767fe8abd4251

257141d8551fbc781c4df287d30e9a7e795f6759382d0ca3c20f7c46411614ec

a4369c29cfe48966fe3e06ad19de1b717f0d6c325b369e38ee5ecc889fcc74e0

0b55e834fe97dbfc24ac1be9370381c94a386f3237c4641cdb57dfcb9f2f399e

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

Campaign

GHSA-2rp9-v657-8w4r

References

Credits

Amazon Inspector · finder

Detect & block this

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