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 @aligntech-cw/alignerfit (npm)
Malicious code was discovered in the npm package @aligntech-cw/alignerfit. The package was identified by the OpenSSF malicious-packages project and assigned identifier MAL-2024-1743.
npmCompromised package - resolvedcritical
Malicious code in @akunsansan0/susu10 (npm)
@akunsansan0/susu10 is a malicious npm package containing autopublish scripts designed to automatically generate and republish derivative packages with randomized names to the npm registry. The package was part of a tea.xyz token reward campaign that flooded npm with similar malicious packages.
npmCompromised package - containedcritical
Malicious code in @antv/f-wx (npm)
The npm account `atool` was compromised and used to publish 631 malicious versions across 314 packages, including @antv/f-wx. Each version injects a preinstall hook executing an obfuscated Bun script that exfiltrates credentials via the GitHub API and establishes persistence through CI/CD workflow injection and system daemons.
Mini Shai HuludTeamPCPnpmOtherAccount takeoverCompromised packageMalicious commit - resolvedcritical
Malicious code in @akunsansan0/susu11 (npm)
@akunsansan0/susu11 is a malicious npm package containing autopublish scripts designed to automatically generate and republish derivative packages with randomized names to inflate tea protocol token rewards. The package modifies package.json, changes version numbers, and continuously pollutes the npm registry with variants.
npmCompromised package