Bitwarden CLI Hacked in Supply Chain Attack

Bitwarden’s Command Line Interface (CLI) was compromised on April 23, 2026 , in an incident tied to an ongoing software supply chain campaign identified by Checkmarx. The affected tool is used to manage passwords and other sensitive information, and officials said the intrusion involved inserting malicious code into the CLI during its build process.

According to the description of the incident, the compromise stemmed from a dependency confusion attack aimed at the Bitwarden CLI. In this technique, an attacker registers a malicious package with a name that closely resembles a legitimate internal dependency. The malicious package can then be pulled into automated builds by mistake, creating a pathway for unauthorized code to enter a software release.

In this case, the attacker’s package was inadvertently included in the CLI’s build pipeline, enabling the injection of code designed to exfiltrate sensitive user data to an external server. The data at risk was described as including environment variables and potentially vault data, underscoring the sensitivity of the information that can be handled through command-line workflows and automated environments.

After the issue was identified, Bitwarden released an urgent update intended to address the vulnerability. The company advised users to update their CLI installations immediately, reflecting the risk that compromised tooling can pose when it is embedded into developer workflows, automation scripts, and operational processes that may have access to secrets.

The incident was presented as part of a broader pattern of supply chain threats, where weaknesses in third-party components, package ecosystems, or development processes can be leveraged to reach downstream users. Checkmarx identified the campaign as ongoing, indicating that similar tactics may be used against other software projects that rely on dependencies and automated builds.

What remains uncertain from the available details is the full scope of exposure among users, including how many installations may have been affected and whether any exfiltration attempts succeeded. The description also does not specify which internal dependency name was imitated, or how long the malicious package may have been available before discovery.

For global markets and international stakeholders, the episode reinforces how supply chain compromises can quickly become cross-border issues when widely used software is involved. Organizations operating across jurisdictions often depend on shared tooling and package repositories, meaning a single compromised component can create operational and security risks that propagate internationally.