Critical Malicious Code Vulnerability in @beloved-lenora/opencode-orchestrator Package
Summary
MAL-2026-17905: Malicious code in @beloved-lenora/opencode-orchestrator (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 @beloved-lenora/opencode-orchestrator package is an npm library designed for orchestrating open-source code operations. It is utilized by developers to streamline workflows and manage code dependencies efficiently. However, this package has been compromised, embedding malicious code that poses significant security risks to any system using it.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the @beloved-lenora/opencode-orchestrator package. Any system running this package is considered fully compromised, allowing attackers potential access to sensitive information such as secrets and keys. The malicious code can lead to unauthorized control over the affected system, making it imperative for users to act swiftly to mitigate risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @beloved-lenora/opencode-orchestratorIf 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 other than removing the package entirely. Users should ensure that all dependencies relying on this package are also evaluated and updated as necessary.
Conclusion
The @beloved-lenora/opencode-orchestrator package has been compromised with malicious code, posing severe security risks to any system utilizing it. Immediate action is required to remove the package and secure any sensitive information. Regular monitoring of dependencies is advised to prevent future vulnerabilities.
See every vulnerability recorded for @beloved-lenora/opencode-orchestrator →
FAQ
You should immediately uninstall the package and rotate any secrets or keys stored on the affected system.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
No, there is currently no patched version available for this package.
Failing to remove the compromised package may result in unauthorized access to sensitive data and complete control of your system by malicious actors.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
