@asyncapi/specs
This report shows the evidence for @asyncapi/specs@6.11.2. 6 of 6 known versions are blocked or flagged. See all versions.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2025-190643 confirms this npm version as malicious.
Advisory
MAL-2025-190643
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @asyncapi/specs (npm)
Details
@asyncapi/specs versions 6.11.2-alpha.1 and 6.11.2 were 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. Unlike the whitespace-hiding technique used in the compromised generator packages, here the attacker prepended the malicious code directly to the top of index.js. When the package is installed, the injected code spawns a child process that downloads the Miasma RAT binary from IPFS (https://ipfs.io/ipfs/Qmet4fhsAaWMBUxNDfREHwgiyDeSWy4YSYs9wiKUW5jGyf), 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 6.11.1.
---
## Source: amazon-inspector (3b9e99714f1fe7132e3c690ab23d255f689800dcb1234ebf1d6bf68c61f2d2ca) index.js in @asyncapi/specs 6.11.2 contains a string-array-obfuscated payload (_0x-style decoder) that, whenever the module is required, spawns a detached node child process. The decoded logic fetches a file from the IPFS gateway URL https://ipfs.io/ipfs/Qmet4fhsAaWMBUxNDfREHwgiyDeSWy4YSYs9wiKUW5jGyf, writes it as sync.js under a platform-specific hidden directory (LOCALAPPDATA/NodeJS on Windows, ~/Library/Application Support/NodeJS on macOS, ~/.local/share/NodeJS on Linux), and executes it detached via node. The obfuscation hides the URL, target filename, and use of https, child_process, and fs APIs. A legitimate AsyncAPI JSON spec loader has no need for obfuscated code or remote code fetch-and-execute; the behavior is inconsistent with the package's advertised purpose and gives whoever controls the IPFS content full code execution on any machine that installs or loads this version.
## Source: ghsa-malware (5715faf8c80acf7c963aac8c332a2cffed06a23ca9663a2fdcb6fd11be4325e9) 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 (938ab70c817e26ed594a554747f21aa339e5a01f3daf999dead6c94fd2289490) 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.
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to @asyncapi/specs@6.11.2.
The same advisory and Firewall decision cover 6 recorded versions
6.10.1, 6.11.2, 6.8.2, 6.8.3, 6.9.1, 6.11.2-alpha.1
The versions list below shows the verdict for each recorded version.
- Avoid installing @asyncapi/specs@6.11.2. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.