@asyncapi/generator-components
Affected
- Versions:
0.3.2,0.3.3,0.7.1
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-m6ch-4fxh-v72c
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in @asyncapi/generator-components (npm)
@asyncapi/generator-components version 0.7.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 0.7.0.
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (53b011ee7d312f04a975987c919c0b2682df7e875bffceef2d932027e08a2f2a)
lib/utils/ErrorHandling.js contains an obfuscator.io string-array with a base64+decodeURIComponent decoder colocated with a top-level main() invocation reachable via the package's main entry (lib/index.js -> components/HandleError.js -> utils/ErrorHandling.js). On require of the package, main() spawns a detached, stdio-ignored Node subprocess via spawn('node', ['-e', <decoded-payload>], { detached: true, stdio: [...], windowsHide: true }).unref(), where the '-e' argument is ~3 KB of code decoded at runtime from a base64 blob in the obfuscated string array. The payload delivery mechanism (heavy obfuscation, runtime string decoding, detached backgrounded child process, hidden window on Windows) is inconsistent with any documented error-handling functionality and matches the shape of a hidden load-time RCE injection into a legitimate AsyncAPI package.
Source: ghsa-malware (f8979c7e0c324a5176bad2972f76ef64aaea7afdbbe7f728586c94682bd0d1ad)
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.
Source: google-open-source-security (f627fc2ccd3242571f3bc5f3872bef674cde6c2539401724b25294592da5c2a9)
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.
Not rated by the source.
0.3.2, 0.3.3, 0.7.1None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0