People search Checkmarx data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 1 Checkmarx-linked incident. This page maps every attested event through 2026 with internal links to canonical records.
Why Checkmarx breach history matters
Checkmarx operates in Technology (Israel). Across indexed rows, recurring themes include credential theft and social engineering, third-party and supply-chain exposure. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2026 — LAPSUS$ leaks ~96 GB from GitHub; Trivy supply-chain pivot (Apr)
Cataloged incident. In late April 2026, Checkmarx confirmed that data the LAPSUS$ extortion group published matched material taken from its private GitHub environment, stemming from access beginning March 23, 2026. BleepingComputer and Checkmarx incident blogs described a chain where credentials exposed via the separate Trivy open-source scanner supply-chain compromise (TeamPCP–attributed) enabled interaction with Checkmarx’s GitHub org, subsequent publication of malicious artifacts (including KICS-related Docker images and editor ext Exposed categories include Source code, signing or build artifacts, and developer secrets as typical for compromised repos—customer DBs explicitly excluded in early company statements. No attested victim count is published for this row yet. See the checkmarx-lapsus-github 2026 record and canonical BreachHistory entry.
Patterns and analysis
- Credential theft and social engineering — appears across multiple Checkmarx catalog entries; prioritize controls that address this class of failure.
- Third-party and supply-chain exposure — appears across multiple Checkmarx catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Review OAuth app permissions and revoke unused third-party integrations.
- Step 5: Bookmark the Checkmarx company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/checkmarx · Latest: checkmarx-lapsus-github2026.
Sources: BreachHistory catalog (1 row for Checkmarx), company and regulator disclosures cited in individual breach records.