Critical Malicious Code Vulnerability in pool-check Package
Summary
MAL-2026-1152: Malicious code in pool-check (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The pool-check package is an npm module designed for checking the status of various pools in a software environment. It is often utilized in applications that require monitoring of resource availability. However, this package has been compromised, leading to significant security concerns for users who have it installed.
Vulnerability Detail
The vulnerability stems from the presence of malicious code embedded within the pool-check package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this issue is linked to a malicious actor who has inserted harmful code into the package, making it a severe threat to users and their systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall pool-check
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 avoid using the pool-check package altogether and consider alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your environment is secured and monitor for any unusual activity.
Conclusion
The pool-check package has been compromised with malicious code, posing a serious threat to users. Immediate action is required to uninstall the package and secure any sensitive information. Users are encouraged to explore alternative packages and utilize tools like Vulert for ongoing vulnerability monitoring.
See every vulnerability recorded for pool-check →
FAQ
Immediately uninstall the package using npm uninstall pool-check 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 needing to sign up.
Keeping the package installed poses a significant risk as it allows malicious actors to gain unauthorized access to your system and sensitive data.
Yes, consider using other npm packages that provide similar functionality but are known to be secure and free from malicious code.
Vulert monitors and alerts users in real-time for open-source vulnerabilities in their software by analyzing the package-lock.json file.