Malicious Code Detected in @postman/final-node-keytar - Security Alert

@postman/final-node-keytar Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190901: Malicious code in @postman/final-node-keytar (npm). Affects @postman/final-node-keytar versions 7.9.1 – 7.9.2. 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 package @postman/final-node-keytar is a Node.js library used for secure storage and retrieval of credentials. It is commonly utilized in applications that require user authentication and secure data handling. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability originates from the discovery of malicious code within the @postman/final-node-keytar package, as identified by Amazon Inspector. This malicious code can potentially compromise the integrity of applications using this package, leading to unauthorized access to sensitive information or system exploitation. The affected versions are 7.9.1 and 7.9.2, which are known to harbor this malicious code.

How To Fix

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

npm uninstall @postman/final-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

If immediate patching is not feasible, consider removing the @postman/final-node-keytar package from your project until a secure version is confirmed. You can do this by running: npm uninstall @postman/final-node-keytar.

Conclusion

The discovery of malicious code in the @postman/final-node-keytar package poses a significant security threat to applications relying on it. Immediate action is recommended to update or remove the package to safeguard sensitive data and maintain application integrity.

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

Share this vulnerability

FAQ

The malicious code can compromise application security by allowing unauthorized access to sensitive data.

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

Consider removing the package from your project as a temporary measure until a secure version is available.

While specific exploits have not been detailed, the presence of malicious code indicates a high risk of exploitation.

You can reach out to Amazon Inspector at actran@amazon.com for further inquiries regarding this vulnerability.

How To Fix

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

npm uninstall @postman/final-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