Malicious Code Detected in angulargp Package - Security Alert

angulargp Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14536: Malicious code in angulargp (npm). Affected versions are not published. 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 angulargp package is a JavaScript library designed for Angular applications, providing various functionalities for enhancing user interfaces. It is widely used in the npm ecosystem for its ease of integration and robust features. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the angulargp package originates from the inclusion of malicious code that can compromise the security of applications using this library. This code may lead to unauthorized access, data breaches, or other malicious activities. The issue affects all versions of the package starting from its introduction, making it critical for developers to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall angulargp

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, consider removing the angulargp package from your project until a secure version is released. You can uninstall it using the command: npm uninstall angulargp. Additionally, look for alternative packages that provide similar functionalities without the associated risks.

Conclusion

The discovery of malicious code in the angulargp package highlights the importance of regularly monitoring and updating dependencies in software projects. Developers are urged to take immediate action to secure their applications by updating or removing the affected package.

See every vulnerability recorded for angulargp →

Share this vulnerability

FAQ

angulargp is a JavaScript library for Angular applications, offering various features to enhance user interfaces.

The malicious code can lead to unauthorized access and data breaches, posing significant security threats.

You can use Vulert, which monitors vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Consider removing the angulargp package from your project as a temporary measure until a secure version is available.

Yes, using Vulert, you can monitor your package-lock.json file for vulnerabilities in real-time without needing to access the code.

How To Fix

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

npm uninstall angulargp

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