Bitwarden CLI was compromised in a supply chain attack tied to the ongoing Checkmarx campaign, according to JFrog and Socket. The affected release was **@bitwarden/cli@2026.4.0**, which contained malicious code in **bw1.js** and was briefly distributed through npm on **April 22, 2026**. Bitwarden said the malicious package was available only for a short window and that users who did not download it during that time were not affected.
The attack reportedly began with a **compromised GitHub Action** in Bitwarden’s CI/CD pipeline. The malicious code ran through a **preinstall hook**, stealing sensitive data such as **GitHub and npm tokens, SSH keys, .env files, shell history, cloud secrets, and AI coding tool credentials** from tools like Claude, Cursor, Codex CLI, and Aider. The stolen data was encrypted and exfiltrated to a fake Checkmarx domain, **audit.checkmarx[.]cx**, with GitHub used as a fallback. If GitHub tokens were found, attackers could inject malicious workflows into repositories and expand access to CI/CD secrets.
Security researchers said this was one of the most capable npm supply chain payloads seen so far. Bitwarden confirmed the incident, revoked compromised access, deprecated the malicious release, and issued **@bitwarden/cli@2026.4.1** as a safe re-release of version 2026.3.0. The company also said there was **no evidence of end-user vault data exposure or production system compromise**. Users who installed 2026.4.0 are advised to uninstall it, clear npm cache, rotate exposed secrets, review GitHub and CI activity, and upgrade to 2026.4.1.
Article timeline
Build this article’s timeline
Extract dated events, key actors, and open questions using the same timeline analysis available in Signal.
Comments
Login to view and post comments.