Critical Malicious Code Vulnerability in scenes-e2e Package
Summary
MAL-2025-6196: Malicious code in scenes-e2e (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 scenes-e2e package is an npm library designed for end-to-end testing of web applications. It provides tools and utilities to simulate user interactions and validate application behavior. However, this package has been identified to contain malicious code that compromises the security of systems where it is installed.
Vulnerability Detail
The vulnerability originates from embedded malicious code within the scenes-e2e 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 ramifications of this vulnerability are severe, as it can lead to 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 scenes-e2eIf 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, you can temporarily disable the functionality that relies on the scenes-e2e package while you assess the impact and remove the package. This can be done by commenting out the relevant import statements in your code and ensuring that your application does not call any functions from the package.
Conclusion
The scenes-e2e package contains malicious code that poses a significant security risk. It is essential to remove the package and rotate any compromised secrets. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.
See every vulnerability recorded for scenes-e2e →
FAQ
Immediately remove the scenes-e2e package from your project and rotate any sensitive information that may have been compromised.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
Keeping the scenes-e2e package can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.
Currently, there is no patched version available. The best course of action is to remove the package entirely.
Vulert uses the package-lock.json file to monitor your dependencies for vulnerabilities and provides real-time alerts, ensuring your application remains secure.
