Bitwarden CLI npm Package Hijacked to Steal Developer Credentials

Executive Summary

Bitwarden's official CLI package on the npm registry was briefly compromised on April 22, 2026, after attackers published a malicious version of @bitwarden/cli designed to steal developer credentials and propagate to other projects. The rogue package was live for several hours before Bitwarden revoked it. The incident underscores the persistent risk of supply-chain attacks targeting the npm ecosystem, particularly against widely used developer tools.

Technical Analysis

According to BleepingComputer, the malicious @bitwarden/cli package contained a credential-stealing payload that targeted environment variables, configuration files, and stored tokens. The malware was capable of exfiltrating credentials and spreading to other projects on the same system, amplifying the potential blast radius. The package was published under the same name as the legitimate Bitwarden CLI, making it difficult for developers to distinguish the rogue version without verifying checksums or package signatures.

Bitwarden confirmed the compromise and revoked the malicious package after detection. The company has not disclosed the exact method by which the attackers gained access to the npm publishing credentials, nor the specific version number of the compromised release. The incident follows a pattern of supply-chain attacks targeting npm packages, including the recent Checkmarx KICS compromise that affected Docker images and VS Code extensions.

Mitigations & Recommendations

Developers who installed or updated the @bitwarden/cli package between April 22 and the time of revocation should immediately rotate all credentials stored in the affected environment, including API keys, SSH keys, and cloud provider tokens. Teams should audit npm package integrity by comparing checksums against Bitwarden's official release signatures. Organizations should implement npm package pinning, use integrity verification (e.g., npm audit with --audit-level=critical), and restrict automated CI/CD pipeline updates to trusted registries. Bitwarden recommends using the official GitHub releases or verifying package hashes before installation.