Malicious Code Detected in appkeys Package - Security Alert

appkeys Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14673: Malicious code in appkeys (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 appkeys package is a Node.js library designed for managing application keys securely. It is widely used in various npm projects to handle sensitive information. However, recent findings have revealed that this package contains malicious code, posing a significant security risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the appkeys package originates from the inclusion of malicious code that can compromise the integrity and security of applications using this library. This malicious code may allow unauthorized access to sensitive data, lead to data breaches, or enable further exploitation of the affected systems. The issue affects all versions starting from 0, making it critical for developers to address this vulnerability promptly.

How To Fix

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

npm uninstall appkeys

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 measure, consider removing the appkeys package from your project until a secure version is released. You can do this by running: npm uninstall appkeys. Additionally, review your codebase for any instances where appkeys is used and replace it with a secure alternative if necessary.

Conclusion

The appkeys package has been identified as containing malicious code, posing a serious security threat to applications that utilize it. Developers are urged to update or remove the package to safeguard their applications. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for appkeys →

Share this vulnerability

FAQ

The appkeys package is used for managing application keys securely in Node.js applications.

The malicious code can compromise application security, potentially leading to unauthorized data access and breaches.

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.

Yes, it is recommended to update the appkeys package to the latest secure version to mitigate the vulnerability.

As a workaround, consider removing the appkeys package from your project until a secure version is available.

How To Fix

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

npm uninstall appkeys

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