Critical Malicious Code Vulnerability in api-key-provider Package

api-key-provider Updated 02 Oct 2025

Summary

22/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6149: Malicious code in api-key-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 api-key-provider package is an npm library designed to facilitate the management of API keys in applications. It allows developers to securely store and retrieve API keys, enhancing the security of applications that rely on external services. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the api-key-provider package. This code can lead to full compromise of any computer that has the package installed or running. It poses a significant risk as it can expose sensitive information, including secrets and keys stored on the affected system. The malicious code can potentially allow unauthorized access and control over the system, making it imperative 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 api-key-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 workaround, it is recommended to rotate all secrets and keys stored on the affected computer from a different, secure machine. This ensures that any compromised credentials are no longer valid.

Conclusion

The api-key-provider package has been identified as containing malicious code that poses a severe risk to any system it is installed on. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for api-key-provider →

Share this vulnerability

FAQ

The api-key-provider package is an npm library used for managing API keys securely within applications.

The malicious code can lead to full compromise of your system, allowing unauthorized access to sensitive information.

You should immediately remove the package and rotate any secrets or keys stored on the affected machine.

Yes, you can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

While removing the package is necessary, it may not fully secure your system as other malicious software could remain. It's essential to take additional security measures.

How To Fix

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

npm uninstall api-key-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