INGRAM MICRO INC.
ent_019e1f2024e4832f902bd0d63357d6c9
Disclosures
9
Leak Site · SEC 10-K Item 1C · State AG · SEC 8-K · 8 jurisdictions
Incidents
1
filings grouped by incident
Max affected reported
42,521
nationwide · State AG IN
Leak-site claims
1
unverified actor claims
Identity resolution
- Canonical name
- INGRAM MICRO INC.
- Normalized
- ingram micro— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- 549300KJMEWPKRQZHX63
- SEC EDGAR CIK
- 0001897762
- Domain
- None on record
Disclosure history (9)newest first
- GLOBALLeak Siteas victim2026-07-01
The Company failed to reach an agreement with us despite our incredible patience, all the chances and offers we made. They don't care. | Updated: 02 July 2026 | SHA256: f3c961b709bcff8f70dbb8361116831d2c86361754a09658115b9efed39308e5
- FEDERALSEC 10-K Item 1Cas victim2026-03-03
Ingram Micro Inc. filed Item 1C of its 10-K disclosing its cybersecurity risk management program. The filing explicitly states that no cybersecurity threats or incidents, individually or in aggregate, have materially affected the Company during the reporting periods. The document describes governance, controls, and training but confirms no specific breach occurred.
- ⛰️New Hampshire State AGas victim2026-01-23
Ingram Micro Inc. notified the New Hampshire Attorney General of a cybersecurity incident detected on July 3, 2025. An unauthorized party accessed internal file repositories between July 2 and 3, 2025, exfiltrating employment and job applicant records. Affected data included names, contact info, SSNs, driver's licenses, passport numbers, and health/insurance information. Approximately 40 New Hampshire residents (current/former employees and applicants) were notified. Ingram Micro engaged forensic experts, notified law enforcement, took systems offline, and offers two years of credit monitoring.
- ⭐Texas State AGas victim2026-01-21
Ingram Micro Inc. based in Irvine, California, a business – retail or merchant entity reported a data breach to the Texas Attorney General. The breach was discovered on 2025-12-26 and reported on 2026-01-21. 3,079 Texas residents were affected. 42,521 individuals affected in total. Types of information involved: Name of individual;Address;Social Security Number Information;Driver’s License number;Government-issued ID number (e.g. passport, state ID card);Medical Information;Health Insurance Information;Other;Date of Birth. Consumers were notified via U.S. Mail.
- 🐻California State AGas victim2026-01-16
Ingram Micro, Inc. reported a breach occurring on July 2–3, 2025. The nature of the intrusion is not described in detail in the consumer notification. Affected individuals were offered two years of complimentary Experian IdentityWorks credit monitoring and identity protection services. Notifications were sent to residents of multiple US states.
- 🍁Vermont State AGas victim2026-01-16
Ingram Micro Inc. notified Vermont AG of a cybersecurity incident detected July 3, 2025. An unauthorized third party accessed internal file repositories between July 2-3, 2025, exfiltrating employment and job applicant records containing PII, SSNs, and government IDs. Ingram Micro took systems offline, engaged cybersecurity experts, notified law enforcement, and is offering two years of credit monitoring.
- 🦞Maine State AGas victim2026-01-16
Ingram Micro Inc. identified an external system breach that occurred from July 2, 2025, to July 3, 2025. The breach was discovered on December 26, 2025, and affected 5 Maine residents. In response, the company offered 24 months of credit monitoring and identity protection services through Experian to the individuals impacted.
- 🏎️Indiana State AGas victim2026-01-16
Ingram Micro Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-07-02 and was reported on 2026-01-16. 4,136 Indiana residents were affected. 42,521 individuals affected in total.
- FEDERALSEC 8-Kas victim2025-07-07
Ingram Micro Holding Corporation filed an 8-K on July 7, 2025, reporting that it identified ransomware on certain internal systems on July 5, 2025. The company took systems offline, engaged cybersecurity experts, and notified law enforcement. The incident is active as the company works to restore systems to process and ship orders.