Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@asyncapi/generator-helpersnpm

@asyncapi/generator-helpers is a confirmed malicious npm package (MAL-2025-190657) that steals credentials and exfiltrates sensitive data (malicious versions 0.2.1, 0.2.2, 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @asyncapi/generator-helpers (npm)

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

@asyncapi/generator-helpers version 1.1.1 was published as part of the "Miasma RAT" software supply-chain attack (campaign identifier "miasma-train-p1") that compromised several widely used @asyncapi npm packages on 2026-07-14. The malicious code was injected using whitespace hiding: it is appended to a legitimate source file after hundreds of trailing spaces on the file's final line, so it is not visible in a casual diff. When the package is installed, the injected code spawns a child process that downloads the Miasma RAT binary from IPFS (https://ipfs.io/ipfs/QmQobZSp1wRPrpSEQ56qnyq7ecZh5Bg5k1fnjt4SUwwHb9), writes it to a platform-specific drop location, and executes it. Persistence is established by dropping a backdoor named sync.js (~/.local/share/NodeJS/sync.js on Linux, ~/Library/Application Support/NodeJS/sync.js on macOS, %LOCALAPPDATA%\NodeJS\sync.js on Windows). The Miasma RAT harvests browser credentials, SSH keys, npm tokens, GitHub CLI credentials, AWS secrets, and cryptocurrency wallets, and communicates with a command-and-control server at 85.137.53.71 (AS43641, Netherlands). The attacker also embedded an Ethereum smart-contract address (0x12c37A86a0Ed0beBe5d1d6a43E42f07860eAc710), suggesting on-chain command routing or exfiltration. The last known safe version is 1.1.0.

src/utils.js — reached via the package main src/index.js — contains an obfuscator.io IIFE that runs at module load. Alongside the legitimate helpers (getInfo, getTitle, toSnakeCase, toCamelCase), the file ships a rotated string array (_0x2d89), a custom lowercase-first base64 decoder (_0x1dd2), and a ~4KB opaque literal that decodes at runtime to further JavaScript. The top-level main() then invokes child_process.spawn on the Node runtime with '-e' and the decoded string, using {detached: true, stdio: 'ignore', windowsHide: true} so the child process is disowned and hidden. Because this fires unconditionally on require('@asyncapi/generator-helpers'), any consumer or generator template that loads this version executes attacker-controlled JavaScript in a detached Node process on the host. The behavior — obfuscator.io string-array plus custom-base64 blob reconstructed into node -e arguments — is not consistent with the package's documented purpose as an AsyncAPI generator helper library and matches a trojanized-release supply-chain compromise.

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

3 flagged
0.2.10.2.21.1.1

Indicators of compromise (SHA-256)

6c55b498d8766225c87bc5781438ffe36f84333b8bb731069bb0bac726cb6b3e
1fb4a795f9e4f1dc8304d727b4b4a4b6d4024952675eb497e79b9f78fa2b96ca
f8004b054d45a6f08280a93c7be997f099739cdc3a8311a35d9976efd619b1c4
eaf9598bd0d64189828293050c590d3885311537cef7b91153a0df8cef9489f4
a9a130715f7eec3592c53d27ff4aba0f3ecb2e88f5e4276c9906981bc94df1b0
f5d32214c0ccb2ee8f88d55a002ca8bd58405c001051f75646cb765588ccfa9c

Detection & response playbook

Credential / info stealer
  1. 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 (3 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.

  2. 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.

  3. 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.

  4. 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, 1.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-gw3q-hxvp-x7vmIN-MAL-2026-010493

References

Credits

  • Amazon Inspector · finder
  • SafeDep · 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.

Explore