There have been multiple reports that the npm package @bitwarden /cli has been compromised in version 2026.4.0:
Has there been any official confirmation from the Bitwarden team?
grb
April 23, 2026, 2:14pm
2
I am a volunteer moderator here (i.e., a Bitwarden user, not an employee), so this is not an official confirmation, but I wanted to share with you that mods have received information that Bitwarden has taken action on this and will be making some kind of public announcement. Stay tuned…
grb
April 23, 2026, 2:23pm
3
This Github comment has the first official response from a Bitwarden rep:
opened 12:12PM - 23 Apr 26 UTC
bug
cli
### Steps To Reproduce
Source: https://x.com/JFrogSecurity/status/204726857607… 1991766
JFrog Security states on X:
"The Checkmarx TeamPCP campaign has now spread to npm! Package @bitwarden/cli (78K weekly downloads) v2026.4.0 steals GitHub/npm tokens, .ssh, .env, shell history, GitHub Actions and cloud secrets, then exfiltrates the data to private domains & as GitHub commits"
Since Bitwarden cli shares its repo with all other clients, I am at least concerned.
### Expected Result
---
### Actual Result
---
### Screenshots or Videos
_No response_
### Additional Context
_No response_
### Operating System
macOS
### Operating System Version
_No response_
### Shell
Bash
### Build Version
2026.4.0
### Issue Tracking Info
- [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
“We verified that a malicious version of CLI was published to NPM as 2026.4.0. We have since deprecated that version and contacted NPM for its removal.”
grb
April 23, 2026, 3:09pm
4
And now there is a slightly more detailed statement, in a pinned post on the forum:
The Bitwarden security team identified and contained a malicious package that was briefly distributed through the npm delivery path for @bitwarden/cli@2026.4.0 between 5:57 PM and 7:30 PM (ET) on April 22, 2026, in connection with a broader Checkmarx supply chain incident.
The investigation found no evidence that end user vault data was accessed or at risk, or that production data or production systems were compromised. Once the issue was detected, compromised access was revoked, the malicious …
eck
(Adam Eckerle)
April 23, 2026, 3:17pm
6
Closing this topic and encourage people to continue the discussion in the pinned topic @grb linked above.