Critical Malicious Code Vulnerability in opencode2-linux-x64 Package

opencode2-linux-x64 Updated 14 Oct 2026

Summary

13/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17857: Malicious code in opencode2-linux-x64 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The opencode2-linux-x64 package is a Node.js library designed for various functionalities in Linux environments. It is commonly used in applications that require cross-platform compatibility and ease of integration. However, this package has been identified as containing malicious code, posing significant security risks to any system where it is installed.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the opencode2-linux-x64 package. This code can compromise the entire system, allowing unauthorized access and control to external entities. Systems running this package should be considered fully compromised, with all stored secrets and keys at risk. The malicious nature of the code is classified under CWE-506, indicating that it appears to be intentionally harmful.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall opencode2-linux-x64

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

There are no effective workarounds to mitigate the risks posed by this vulnerability. The only recommended action is to completely remove the package from your system.

Conclusion

The opencode2-linux-x64 package contains malicious code that poses a severe security threat. Immediate removal of the package and rotation of sensitive information is essential to mitigate risks. Utilizing tools like Vulert can help monitor and prevent future vulnerabilities.

See every vulnerability recorded for opencode2-linux-x64 →

Share this vulnerability

FAQ

You should immediately uninstall the package 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 without requiring any signup.

Failure to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

Regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

Vulert monitors and alerts for open-source vulnerabilities using just your package-lock.json file, providing real-time insights into your software's security.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall opencode2-linux-x64

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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback