People search DigiCert data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 1 DigiCert-linked incident. This page maps every attested event through 2026 with internal links to canonical records.
Why DigiCert breach history matters
DigiCert operates in Technology (United States). Across indexed rows, recurring themes include credential theft and social engineering. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2026 — support-channel social engineering; unauthorized EV code-signing certificates (Apr)
Cataloged incident. DigiCert reported that on April 2, 2026 its customer-support channel was targeted by social engineering: a threat actor delivered a malicious ZIP disguised as a screenshot containing a .scr screensaver installer. The attacker abused a limited support-portal function that lets analysts view customer accounts to harvest initialization codes for approved pending orders, ultimately compromising two support endpoints—one contained within 24 hours, a second remaining undetected for almost two weeks due to endpoint-protec Exposed categories include Unauthorized EV code-signing certificates (revoked); internal support systems—no mass consumer credential database cited. No attested victim count is published for this row yet. See the digicert-ev-code-signing-support 2026 re and canonical BreachHistory entry.
Patterns and analysis
- Credential theft and social engineering — appears across multiple DigiCert 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 DigiCert company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/digicert · Latest: digicert-ev-code-signing-support2026.
Sources: BreachHistory catalog (1 row for DigiCert), company and regulator disclosures cited in individual breach records.