INGRAM MICRO INC.
bd_2d49c4f0e0bc40fc · schema v1 · pii pii-v1
Full breach record for INGRAM MICRO INC. →2 incidents on fileIngram Micro Inc. reported an external system breach (hacking) occurring July 2-3, 2025, discovered December 26, 2025. 42,521 individuals affected, including 5 Maine residents. Employment and job applicant records containing PII and government IDs were accessed. The company engaged cybersecurity experts, notified law enforcement, and offered 24 months of credit monitoring.
J jump to incidentP pin to compareR raw source
Incident timeline
Jul 2, 2025
Begins
Dec 26, 2025
Discovered
Jan 16, 2026
Filed
vs. sector median
8 wks faster
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Sitesafepaybd_97326dee4e65ed902025-07-29 · +170dVerified by operator
Regulatory filings (8) · sorted by filing gap
- California State AGbd_0c948d47559f2f842026-01-16Verified
- Vermont State AGbd_1b20f97ec00dda792026-01-16Verified
- Indiana State AGbd_6eb764c4140067392026-01-16Verified
- Nebraska State AGbd_f2bbb189422c98512026-01-16Verified
Show 4 more filings ↓Show fewer ↑up to 15d gap
- Massachusetts State AGbd_0de697dc55ff50ec2026-01-17 · +1dVerified
- Texas State AGbd_7837f481c3fe62e82026-01-21 · +5dVerified
- New Hampshire State AGbd_eee1ae1379bcb8152026-01-23 · +7dVerified
- Illinois State AGbd_6020002ac5880d962026-01-01 · +15dCandidate
Filing propagation · 9 filings · 9 states
View merged incident ↗Pattern: first filing Jan 1 (IL), last Jan 23 (NH) — a 22-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.