Malicious Code Vulnerability in @angulra/cli Package

@angulra/cli Updated 05 Oct 2026

Summary

04/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17495: Malicious code in @angulra/cli (npm). Affects @angulra/cli versions 22.2.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 @angulra/cli package is a character-swapped version of the legitimate @angular/cli package, which is widely used for building Angular applications. It mimics the original package's metadata, including its description, repository, and dependencies. However, this malicious package contains a preinstall script that poses significant security risks to users.

Vulnerability Detail

The vulnerability originates from the @angulra/cli package, which executes a preinstall script that fetches and runs JavaScript code from an untrusted source. This script is executed automatically during the npm install process, allowing the operator of the malicious endpoint to execute arbitrary code on the installer's machine. The lack of integrity checks and the use of an unpinned URL further exacerbate the risk, making it a severe security threat.

How To Fix

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

npm uninstall @angulra/cli

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 workaround, users can manually inspect their package.json file and remove any references to @angulra/cli. Additionally, ensure that your npm install commands do not include this malicious package.

Conclusion

The @angulra/cli package poses a significant security risk due to its malicious preinstall script that executes arbitrary code. Users are strongly advised to uninstall this package and switch to the legitimate @angular/cli to safeguard their systems.

See every vulnerability recorded for @angulra/cli →

Share this vulnerability

FAQ

The @angulra/cli package is a malicious version of the legitimate @angular/cli package, designed to execute harmful code on users' machines.

The vulnerability allows an attacker to execute arbitrary code on your system during the installation of the malicious package, potentially leading to data breaches or system compromise.

You can use Vulert, 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.

If you have installed @angulra/cli, you should uninstall it immediately and install the legitimate @angular/cli package instead.

While npm does provide integrity checks for packages, the @angulra/cli package lacks these checks, making it particularly dangerous.

How To Fix

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

npm uninstall @angulra/cli

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