@asyncapi/generator version 3.3.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. The malicious commit 3eab3ec9304aa26081358330491d3cfeb55cc245 was pushed to the generator repository's next branch. 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 3.3.0.

---

-= Per source details. Do not edit below this line.=-

lib/templates/config/validator.js contains a javascript-obfuscator string-array block (variables _0x1dd48b/_0x2d89, base64+URI-decode decoder with rotation) injected between legitimate functions. The block requires fs, path, https, child_process.spawn, and os, and invokes a top-level main() that calls spawn(<decoded-node-binary>, ['-e', <decoded-payload>], {detached:true, stdio:'ignore', windowsHide:true}).unref(). The -e argument is a ~4KB base64-encoded JavaScript body reconstructed from the obfuscated string array. The command name, -e flag, stdio value, and payload are all hidden behind the string-array decoder. Because validator.js is reachable via require() in this widely-used generator, loading the module launches a hidden, detached Node child process running attacker-supplied code with fs/https/os capabilities on the installer's machine. The obfuscation, mismatch with the file's declared validator purpose, and injection between existing functions are inconsistent with a legitimate maintainer change and match a compromised-release pattern.

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.