Malicious code in @angular_devkit/build-webpack (npm)
The npm package @angular_devkit/build-webpack version 99.1.1 was identified as malicious by the OpenSSF Package Analysis project. The package communicates with domains associated with malicious activity and executes commands consistent with malicious behavior.
- Disclosed
- Last updated
- Blast radius
- Potentially all projects that installed @angular_devkit/build-webpack version 99.1.1
- Ecosystems
- Attack vectors
- Affected entities
- @angular_devkit/build-webpack · 99.1.1
The OpenSSF Package Analysis project identified @angular_devkit/build-webpack version 99.1.1 on npm as containing malicious code. The package was flagged for communicating with a domain associated with malicious activity and executing commands consistent with malicious behavior.\n\nThis appears to be a typosquatting or account compromise attack targeting the legitimate Angular DevKit build-webpack package. The malicious version 99.1.1 was published to npm and could affect any developer or CI/CD pipeline that installed this specific version.\n\nThe incident was disclosed through the OpenSSF's malicious packages repository and GitHub Security Advisory GHSA-qx5g-37g8-5j97.
Indicators of compromise
- Packages
- @angular_devkit/build-webpack@99.1.1
Remediation
- Immediately remove @angular_devkit/build-webpack version 99.1.1 from all environments
- Audit all systems where this package was installed for signs of compromise
- Review network logs for connections to the malicious domain identified by OpenSSF
- Update to a known-good version of @angular_devkit/build-webpack or the legitimate Angular DevKit package
- Regenerate any credentials or secrets that may have been exposed on affected systems
- Check npm audit logs and package-lock.json files to identify all affected projects
Sources
- GitHub Advisory GHSA-qx5g-37g8-5j97 · GitHub Advisory Database
Cite this entry
"Malicious code in @angular_devkit/build-webpack (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 26, 2026; last updated July 26, 2026. https://supplychainattack.org/incident/malicious-code-in-angular-devkit-build-webpack-npm-65u4pq
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in sme-rko-finance-front-operations-feed-impl (npm)
The npm package sme-rko-finance-front-operations-feed-impl contained malicious code that downloads and executes platform-specific binary payloads via Cloudflare Workers or DNS-based staging channels. The malware obfuscates child_process imports and executes on require(), making it active upon installation.
npmCompromised package - containedcritical
Malicious code in sme-rko-finance-front-operations-overnight (npm)
The npm package sme-rko-finance-front-operations-overnight contains malicious code that downloads and executes attacker-controlled binaries from Cloudflare Workers hosts on package require. The payload uses obfuscation techniques to evade static analysis and includes environment-based gating to reduce detection.
npmCompromised package - containedcritical
Malicious code in sme-rko-finance-front-payment-registers-operations-domain (npm)
The npm package sme-rko-finance-front-payment-registers-operations-domain contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure. The package uses obfuscated string construction to hide command-and-control domains and implements a DNS-TXT fallback channel for payload delivery.
npmCompromised package - resolvedcritical
Malicious code in sme-rko-finance-front-operations-providers (npm)
The npm package sme-rko-finance-front-operations-providers contained malicious code that downloads and executes platform-specific binaries from attacker-controlled Cloudflare Workers subdomains and DNS-TXT fallback channels upon require().
npmCompromised package