Critical Malicious Code Vulnerability in @bugdtest/test1 Package
Summary
MAL-2025-192963: Malicious code in @bugdtest/test1 (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 @bugdtest/test1 package is an npm library that is utilized in various JavaScript applications for testing purposes. It is designed to facilitate developers in creating and running tests efficiently. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on, making it a significant threat to developers and organizations relying on it.
Vulnerability Detail
The vulnerability originates from embedded malicious code within the @bugdtest/test1 package. This code can fully compromise any computer that has the package installed or running, allowing unauthorized access to sensitive information, including secrets and keys. The ramifications of this vulnerability are severe, as it can lead to data breaches and loss of control over the affected systems. Users are advised to treat any system with this package as compromised and take immediate action.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @bugdtest/test1If 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 and securing the system. Users should ensure that all sensitive information is rotated and that the system is scanned for any residual malicious software.
Conclusion
The @bugdtest/test1 package poses a critical security risk due to embedded malicious code. Users must act swiftly to remove the package and secure their systems. Regular monitoring for vulnerabilities using tools like Vulert can help prevent future incidents.
See every vulnerability recorded for @bugdtest/test1 →
FAQ
Immediately remove the package and rotate any sensitive information stored on the affected system.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Currently, there is no patch available. The best course of action is to remove the package and secure your system.
Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and loss of control over your systems.
Vulert monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file, allowing you to stay informed about potential threats.
