Critical Malicious Code Vulnerability in pump.js Package

pump.js Updated 27 Jan 2026

Summary

27/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-541: Malicious code in pump.js (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The pump.js package is a widely used Node.js module that facilitates the piping of streams in a simple and efficient manner. It is often utilized in various applications for handling data streams, making it a crucial component in many Node.js projects. However, the recent discovery of malicious code within this package poses a significant threat to users and their systems.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code in the pump.js package, which has been identified as a serious security risk. Any system that has this package installed is considered fully compromised, potentially allowing unauthorized access to sensitive information such as secrets and keys. The malicious code can lead to severe ramifications, including data breaches and loss of control over the affected systems.

How To Fix

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

npm uninstall pump.js

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 workaround, users should ensure that the pump.js package is uninstalled from their projects. You can do this by running the following command: npm uninstall pump.js. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the pump.js package highlights the importance of vigilance in managing open-source dependencies. Users must take immediate action to remove the compromised package and secure their systems to prevent potential data breaches.

See every vulnerability recorded for pump.js →

Share this vulnerability

FAQ

pump.js is a Node.js module used for piping streams, allowing for efficient data handling in applications.

You can check if your application is affected by using the Vulert playground at Vulert Scanner, which monitors vulnerabilities in your package-lock.json file.

If you have installed pump.js, you should immediately uninstall it and rotate any sensitive information stored on your system.

Currently, there is no patched version available. The best course of action is to remove the package entirely.

Vulert provides real-time monitoring and alerts for open-source vulnerabilities in your software, using just your package-lock.json file.

How To Fix

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

npm uninstall pump.js

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