Critical Malicious Code Vulnerability in bingo-logger Package
Summary
MAL-2025-6216: Malicious code in bingo-logger (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 bingo-logger package is an npm library designed for logging purposes in JavaScript applications. It provides developers with a simple interface to log messages, errors, and other information to various outputs. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on.
Vulnerability Detail
The vulnerability stems from embedded malicious code within the bingo-logger package. This code can lead to complete compromise of any computer running the package, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code has been confirmed by security researchers, and it poses a significant risk to users and their data.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall bingo-loggerIf 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 entirely. Ensure that you check your package-lock.json file for any instances of bingo-logger and remove it from your dependencies.
Conclusion
The bingo-logger package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to remove the package and secure any compromised systems. Users are advised to monitor their applications for vulnerabilities using tools like Vulert.
See every vulnerability recorded for bingo-logger →
FAQ
You should immediately remove the bingo-logger package from your project and rotate any sensitive information stored on the affected system.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
Using the bingo-logger package can lead to unauthorized access to your system, data theft, and potential control by malicious entities.
While removing the package is essential, there is no guarantee that all malicious software will be eliminated. It is crucial to perform a thorough security audit and rotate all secrets.
If a patched version is released, updating may resolve the vulnerability. However, due to the severity of the compromise, immediate removal is recommended.
