npm package report

Is @bitwarden/cli safe?

Version 2026.4.0 of @bitwarden/cli was compromised (ci workflow compromise). Other versions are not flagged as malicious.

Do not install @bitwarden/cli 2026.4.0

CRITICALanalyst verified

Ci workflow compromise, part of the bitwarden-cli-gha-compromise-2026-04 campaign. Added to CyberXYZ 2026-04-23, verified by a CyberXYZ analyst.

// what we observed

@bitwarden/cli@2026.4.0 shipped a malicious preinstall hook (bw1.js) after the project's GitHub Actions publish workflow was compromised. The loader fetches and evaluates a remote payload at install time that exfiltrates environment variables, ~/.npmrc, ~/.aws/credentials, SSH keys, and browser cookies; it also appends a persistence hook to ~/.bashrc and ~/.zshrc. A locale kill-switch skips execution on ru-* systems. This version added a preinstall hook where prior legitimate versions had none (republishing signal).

entry vector
github_actions_workflow_compromise
kill switch locale
ru
// versions and what to do
Malicious
2026.4.0
Move to
2026.10.1 newest 2026.x release, no known advisory

If one of these versions was installed, remove it and treat the credentials, tokens and SSH keys on that machine as exposed: rotate them. Check CI runners and container images that installed it too.

npm install @bitwarden/cli@2026.10.1
// reach

0 direct dependencies

none carry a known advisory

    1 packages depend on it

    an advisory here reaches each of them

    Create a free accountfor every dependency path, dependent and what to upgrade
    // ai model usage

    Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.



    Checked 2026-10-31 at 00:03 UTC. Updated continuously from NVD, GHSA, OSV and CNA feeds.

    Think a verdict here is wrong? Tell us — we respond within 2 business days.