Malicious AsyncAPI npm Packages Used GitHub Actions Workflows to Deliver Malware
Summary
Attackers compromised two AsyncAPI GitHub repositories and abused release workflows to publish five malicious npm versions carrying a multi-stage RAT. One researcher said automated data harvesting failed; versions were removed, but exposed systems need cleanup and their
Key points
- On July 14, an attacker compromised two AsyncAPI GitHub repositories and injected malware into project files.
- The attacker abused a misconfigured GitHub Actions workflow and trusted-publisher integration; legitimate release workflows published packages with SLSA provenance attestations.
- Five malicious versions across four @asyncapi packages were published, including versions of @asyncapi/specs with more than 2.1 million weekly downloads.
- The malware used an obfuscated JavaScript first stage, retrieved a second-stage script from IPFS, and launched a modular payload with persistence and several C2 communication methods.
- The malware was designed to target credentials, secrets, browser data, wallets, databases, and CI/CD data. Aikido researchers said automated harvesting exited before collecting data, though collection could be performed manually.
- The malicious package versions were removed after an exposure window of about four hours. Existing installations and lock files may still contain them.
- Recommended actions include using known-good files, regenerating lock files, removing the hidden payload, terminating malicious processes, and rotating credentials.
Article Details
- Event Type
- Software supply-chain attack involving compromised AsyncAPI GitHub repositories and trojanized npm package releases.
- Impact
- Five malicious package versions delivered a multi-stage remote access trojan with data-stealing capabilities. The malware was designed to target secrets, credentials, browser data, cryptocurrency wallets, databases, and CI/CD data; however, Aikido reported that the data-harvesting tool exits before collecting anything, though researchers said collection could be performed manually. The releases were removed from npm, but existing installations and lock files created during the exposure window may still contain them.
MITRE ATT&CK
T1059.007 · JavaScriptAn obfuscated JavaScript statement in the packages triggers a downloader when the infected file is imported.T1071.001 · Web ProtocolsThe malware communicates with its command-and-control server over HTTP.T1105 · Ingress Tool TransferThe malware retrieves a second-stage script from IPFS and can download Gitleaks and HackBrowserData.
Malware
Vendors
GitHubFive malicious AsyncAPI packages were published to npm in a supply-chain attack that used compromised GitHub Actions workflows to deliver a remote access trojan with data-stealing capabilities.npmFive malicious AsyncAPI packages were published to npm in a supply-chain attack that used compromised GitHub Actions workflows to deliver a remote access trojan with data-stealing capabilities.
Products
GitHub ActionsFive malicious AsyncAPI packages were published to npm in a supply-chain attack that used compromised GitHub Actions workflows to deliver a remote access trojan with data-stealing capabilities.npmFive malicious AsyncAPI packages were published to npm in a supply-chain attack that used compromised GitHub Actions workflows to deliver a remote access trojan with data-stealing capabilities.