Critical Malicious Code Vulnerability in @angular_devkit/architect Package

@angular_devkit/architect Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6900: Malicious code in @angular_devkit/architect (npm). Affects @angular_devkit/architect versions >= 99.1.1. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The @angular_devkit/architect package is a crucial component of the Angular framework, providing tools for building and managing Angular applications. It facilitates the execution of build and development tasks, allowing developers to streamline their workflows. However, this package has been identified to communicate with a domain associated with malicious activity, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability arises from the package's communication with a domain linked to malicious activities. This could lead to unauthorized data access, potential data breaches, or the execution of harmful scripts within applications. The issue was introduced in version 99.1.1, making it imperative for users of this package to be aware of the risks and take appropriate action to mitigate them.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @angular_devkit/architect

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary measure, consider removing the @angular_devkit/architect package from your project until a secure version is confirmed. You can uninstall it using the command: npm uninstall @angular_devkit/architect.

Conclusion

The @angular_devkit/architect package has a critical vulnerability that allows communication with a malicious domain, posing severe risks to applications. Users are urged to update the package or remove it until a secure version is available. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for @angular_devkit/architect →

Share this vulnerability

FAQ

The vulnerability involves the package communicating with a domain associated with malicious activities, which can compromise application security.

You can use the Vulert platform, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

Failure to address this vulnerability could lead to unauthorized access to sensitive data, data breaches, or the execution of malicious scripts that could harm your application.

Yes, updating to the latest version of the @angular_devkit/architect package will provide the necessary security patches to mitigate this vulnerability.

If immediate updates are not feasible, consider removing the package temporarily until a secure version is available to minimize risk.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @angular_devkit/architect

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback