Critical Malicious Code Vulnerability in opencode2-linux-x64-musl Package

opencode2-linux-x64-musl Updated 14 Oct 2026

Summary

13/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17858: Malicious code in opencode2-linux-x64-musl (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-musl package is an npm package designed for Linux environments, providing various functionalities for developers. However, it has been identified as containing malicious code, posing a significant security risk to any system where it is installed. This vulnerability compromises the integrity of the system, potentially allowing unauthorized access and control.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the opencode2-linux-x64-musl package. Any system running this package is considered fully compromised, with all stored secrets and keys at risk. The malicious code can lead to unauthorized access, data breaches, and further exploitation of the system. 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 opencode2-linux-x64-musl

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

As a workaround, if you need similar functionality, consider using alternative packages that do not have known vulnerabilities. Always verify the integrity of packages before installation.

Conclusion

The opencode2-linux-x64-musl package contains malicious code that poses a severe security risk. Immediate action is required to remove the package and secure any compromised systems. Users should remain vigilant and utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for opencode2-linux-x64-musl →

Share this vulnerability

FAQ

Immediately uninstall the opencode2-linux-x64-musl package and rotate any secrets or keys stored on the affected system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

Failing to address this vulnerability can lead to unauthorized access, data breaches, and potential control of your system by malicious actors.

Yes, Vulert provides a service that monitors your package-lock.json file for open-source vulnerabilities in real-time.

While many npm packages are safe, always verify the source and integrity of packages before installation to minimize risks.

How To Fix

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

npm uninstall opencode2-linux-x64-musl

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