Malicious Code Detected in angular2-safe-provider: A Critical Security Alert

angular2-safe-provider Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14534: Malicious code in angular2-safe-provider (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 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 angular2-safe-provider package is an npm library designed to provide safe dependency injection for Angular applications. It is intended to enhance security by ensuring that only trusted providers are used in the application. However, it has been found to contain malicious code, posing significant risks to users who integrate this package into their projects.

Vulnerability Detail

The vulnerability in the angular2-safe-provider package originates from the inclusion of malicious code that can compromise the security of applications utilizing this library. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the affected applications. The presence of such code undermines the integrity of the package and poses a serious threat to developers and end-users alike.

How To Fix

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

npm uninstall angular2-safe-provider

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, avoid using the angular2-safe-provider package in your application. Instead, consider using alternative libraries that offer similar functionality without the associated risks. Always ensure to review the security status of any packages before integrating them into your project.

Conclusion

The discovery of malicious code in the angular2-safe-provider package highlights the importance of vigilance when using open-source libraries. Developers should take immediate action to remove the affected package and seek alternatives to safeguard their applications. Utilizing tools like Vulert can help monitor for vulnerabilities in real-time.

See every vulnerability recorded for angular2-safe-provider →

Share this vulnerability

FAQ

It is an npm library designed to provide safe dependency injection for Angular applications.

The specific nature of the malicious code has not been disclosed, but it poses significant security risks.

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

Immediately uninstall the angular2-safe-provider package and look for alternative libraries to ensure your application's security.

If a patched version is released, you will be able to update to it using 'npm install angular2-safe-provider@<patched_version>'. Keep an eye on the package repository for updates.

How To Fix

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

npm uninstall angular2-safe-provider

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