Malicious Code Vulnerability in angula Package

angula Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14520: Malicious code in angula (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The angula package is a JavaScript library designed for building web applications. It provides developers with tools and functionalities to create dynamic and responsive user interfaces. However, it has been identified to contain malicious code, which poses a significant risk to applications that utilize this package.

Vulnerability Detail

The vulnerability in the angula package stems from the inclusion of malicious code that can compromise the security of applications using it. This code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The vulnerability was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action.

How To Fix

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

npm uninstall angula

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, developers can isolate the use of the angula package in a controlled environment to limit exposure while searching for alternatives. However, this is not a long-term solution and should not replace the need for a proper fix.

Conclusion

The angula package has been identified as containing malicious code, posing a serious threat to applications that utilize it. Immediate action is required to remove the package and replace it with a secure alternative. Regular monitoring for updates and vulnerabilities is essential to maintain application security.

See every vulnerability recorded for angula →

Share this vulnerability

FAQ

The angula package is a JavaScript library used for building web applications, providing tools for creating dynamic user interfaces.

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

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

You should remove the angula package from your project and replace it with a secure alternative immediately.

Currently, there is no patched version available. Users are advised to remove the package until a secure alternative is found.

How To Fix

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

npm uninstall angula

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