Malicious Code Detected in @postman/pm-bin-windows-x64: Security Alert

@postman/pm-bin-windows-x64 Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190906: Malicious code in @postman/pm-bin-windows-x64 (npm). Affects @postman/pm-bin-windows-x64 versions 1.24.4 – 1.24.5. 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 package @postman/pm-bin-windows-x64 is a Windows-specific binary distribution of Postman's command-line interface, designed for API testing and development. It allows developers to run Postman collections and automate API testing. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users who rely on it for their development workflows.

Vulnerability Detail

The vulnerability originates from the package @postman/pm-bin-windows-x64, which has been identified to contain malicious code. This code can potentially compromise the security of systems using the package, leading to unauthorized access, data breaches, or other malicious activities. The specific versions affected are 1.24.5 and 1.24.4, as reported by Amazon Inspector.

How To Fix

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

npm uninstall @postman/pm-bin-windows-x64

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 workaround, users can avoid using the affected versions (1.24.5 and 1.24.4) of the package until a secure version is confirmed. It is advisable to monitor the package repository for updates and announcements regarding the vulnerability.

Conclusion

The discovery of malicious code in the @postman/pm-bin-windows-x64 package highlights the importance of maintaining secure dependencies in software development. Users are urged to take immediate action by updating to a secure version and utilizing tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for @postman/pm-bin-windows-x64 →

Share this vulnerability

FAQ

The malicious code can compromise system security, potentially leading to unauthorized access or data breaches.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

It is recommended to update the package to the latest secure version as soon as possible.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities using just your package-lock.json file.

Detailed information can be found in the vulnerability report from Amazon Inspector and the package's official repository.

How To Fix

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

npm uninstall @postman/pm-bin-windows-x64

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