Critical Malicious Code Vulnerability in @postman/node-keytar Package

@postman/node-keytar Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190754: Malicious code in @postman/node-keytar (npm). Affects @postman/node-keytar versions 7.9.4 – 7.9.6. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The @postman/node-keytar package is a Node.js library that provides a simple way to store and retrieve secrets securely. It is commonly used in applications that require secure storage of sensitive information such as API keys and passwords. However, recent findings have revealed that this package contains malicious code that compromises the security of any system it is installed on.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the @postman/node-keytar package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information stored on that system. The ramifications of this vulnerability are severe, as it can lead to data breaches and loss of control over critical secrets and keys. Users are advised to treat any system with this package as compromised.

How To Fix

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

npm uninstall @postman/node-keytar

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

There are no effective workarounds for this vulnerability other than removing the package and rotating any compromised secrets. It is essential to ensure that your application does not rely on this package for secure storage.

Conclusion

The discovery of malicious code in the @postman/node-keytar package poses a significant threat to users and their sensitive information. Immediate action is required to remove the package and secure any affected systems. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for @postman/node-keytar →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any sensitive information stored on the affected system.

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

Failing to address this vulnerability can lead to unauthorized access to sensitive information, data breaches, and potential loss of control over your system.

There is no patch available for the @postman/node-keytar package. The only solution is to remove the package entirely.

Vulert monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file, allowing developers to stay informed about potential risks.

How To Fix

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

npm uninstall @postman/node-keytar

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