Malicious Code Vulnerability in @angjlar/core Package

@angjlar/core Updated 05 Oct 2026

Summary

05/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17534: Malicious code in @angjlar/core (npm). Affects @angjlar/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 @angjlar/core package is a malicious npm package that impersonates the legitimate @angular/core package. It aims to deceive developers into installing it by mimicking the original package's metadata, such as its description, author, and repository URL. This package is designed to execute arbitrary code on the installer's machine, posing a significant security risk.

Vulnerability Detail

The vulnerability arises from the postinstall lifecycle script in the @angjlar/core package's package.json file, which executes a command to fetch and run JavaScript code from an external source (gitflic.ru) via curl. This allows the operator of the remote script to execute arbitrary code on the user's machine during the installation process. The malicious nature of this package is highlighted by its impersonation of the legitimate Angular package, targeting developers who may mistype the package name.

How To Fix

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

npm uninstall @angjlar/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 measure, avoid using the @angjlar/core package and ensure that your package.json file does not include it. Regularly audit your dependencies to identify any potentially malicious packages.

Conclusion

The @angjlar/core package poses a significant security risk due to its malicious code execution capabilities. Developers should be vigilant in verifying package names and using tools like Vulert to monitor for vulnerabilities. Immediate action is required to remove this package and ensure the integrity of your applications.

See every vulnerability recorded for @angjlar/core →

Share this vulnerability

FAQ

The @angjlar/core package is a malicious npm package that impersonates the legitimate @angular/core package, designed to execute arbitrary code on the user's machine.

The vulnerability works by executing a postinstall script that fetches and runs untrusted JavaScript code from an external source, allowing for arbitrary code execution.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

If you have installed @angjlar/core, you should uninstall it immediately using the command: npm uninstall @angjlar/core and replace it with the legitimate @angular/core package.

Using malicious packages can lead to arbitrary code execution, data breaches, and compromise of your application's security, potentially affecting your users and infrastructure.

How To Fix

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

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