@bitwarden/[email protected]rejectedRisk: 100SEE LICENSE IN LICENSE.txt
@bitwarden/cli@2026.4.0
rejected
This version was rejected.
It did not pass GreenFlagged's security review and is not served by the registry.
The findings and risk dispositions below explain why.
CRITICALMAL-2026-3020: Malicious code in @bitwarden/cli (npm)osv
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (c6fb2336936a86f37fc2018f8e68dc9989ffc3e79aa23297bf470de178201f50)
The package @bitwarden/cli was found to contain malicious code.
## Source: ghsa-malware (8a8c7958926d5ec3795102e9114dfaa649ae3160afb9159ec2c46f044018b776)
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.
HIGHPackage has 'preinstall' scriptinstall-scripts
Script: node bw_setup.js
HIGHMissing gitHead — previous versions had itprovenance
This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
HIGHPublisher changed: kspearrin → GitHub Actions (on 2026-04-22)provenance
This version was published by a different npm account than previous versions on 2026-04-22. This could indicate a legitimate maintainer transition or an account compromise.
HIGHNew obfuscated file: bw1.jssource-diff
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
HIGHNew file with network + code execution: bw1.jssource-diff
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
LOWNo provenance attestationprovenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
Review Summary
Risk score: 100 (capped from 289). Findings: 1 critical (+40), 5 high (+125), 4 medium (+40), 28 low (+84), 1 info (+0).