Which versions of @asyncapi/generator-helpers are malicious?

The following npm versions of @asyncapi/generator-helpers are flagged malicious: 0.2.1, 0.2.2. Treat any of these as compromised.

How do I remediate @asyncapi/generator-helpers if I installed it?

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

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

Yes — @asyncapi/generator-helpers is associated with the GHSA-gw3q-hxvp-x7vm 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/generator-helpers 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/generator-helpers (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/generator-helpers across your stack and pipelines.

Malicious package

@asyncapi/generator-helpersnpm

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

MAL-2025-190657

Immediate action

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

npm uninstall @asyncapi/generator-helpers

What this malware does

The package @asyncapi/generator-helpers 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.2.10.2.2

Indicators of compromise (SHA-256)

6c55b498d8766225c87bc5781438ffe36f84333b8bb731069bb0bac726cb6b3e

1fb4a795f9e4f1dc8304d727b4b4a4b6d4024952675eb497e79b9f78fa2b96ca

f8004b054d45a6f08280a93c7be997f099739cdc3a8311a35d9976efd619b1c4

eaf9598bd0d64189828293050c590d3885311537cef7b91153a0df8cef9489f4

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

Campaign

GHSA-gw3q-hxvp-x7vm

References

Credits

Amazon Inspector · finder

Detect & block this

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