Checkmarx Confirms Data Stolen in Supply Chain Attack
The hackers exfiltrated the data from Checkmarx’s GitHub environment on March 30, a week after publishing malicious code. The post Checkmarx Confirms Data Stolen in Supply Chain Attack appeared first on SecurityWeek .
AI Analysis
Technical Summary
In March 2026, Checkmarx's GitHub environment was compromised following a supply chain attack originating from the Trivy incident. Attackers hijacked GitHub Action version tags and poisoned OpenVSX plugins to inject malware without visible code changes. The threat actors, linked to TeamPCP and Lapsus$, accessed sensitive data including source code and credentials. Despite initial remediation steps, attackers maintained or regained access, continuing to publish malicious code and ultimately leaking a 96GB archive of stolen data. Checkmarx responded by removing malicious packages, rotating credentials, blocking attacker infrastructure, notifying law enforcement, retaining Mandiant for investigation, and conducting a code audit. The company reports the breach is contained and is completing its investigation.
Potential Impact
The attack resulted in the theft of sensitive data including source code, employee databases, API keys, and database credentials from Checkmarx's GitHub repositories. The compromise affected the integrity of open source software supply chains and exposed critical internal assets. The public leak of a large data archive increases the risk of further exploitation or secondary attacks. The incident also impacted the Bitwarden CLI NPM package, a widely used open source password management tool, potentially affecting its users.
Mitigation Recommendations
Checkmarx has removed malicious packages, revoked and rotated compromised credentials, blocked outbound access to attacker infrastructure, and locked down GitHub repository access. The company has engaged law enforcement and cybersecurity experts (Mandiant) and is conducting a thorough code audit. These remediation steps have contained the unauthorized access. Organizations using affected open source components should monitor vendor advisories for updates. Patch status is not explicitly stated; check Checkmarx advisories for ongoing remediation guidance.
Checkmarx Confirms Data Stolen in Supply Chain Attack
Description
The hackers exfiltrated the data from Checkmarx’s GitHub environment on March 30, a week after publishing malicious code. The post Checkmarx Confirms Data Stolen in Supply Chain Attack appeared first on SecurityWeek .
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In March 2026, Checkmarx's GitHub environment was compromised following a supply chain attack originating from the Trivy incident. Attackers hijacked GitHub Action version tags and poisoned OpenVSX plugins to inject malware without visible code changes. The threat actors, linked to TeamPCP and Lapsus$, accessed sensitive data including source code and credentials. Despite initial remediation steps, attackers maintained or regained access, continuing to publish malicious code and ultimately leaking a 96GB archive of stolen data. Checkmarx responded by removing malicious packages, rotating credentials, blocking attacker infrastructure, notifying law enforcement, retaining Mandiant for investigation, and conducting a code audit. The company reports the breach is contained and is completing its investigation.
Potential Impact
The attack resulted in the theft of sensitive data including source code, employee databases, API keys, and database credentials from Checkmarx's GitHub repositories. The compromise affected the integrity of open source software supply chains and exposed critical internal assets. The public leak of a large data archive increases the risk of further exploitation or secondary attacks. The incident also impacted the Bitwarden CLI NPM package, a widely used open source password management tool, potentially affecting its users.
Mitigation Recommendations
Checkmarx has removed malicious packages, revoked and rotated compromised credentials, blocked outbound access to attacker infrastructure, and locked down GitHub repository access. The company has engaged law enforcement and cybersecurity experts (Mandiant) and is conducting a thorough code audit. These remediation steps have contained the unauthorized access. Organizations using affected open source components should monitor vendor advisories for updates. Patch status is not explicitly stated; check Checkmarx advisories for ongoing remediation guidance.
Technical Details
- Article Source
- {"url":"https://www.securityweek.com/checkmarx-confirms-data-stolen-in-supply-chain-attack/","fetched":true,"fetchedAt":"2026-04-29T11:06:22.348Z","wordCount":1056}
Threat ID: 69f1e62ecbff5d8610fb0e7b
Added to database: 4/29/2026, 11:06:22 AM
Last enriched: 4/29/2026, 11:06:31 AM
Last updated: 4/30/2026, 12:27:59 AM
Views: 32
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.