CampaignsPublisher / pipeline compromise
@bitwarden/cli 2026.4.0 published through a poisoned Checkmarx GitHub Action
- Taken downas of
- Moderate confidence
- Indicators (4): CSV, JSON
- Seen to
Do this now
- Upgrade to 2026.4.1 or later and rotate secrets on hosts that installed 2026.4.0
- Audit workflows for Checkmarx action references used in Mar-Apr 2026 and pin by SHA
- Block the exfil domain
Indicators to check
Look for any of these on your machines or in your logs:
- package
@bitwarden/cli@2026.4.0
What happened
A compromised Checkmarx GitHub Action in Bitwarden's release pipeline let the attacker publish a malicious @bitwarden/cli 2026.4.0 through the trusted OIDC path, and it was live for about 1.5 hours. A preinstall-triggered payload stole tokens, SSH keys, cloud credentials and AI-tool configs, and sent them to a Checkmarx-themed domain and to GitHub repos labelled 'Shai-Hulud: The Third Coming'.
- npm
- GitHub Actions
Attack chain
-
Lure
No lure; users trusted an official, OIDC-published release
First seen
-
Artifact
@bitwarden/cli@2026.4.0 (bw1.js, bwsetup.js)
-
Actor
No source we cite attributes this activity to an actor.
-
Infrastructure
- Checkmarx-lookalike exfil domain
- GitHub commit-search dead drop
Last seen
Timeline
- First seen
- Endor Labs reports
- The Hacker News reports
- Last seen
- Status checked: Taken down
Related campaigns
| Type | Value | Copy |
|---|---|---|
| package | @bitwarden/cli@2026.4.0 | |
| domain | audit[.]checkmarx[.]cx | |
| ip | 94[.]154[.]172[.]43 | |
| sha256 | 18f784b3bc9a0bcdcb1a8d7f51bc5f54323fc40cbd874119354ab609bef6e4cb |
Confidence: Moderate
Strong evidence, not yet confirmed by our own analysis. See the confidence scale for what each level requires. The sources below are the evidence.
Sources
Notes
- Some researchers link this to TeamPCP; Endor Labs does not, so the actor is null.
Corrections
No corrections.
See the corrections policy. Spotted an error? Tell us.