Which versions of @asyncapi/optimizer are malicious?

The following npm versions of @asyncapi/optimizer are flagged malicious: 1.0.5, 1.0.6. Treat any of these as compromised.

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

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

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

Yes — @asyncapi/optimizer is associated with the GHSA-xgcr-6c5m-pmwv 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/optimizer 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/optimizer (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/optimizer across your stack and pipelines.

Malicious package

@asyncapi/optimizernpm

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

MAL-2025-190663

Immediate action

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

npm uninstall @asyncapi/optimizer

What this malware does

The package @asyncapi/optimizer 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.51.0.6

Indicators of compromise (SHA-256)

8de2e980105b98ca3c0a508059dddff106593a8bc4d9298dec6075041452240a

886928a124b656faf40d1490a3b484cf0aa717d98fa9f5cd6de025e1874183e5

cec7029abdb9f604cf1436d05886eeb359685cdfcb795d2479e4631673bcddf0

9007469bef60ae80363b8649b4ec69214926dba62a3a05f7641d2ac8a6005fcb

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

Campaign

GHSA-xgcr-6c5m-pmwv

References

Credits

Amazon Inspector · finder

Detect & block this

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