Malicious Code Vulnerability in @angupar/core: A Critical Security Risk
Summary
MAL-2026-17539: Malicious code in @angupar/core (npm). Affects @angupar/core versions 22.2.1. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The package @angupar/core is a malicious npm package that impersonates the legitimate Angular core package (@angular/core). It is designed to deceive users into installing it by mimicking the name, author, and repository of the original package. This package executes arbitrary code during installation, posing significant security risks to applications that rely on it.
Vulnerability Detail
The vulnerability originates from the package's postinstall script, which runs a command to fetch and execute JavaScript from an untrusted third-party source. This script uses curl to download code from a user account on gitflic.ru, routed through web.archive.org. The lack of integrity checks and the unpinned nature of the fetch means that any code could be executed, leading to potential data breaches, system compromise, or further exploitation of the host environment.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @angupar/coreIf 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 @angupar/core package and ensure that your package.json does not include it. Regularly audit your dependencies to identify any potentially malicious packages.
Conclusion
The @angupar/core package poses a significant security threat due to its malicious code execution capabilities. Users are strongly advised to remove this package and ensure they are using trusted sources for their dependencies. Regular monitoring and auditing of packages can help mitigate such risks in the future.
See every vulnerability recorded for @angupar/core →
FAQ
Using @angupar/core can lead to arbitrary code execution on your system, which may result in data loss, unauthorized access, or further exploitation.
You can use Vulert to monitor your application for vulnerabilities. By analyzing your package-lock.json file, Vulert provides real-time alerts for open-source vulnerabilities.
There is no patch for @angupar/core as it is a malicious package. The best course of action is to uninstall it and use the legitimate @angular/core package.
Always verify the authenticity of packages before installation. Use tools like Vulert to monitor your dependencies for vulnerabilities regularly.
Immediately uninstall the package using npm uninstall @angupar/core and check your application for any signs of compromise.
