Malicious code in @angular_devkit/build_angular (npm)
Malicious code was discovered in the npm package @angular_devkit/build_angular. The compromised package contained code that communicates with a domain associated with malicious activity. The incident was identified and reported by the OpenSSF malicious packages project.
- Disclosed
- Last updated
- Blast radius
- Potentially all projects using affected versions of @angular_devkit/build_angular
- Ecosystems
- Attack vectors
- Affected entities
- @angular_devkit/build_angularnpm package
A malicious version of the npm package @angular_devkit/build_angular was identified containing code designed to communicate with a domain associated with malicious activity. This represents a direct compromise of the package itself rather than a build-time or maintainer-level attack.\n\nThe vulnerability was discovered and documented by the OpenSSF's malicious packages project (MAL-2025-6901), which maintains a public catalog of confirmed malicious packages across major ecosystems.\n\nAny developer or project that installed the affected version(s) of @angular_devkit/build_angular may have been exposed to malicious behavior during the build process or at runtime, depending on the specific payload and trigger conditions.
Indicators of compromise
- Packages
- @angular_devkit/build_angular
Remediation
- Identify and audit all projects using @angular_devkit/build_angular to determine which versions were installed
- Remove or update to a known-clean version of @angular_devkit/build_angular from a trusted source
- Review build logs and system activity during the period when the malicious package may have been in use
- Regenerate any credentials, tokens, or secrets that may have been exposed during the compromise
- Scan affected systems for indicators of compromise or persistence mechanisms
- Monitor for any suspicious outbound network connections to the malicious domain
Sources
- GitHub Advisory GHSA-f792-mwpq-wxpf · GitHub Advisory Database
Cite this entry
"Malicious code in @angular_devkit/build_angular (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-angular-npm-1t8i6l
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