A malicious version of the Bitwarden CLI was distributed via npm for 93 minutes on April 22. The attack, linked to a broader supply chain campaign, targeted infrastructure credentials rather than vault data, highlighting critical vulnerabilities in CI/CD release pipelines.
On April 22, 2026, a malicious version of Bitwarden's CLI was published to npm under the official @bitwarden/cli package name for 93 minutes. The backdoored package targeted infrastructure credentials including GitHub tokens, SSH keys, AWS/GCP/Azure credentials, and GitHub Actions secrets rather than Bitwarden vaults. Bitwarden removed the package and found no evidence of vault data access. Security researchers determined the attack exploited a compromised GitHub Action in Bitwarden's CI/CD pipeline, connected to the broader Checkmarx supply chain campaign.
On April 22, 2026, a malicious version of Bitwarden's command-line interface was published to npm under the official package name @bitwarden/[email protected], remaining available for 93 minutes. The compromised package targeted infrastructure credentials including GitHub tokens, npm tokens, SSH keys, AWS/GCP/Azure credentials, and GitHub Actions secrets. Security firm JFrog analyzed the payload and found it had no interest in Bitwarden vaults—only in credentials governing build, deployment, and infrastructure automation. Bitwarden confirmed the incident is connected to the broader Checkmarx supply chain campaign and found no evidence of end-user vault access or production system compromise.
Das npm-Paket @bitwarden/cli wurde zwischen dem 22. und 23. April 2026 mit einem Credential-Stealer infiziert. Die kompromittierte Version 2026.4.0 lud die Bun-Runtime herunter und exfiltrierte GitHub-Tokens, SSH-Schlüssel, AWS-, Azure- und GCP-Zugangsdaten sowie KI-Tool-Konfigurationen. Bitwarden betont, dass Vault-Daten nicht betroffen waren. Alle Nutzer sollten betroffene Systeme bereinigen und Zugangsdaten rotieren.
