Malicious code in @beloved-lenora/opencode-shell-guard (npm)
Published Sources: OSV (Schadpakete)
- Malicious package
What is affected, what to do
Uninstall the package, isolate affected environments and rotate credentials that were available during installation.
Not sure whether and how you are affected? Ask a question about this vulnerability
Malicious package
npm@beloved-lenora/opencode-shell-guard
“@beloved-lenora/opencode-shell-guard” is registered as malicious in the npm repository. Anyone who installed the package should uninstall it immediately, isolate affected environments and rotate credentials that were present during installation.
Affected versions (2)
- 1.0.3
- 1.0.4
purl: pkg:npm/%40beloved-lenora/opencode-shell-guard
Sources (3)
ghsa-malware
GHSA-pm76-w63j-7j29sha256: 122dea54602061507a3752f709f1e910d9126fdaf9fb282aeab13caca388b3e6
amazon-inspector
IN-MAL-2026-021520Versions from this source: 1.0.4
sha256: 57da70f7efcc98515e5d5619ad18d558d39c772820ae1c6926b0081af6a0e6dd
amazon-inspector
IN-MAL-2026-021527Versions from this source: 1.0.3
sha256: ff8dd8daa41992a2f1dec185b6924f6cc81b7172b55cccd6930f062317984ba8
The OSSF `malicious-packages` namespace lists packages flagged as malicious by static analysis or sandbox detonation. An entry here is a confirmed finding, not a suspicion.
Metrics
—
Priority
No value is available for this vulnerability.
—
CVSS v3
No value is available for this vulnerability.
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 30.00 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (ff8dd8daa41992a2f1dec185b6924f6cc81b7172b55cccd6930f062317984ba8)
The package presents itself as a safety guard that reviews shell commands before execution, but contains an undocumented branch that activates when the user's command contains npm run build. On that trigger it bypasses its own review logic, retrieves an encrypted payload and key via UnsealRpc.unseal({}) from the sibling package @beloved-lenora/opencode-shared-rpc, AES-256-CBC decrypts the ciphertext, writes the plaintext to a randomized hidden path under ~/Library/Application Support/.k7Qm2/vX9pL4.sh, and rewrites the user's command to (npm run build || bash '<staged>') || rm -f '<staged>', executing the staged script as a fallback and self-deleting it afterward. The capability (opaque remote-sourced code execution via a sibling package), the hidden dot-directory staging path, and the post-execution file removal are absent from the plugin's documentation and are concealed behind a cover of local command review. Whoever controls @beloved-lenora/opencode-shared-rpc controls arbitrary shell code that will run on the host of any user of this guard whenever they invoke a npm run build command.
Source: ghsa-malware (122dea54602061507a3752f709f1e910d9126fdaf9fb282aeab13caca388b3e6)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.