Malicious Code Vulnerability in @anguar/core Package

@anguar/core Updated 05 Oct 2026

Summary

05/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17535: Malicious code in @anguar/core (npm). Affects @anguar/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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The @anguar/core package is a malicious npm package that impersonates the legitimate @angular/core package. It is designed to trick developers into installing it by using a name that is almost identical to the original package. This package is intended for building web applications and is widely used in the JavaScript ecosystem. However, due to its malicious nature, it poses significant security risks to developers who may inadvertently install it.

Vulnerability Detail

The vulnerability originates from the @anguar/core package, which contains a postinstall lifecycle hook that executes a command to download and run malicious JavaScript code from an untrusted source. This code is fetched from a URL controlled by a third party, which can lead to arbitrary code execution on the developer's machine. The risk is particularly high for developers who mistype the package name and install this malicious version instead of the legitimate one.

How To Fix

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

npm uninstall @anguar/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, ensure that you always double-check the package names before installation. You can also use package-lock.json to monitor dependencies and avoid installing untrusted packages.

Conclusion

The @anguar/core package poses a significant security threat due to its malicious code execution capabilities. Developers must be vigilant in verifying package names and utilizing tools like Vulert to monitor for vulnerabilities. Always ensure you are using trusted packages to maintain a secure development environment.

See every vulnerability recorded for @anguar/core →

Share this vulnerability

FAQ

The @anguar/core package is a malicious npm package that impersonates the legitimate @angular/core package, designed to execute harmful code on installation.

You can check your project's package.json or package-lock.json files for the presence of @anguar/core. If found, it should be removed immediately.

Using the @anguar/core package can lead to arbitrary code execution on your machine, potentially compromising your development environment and data.

There is no patch for the @anguar/core package since it is a malicious package. The only solution is to uninstall it and use the legitimate @angular/core package.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check your application for vulnerabilities using the Vulert playground without signing up.

How To Fix

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

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