Malicious Code Injection in @angulr/core: A Critical Security Threat

@angulr/core Updated 05 Oct 2026

Summary

05/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17538: Malicious code in @angulr/core (npm). Affects @angulr/core 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The npm package @angulr/core is a malicious clone of Angular's legitimate @angular/core package. It falsely represents itself by mimicking the original package's metadata, including its description, author, and repository. This package is designed to deceive developers into installing it, leading to severe security risks due to its hostile postinstall script.

Vulnerability Detail

The vulnerability arises from a malicious postinstall script included in the @angulr/core package. When a developer runs 'npm install @angulr/core', the script executes a command that fetches and runs unverified JavaScript code from an external source (https://gitflic.ru). This poses a significant risk as it allows the execution of attacker-controlled code with the privileges of the installer, leading to potential data breaches, system compromises, and unauthorized access.

How To Fix

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

npm uninstall @angulr/core

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 workaround, you can use the following command to uninstall the malicious package and ensure you are using the correct Angular package: 'npm uninstall @angulr/core && npm install @angular/core'. Additionally, consider using Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The @angulr/core package poses a significant security threat due to its malicious code execution capabilities. Developers must be vigilant in verifying package authenticity and should utilize tools like Vulert to monitor for vulnerabilities. Immediate action is required to mitigate risks associated with this malicious package.

See every vulnerability recorded for @angulr/core →

Share this vulnerability

FAQ

@angulr/core is a malicious npm package that pretends to be Angular's core framework package, @angular/core.

The vulnerability allows the execution of malicious code on your system, potentially leading to data theft, system compromise, or unauthorized access.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If you have installed @angulr/core, you should uninstall it immediately using 'npm uninstall @angulr/core' and install the legitimate @angular/core package.

To prevent similar vulnerabilities, always verify package integrity, use trusted sources, and consider using monitoring tools like Vulert.

How To Fix

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

npm uninstall @angulr/core

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