M-Red-Team: AsyncAPI Supply Chain Compromise via GitHub Actions
M-Red-Team compromised AsyncAPI npm packages via GitHub Actions, injecting malicious code into the supply chain. The attack leveraged build system access to distribute compromised packages to downstream consumers.
- Disclosed
- Last updated
- Blast radius
- AsyncAPI npm packages and projects depending on them; GitHub Actions workflows using AsyncAPI
- Attack vectors
- Threat actor
- Affected entities
- @asyncapinpm package namespace
A supply chain attack designated M-Red-Team targeted the AsyncAPI project, resulting in the publication of malicious npm packages under the @asyncapi namespace. The attack was facilitated through compromise of GitHub Actions workflows, allowing attackers to inject malicious code during the build and release process.
The compromised packages were distributed to npm and could affect any project that depends on AsyncAPI libraries. The attack demonstrates a sophisticated approach combining build-system compromise with package distribution to maximize reach across the npm ecosystem.
The incident was detected and disclosed by Wiz, with mitigation guidance provided to detect and remove affected packages from development environments and supply chains.
Indicators of compromise
- Packages
- @asyncapi
Remediation
- Audit npm dependencies for @asyncapi packages and identify affected versions
- Remove or update compromised @asyncapi packages to known-clean versions
- Review GitHub Actions workflows and secrets for unauthorized access or modifications
- Implement package integrity verification and signed releases
- Monitor for suspicious activity in AsyncAPI package downloads and usage
- Rotate any credentials or tokens that may have been exposed through the compromised build system
Sources
Cite this entry
"M-Red-Team: AsyncAPI Supply Chain Compromise via GitHub Actions." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 14, 2026; last updated July 14, 2026. https://supplychainattack.org/incident/m-red-team-asyncapi-supply-chain-compromise-via-github-actions-zsietq
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- activecritical
TeamPCP's Mini Shai-Hulud Is Back: A Self-Spreading Supply Chain Attack Compromises TanStack npm Packages
The Mini Shai-Hulud worm is actively compromising legitimate npm packages by hijacking CI/CD pipelines and stealing developer secrets. The attack was first detected by StepSecurity in official @tanstack packages and is spreading across the npm ecosystem in real time.
TeamPCPMini Shai HuludnpmOtherCompromised packageBuild-system compromise - activecritical
Shai-Hulud Worm Pivots to Multi-Cloud: intercom-client@7.0.4 Hijacked — 361,000 Weekly Downloads, AWS, GCP, and Azure Credentials Now in Scope
The Shai-Hulud worm has hijacked intercom-client@7.0.4 (361,510 weekly downloads) via a compromised GitHub Actions OIDC publishing pipeline, 29 hours after compromising mbt@1.2.48 and @cap-js/sqlite@2.2.2. The worm is actively propagating through CI/CD infrastructure stolen from earlier victims, targeting multi-cloud credentials (AWS, GCP, Azure).
Shai-HuludnpmOtherCompromised packageBuild-system compromiseAccount takeover - containedcritical
Coordinated AsyncAPI Supply Chain Attack: Miasma RAT Delivered via Compromised CI/CD Pipelines in Two Repositories
Three AsyncAPI npm packages were compromised on July 14, 2026 and published with malicious code (Miasma RAT dropper) via a compromised CI/CD pipeline. The attacker gained push access to the repository's next branch, allowing them to use the legitimate GitHub Actions release workflow to publish malicious versions with valid npm OIDC provenance attestations.
MiasmanpmOtherBuild-system compromiseMalicious commit - containedcritical
Malware in setup-cicd
The npm package setup-cicd was found to contain malware, potentially giving outside entities full control of affected systems. Any computer with this package installed or running should be considered fully compromised.
npmOtherCompromised package