Malicious code in @angular_devkit/architect (npm)
Malicious code was discovered in the npm package @angular_devkit/architect. The 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 users of @angular_devkit/architect who installed affected versions
- Ecosystems
- Attack vectors
- Affected entities
- @angular_devkit/architectnpm package with malicious code
The npm package @angular_devkit/architect was found to contain malicious code that establishes communication with a domain associated with malicious activity. This represents a compromised package incident affecting the npm ecosystem.\n\nThe malicious behavior was identified and documented by the OpenSSF's malicious packages project (reference MAL-2025-6900). The package is a core dependency in the Angular development toolkit, potentially affecting a broad user base.\n\nThe incident was disclosed via GitHub Security Advisory GHSA-hfv6-3m9v-cwv7 on July 26, 2026. Users of affected versions should immediately audit their installations and dependencies.
Indicators of compromise
- Packages
- @angular_devkit/architect
Remediation
- Identify and remove all installations of affected versions of @angular_devkit/architect
- Audit project dependencies for any suspicious network activity or unexpected behavior
- Update to a patched version of @angular_devkit/architect once available
- Review npm package lock files and dependency trees for this package
- Monitor systems for any indicators of compromise from the malicious domain communications
- Consider running security audits on systems where affected versions were installed
Sources
- GitHub Advisory GHSA-hfv6-3m9v-cwv7 · GitHub Advisory Database
Cite this entry
"Malicious code in @angular_devkit/architect (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-architect-npm-1a7iju
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