Critical Malicious Code Vulnerability in opencode2-windows-x64 Package
Summary
MAL-2026-17860: Malicious code in opencode2-windows-x64 (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 opencode2-windows-x64 package is an npm package designed for Windows environments, providing various functionalities for developers. However, it has been identified as containing malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk to users, as it can lead to unauthorized access and control over affected systems.
Vulnerability Detail
The vulnerability originates from the inclusion of embedded malicious code within the opencode2-windows-x64 package. This code can fully compromise any computer that has the package installed, allowing attackers to gain control over the system. The ramifications of this vulnerability are severe, as it can lead to data breaches, loss of sensitive information, and unauthorized access to system resources. Users are advised to treat any system with this package as compromised and take immediate action to secure their data.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall opencode2-windows-x64If 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. The only recommended action is to remove the package and secure the system.
Conclusion
The opencode2-windows-x64 package has been identified as containing malicious code that poses a significant security risk. Users must take immediate action to remove the package and secure their systems. Regular monitoring for vulnerabilities, such as through Vulert, is recommended to maintain security in open-source software.
See every vulnerability recorded for opencode2-windows-x64 →
FAQ
You should immediately remove the package and rotate any secrets or keys stored on your 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.
The risks include unauthorized access to your system, potential data breaches, and loss of sensitive information.
While removing the package is essential, you should also rotate all sensitive information stored on the affected system to ensure security.
If a patched version is released, updating may resolve the issue. However, due to the nature of the compromise, it is crucial to take additional security measures.
