Malicious Code Detected in express-secretkey Package - Vulnerability MAL-2025-20083

express-secretkey Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20083: Malicious code in express-secretkey (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 express-secretkey package is an npm module designed to facilitate the management of secret keys in Express applications. It provides developers with a straightforward way to handle sensitive information securely. However, this package has been identified to contain malicious code, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the express-secretkey package. This code can potentially compromise the security of applications by exposing sensitive data or allowing unauthorized access. The malicious nature of this vulnerability was discovered by Amazon Inspector, highlighting the importance of scrutinizing third-party packages for hidden threats.

How To Fix

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

npm uninstall express-secretkey

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 using alternative packages for managing secret keys in Express applications. Ensure that any alternative package is well-reviewed and free from known vulnerabilities.

Conclusion

The express-secretkey package has been identified as containing malicious code, posing a significant security risk to applications. It is essential to uninstall this package and consider alternatives to safeguard your application. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for express-secretkey →

Share this vulnerability

FAQ

The express-secretkey package is an npm module that helps developers manage secret keys in Express applications.

The specific details of the malicious code have not been disclosed, but it poses risks such as data exposure and unauthorized access.

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 uninstall the package immediately and consider using a secure alternative for managing secret keys.

Vulert uses the package-lock.json file to monitor open-source vulnerabilities, providing alerts in real-time without requiring access to your code.

How To Fix

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

npm uninstall express-secretkey

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