Supply Chain Compromise via GitHub Actions
An attacker exploited a misconfigured GitHub Actions workflow in the AsyncAPI generator repository by abusing a 'pwn request' vulnerability. This led to the theft of a highly privileged Personal Access Token from the asyncapi-bot account. Using these credentials, the attacker published five malicious npm package versions under the @asyncapi namespace, which collectively have over three million weekly downloads. The malware payload executes upon import and includes multi-stage capabilities for persistence, command and control communication, and credential theft targeting browsers, SSH keys, cloud credentials, and cryptocurrency wallets. The malware shares traits with the Miasma framework but also has unique features.
AI Analysis
Technical Summary
On July 14, 2026, a supply chain compromise occurred via a misconfigured GitHub Actions workflow in the AsyncAPI generator repository. The attacker exploited a 'pwn request' vulnerability to open multiple pull requests, one of which contained obfuscated JavaScript that exfiltrated a privileged Personal Access Token belonging to asyncapi-bot. With the stolen token, the attacker published five malicious npm package versions under the @asyncapi namespace. These packages, downloaded millions of times weekly, contain a multi-stage malware payload that activates on import, establishes persistence, connects to command and control infrastructure, and steals various credentials including browser data, SSH keys, cloud credentials, and cryptocurrency wallets. The malware shows technical similarities to the Miasma malware framework but includes a comprehensive and unique command framework.
Potential Impact
The compromise allows attackers to distribute malware through widely used npm packages under the trusted @asyncapi namespace, potentially affecting millions of users. The malware's capabilities include credential theft across multiple sensitive areas (browsers, SSH, cloud, crypto wallets), persistence on infected systems, and remote command and control, posing significant risks to confidentiality and system integrity.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Organizations using packages from the @asyncapi namespace should verify the integrity and authenticity of their dependencies. Review and secure GitHub Actions workflows to prevent unauthorized token exposure, especially by restricting pull request workflows and limiting token permissions. Rotate any exposed Personal Access Tokens immediately and audit for suspicious activity. Monitor for and remove any malicious package versions if detected.
Indicators of Compromise
- hash: 22bf76fe317ea6769bd38619bd440e42d119bd6b
- hash: 9890950adcbc2478e7a080234f053214adbad44e
- hash: a7e18d96efd3cdb127ef4cdcad9e3ad26c482bf2
- hash: c70e105e212ff3c1daa04bb2a62507717f296b0b
- hash: c8cb3f6d5b90c46686d2bf531dc1a5786e27edc5
Supply Chain Compromise via GitHub Actions
Description
An attacker exploited a misconfigured GitHub Actions workflow in the AsyncAPI generator repository by abusing a 'pwn request' vulnerability. This led to the theft of a highly privileged Personal Access Token from the asyncapi-bot account. Using these credentials, the attacker published five malicious npm package versions under the @asyncapi namespace, which collectively have over three million weekly downloads. The malware payload executes upon import and includes multi-stage capabilities for persistence, command and control communication, and credential theft targeting browsers, SSH keys, cloud credentials, and cryptocurrency wallets. The malware shares traits with the Miasma framework but also has unique features.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
On July 14, 2026, a supply chain compromise occurred via a misconfigured GitHub Actions workflow in the AsyncAPI generator repository. The attacker exploited a 'pwn request' vulnerability to open multiple pull requests, one of which contained obfuscated JavaScript that exfiltrated a privileged Personal Access Token belonging to asyncapi-bot. With the stolen token, the attacker published five malicious npm package versions under the @asyncapi namespace. These packages, downloaded millions of times weekly, contain a multi-stage malware payload that activates on import, establishes persistence, connects to command and control infrastructure, and steals various credentials including browser data, SSH keys, cloud credentials, and cryptocurrency wallets. The malware shows technical similarities to the Miasma malware framework but includes a comprehensive and unique command framework.
Potential Impact
The compromise allows attackers to distribute malware through widely used npm packages under the trusted @asyncapi namespace, potentially affecting millions of users. The malware's capabilities include credential theft across multiple sensitive areas (browsers, SSH, cloud, crypto wallets), persistence on infected systems, and remote command and control, posing significant risks to confidentiality and system integrity.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Organizations using packages from the @asyncapi namespace should verify the integrity and authenticity of their dependencies. Review and secure GitHub Actions workflows to prevent unauthorized token exposure, especially by restricting pull request workflows and limiting token permissions. Rotate any exposed Personal Access Tokens immediately and audit for suspicious activity. Monitor for and remove any malicious package versions if detected.
Technical Details
- Author
- AlienVault
- Tlp
- white
- References
- ["https://www.wiz.io/blog/m-red-team-asyncapi-supply-chain-compromise-via-github-actions"]
- Adversary
- null
- Pulse Id
- 6a5665a03fa69522f5e6c982
- Threat Score
- null
Indicators of Compromise
Hash
| Value | Description | Copy |
|---|---|---|
hash22bf76fe317ea6769bd38619bd440e42d119bd6b | — | |
hash9890950adcbc2478e7a080234f053214adbad44e | — | |
hasha7e18d96efd3cdb127ef4cdcad9e3ad26c482bf2 | — | |
hashc70e105e212ff3c1daa04bb2a62507717f296b0b | — | |
hashc8cb3f6d5b90c46686d2bf531dc1a5786e27edc5 | — |
Threat ID: 6a5672b068715ace43ec3001
Added to database: 07/14/2026, 17:32:32 UTC
Last enriched: 07/14/2026, 17:49:48 UTC
Last updated: 07/15/2026, 01:17:26 UTC
Views: 12
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.