Malicious Code Injection in @anuglar/core Package

@anuglar/core Updated 05 Oct 2026

Summary

05/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17541: Malicious code in @anuglar/core (npm). Affects @anuglar/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 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 @anuglar/core package is a malicious npm package that closely resembles the legitimate @angular/core package, which is a core framework for building web applications. This malicious package aims to deceive users by copying the description, author information, and repository URL of the legitimate package, thereby impersonating it. Users may unknowingly install this package, exposing their systems to potential threats.

Vulnerability Detail

The vulnerability arises from a malicious postinstall script in the @anuglar/core package. When installed, this script executes a command that downloads and runs arbitrary JavaScript code from a third-party host (gitflic.ru) via web.archive.org. This code is not verified, meaning it can change at any time, and it runs with the privileges of the user installing the package. The script also performs host reconnaissance by referencing system commands like 'ps' and 'id', which could lead to further exploitation.

How To Fix

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

npm uninstall @anuglar/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 temporary workaround, users can avoid using the @anuglar/core package and ensure that their package.json does not include it. Additionally, regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities.

Conclusion

The @anuglar/core package poses a significant security risk due to its malicious code execution capabilities. Users are strongly advised to uninstall this package and replace it with the legitimate @angular/core package. Regular audits and monitoring of dependencies are essential to maintain a secure development environment.

See every vulnerability recorded for @anuglar/core →

Share this vulnerability

FAQ

The @anuglar/core package is a malicious npm package that impersonates the legitimate @angular/core package, which is used for building web applications.

If the @anuglar/core package is installed, it can execute arbitrary code on your system, potentially leading to data theft, system compromise, or further exploitation.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring access to the code or installation.

You should uninstall the @anuglar/core package immediately and replace it with the legitimate @angular/core package to mitigate the risk.

Regularly audit your dependencies, use tools like npm audit, and verify the authenticity of packages before installation to prevent similar vulnerabilities.

How To Fix

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

npm uninstall @anuglar/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