Critical Malicious Code Vulnerability in opencode2-windows-arm64 Package

opencode2-windows-arm64 Updated 14 Oct 2026

Summary

13/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17859: Malicious code in opencode2-windows-arm64 (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-windows-arm64 package is an npm package designed for Windows ARM64 architecture. It is typically used to facilitate various functionalities in applications that run on this platform. However, this package has been compromised, leading to significant security risks for any system that has it installed.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the opencode2-windows-arm64 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 origin of this issue is linked to the package being flagged as malicious by security researchers, indicating that it poses a severe threat to users and their data.

How To Fix

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

npm uninstall opencode2-windows-arm64

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 this vulnerability other than removing the package entirely. It is essential to monitor your system for any signs of compromise after the package has been uninstalled.

Conclusion

The opencode2-windows-arm64 package poses a critical security risk due to the embedded malicious code. Immediate action is required to uninstall the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for opencode2-windows-arm64 →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any sensitive information stored on your system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

No, there is currently no patched version available for this package.

Failing to remove the package could lead to unauthorized access to your system, compromising sensitive data and potentially allowing further malicious activities.

Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software, providing an easy way to stay informed.

How To Fix

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

npm uninstall opencode2-windows-arm64

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