Supply Chain Attacks Target Checkmarx and Bitwarden Developer Tools
On April 22, 2026, Checkmarx and Bitwarden suffered supply chain attacks where malicious versions of their developer tools were distributed through official channels, attempting to harvest sensitive information such as GitHub and npm tokens and exfiltrating data to audit.checkmarx[.]cx.
On April 22, 2026, Checkmarx and Bitwarden experienced supply chain attacks where threat actors compromised their distribution channels to deliver malicious versions of their developer tools. Checkmarx KICS, a security scanner, was affected via tampered images on Docker Hub (tags v2.1.20-debian, v2.1.20, debian, alpine, latest, v2.1.21), malicious extensions on Open VSX (cx-dev-assist versions 1.17.0, 1.19.0 and ast-results versions 2.63.0, 2.66.0), and a malicious release on GitHub Actions (tag 2.3.35). The Bitwarden CLI was compromised with a trojanized version 2026.4.0 published to npm. The attackers aimed to steal credentials, including GitHub and npm tokens, SSH keys, cloud provider credentials, and AI assistant configurations, exfiltrating the data to audit.checkmarx[.]cx (94.154.172[.]43). These attacks highlight the risk of compromised software supply chains and the potential for widespread data theft.
Attack Chain
- Attacker compromises the CI/CD pipeline or distribution channel of Checkmarx and Bitwarden.
- Malicious KICS images are pushed to Docker Hub with tampered Go binaries.
- Checkmarx extensions on Open VSX are modified to include a hidden ‘MCP addon’ feature, downloading and executing a payload from a hardcoded GitHub URL.
- A malicious release (2.3.35) is tagged on the ast-github-action repository.
- The trojanized @bitwarden/cli version 2026.4.0 is published to npm.
- The malicious payloads harvest sensitive information, including GitHub tokens, npm tokens, AWS/Azure/GCP credentials, SSH keys, environment variables, and AI configuration files.
- Stolen GitHub tokens are used to inject malicious workflows into victim repositories.
- Collected data is encrypted and exfiltrated to audit.checkmarx[.]cx.
Impact
The attacks on Checkmarx and Bitwarden developer tools could have severe consequences. A stolen cloud credential or GitHub token from a developer’s machine can be a foothold for an entire production infrastructure. The compromise of Bitwarden CLI could lead to exposure of stored passwords. Successful exfiltration of sensitive data from development environments allows attackers to access and control critical systems, potentially leading to data breaches, financial loss, and reputational damage. The Bitwarden CLI package draws more than 70,000 weekly downloads, indicating a potentially wide impact.
Recommendation
- Monitor network connections for outbound traffic to the C2 domain
audit.checkmarx[.]cx(IOC - Domain). - Inspect running containers for the presence of tampered KICS images based on the affected Docker Hub tags (IOC - Docker Hub).
- Implement integrity checks for dependencies installed via npm, specifically flagging the compromised
@bitwarden/cliversion 2026.4.0 (IOC - npm). - Deploy the Sigma rule to detect processes executing javascript downloaded from unusual github URLs.
- Review GitHub Action workflows for suspicious modifications or injections using stolen tokens, as described in the attack chain.
Detection coverage 2
Detect Javascript Execution from Unusual Github URL
mediumDetects javascript execution via bun or node after being downloaded from a githubusercontent.com URL
Detect Exfiltration to audit.checkmarx[.]cx
highDetects network connections to the audit.checkmarx[.]cx domain, potentially indicating exfiltration of stolen data.
Detection queries are available on the platform. Get full rules →
Indicators of compromise
1
domain
| Type | Value |
|---|---|
| domain | audit.checkmarx[.]cx |