npm package report

Is @asyncapi/generator-helpers safe?

Versions 0.2.2, 0.2.1 and 1.1.1 of @asyncapi/generator-helpers were compromised. Other versions are not flagged as malicious.

Do not install @asyncapi/generator-helpers 0.2.2, 0.2.1 or 1.1.1

CRITICAL

Compromised releases. Added to CyberXYZ 2025-11-24, OSV malicious-package feed (Google / OpenSSF).

// what we observed

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

Reported by Amazon Inspector, GitHub Advisory Database and Google Open Source Security via OSV.

// versions and what to do
Malicious
0.2.2, 0.2.1, 1.1.1
Move to
1.1.0 newest 1.x release, no known advisory
0.2.0 newest 0.x release, no known advisory

If one of these versions was installed, remove it and treat the credentials, tokens and SSH keys on that machine as exposed: rotate them. Check CI runners and container images that installed it too.

npm install @asyncapi/generator-helpers@1.1.0

OSV recordadvisoryreferencereferencereferencereferencereferenceissue

// reach

0 direct dependencies

none carry a known advisory

    0 packages depend on it

    an advisory here reaches each of them

      Create a free accountfor every dependency path, dependent and what to upgrade
      // ai model usage

      Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.



      Checked 2026-10-31 at 00:00 UTC. Updated continuously from NVD, GHSA, OSV and CNA feeds.

      Think a verdict here is wrong? Tell us — we respond within 2 business days.