Critical Malicious Code Vulnerability in opencode2 Package

opencode2 Updated 14 Oct 2026

Summary

13/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17852: Malicious code in opencode2 (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 package is a Node.js library designed for various functionalities within JavaScript applications. It is commonly used in web development for its ease of integration and utility functions. However, this package has been identified as containing malicious code that compromises the security of any system it is installed on, making it a significant risk for developers and organizations relying on it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the opencode2 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 implications of this vulnerability are severe, as it poses a risk of data breaches and unauthorized control over affected systems. The malicious code is embedded in the package and is designed to operate without the user's knowledge.

How To Fix

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

npm uninstall opencode2

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

Currently, there are no effective workarounds to mitigate the risks posed by the opencode2 package. The only recommended action is to uninstall the package and secure any sensitive information that may have been compromised.

Conclusion

The opencode2 package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to uninstall the package and secure any sensitive information. Monitoring tools like Vulert can help keep your applications safe from future vulnerabilities.

See every vulnerability recorded for opencode2 →

Share this vulnerability

FAQ

opencode2 is a Node.js library used for various functionalities in JavaScript applications, but it has been found to contain malicious code.

The malicious code can fully compromise your system, allowing unauthorized access to sensitive information and control over your computer.

You should uninstall the opencode2 package immediately and rotate any secrets or keys stored on the affected system.

No, there is currently no patched version available for the opencode2 package. The only solution is to remove it completely.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

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

npm uninstall opencode2

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