Ingram Micro Data Breach
The 2025 Ingram Micro data breach affected 42,521 people according to the Indiana Attorney General's record. The company's filing with the U.S. Securities and Exchange Commission confirms that ransomware was identified on certain internal systems.
Exposed Data Types
2 sensitive9- Medical information
- Health insurance information
- Names
- Physical addresses
- Dates of birth
- Social security numbers
- Driver's license numbers
- Government issued identification numbers
- Email addresses
About This Breach
Ingram Micro is a global technology company that provides distribution and services between technology manufacturers and cloud providers and business-to-business technology resellers. The company is headquartered in Irvine, California.
How Did the Incident Occur?
The Indiana record lists July 2, 2025, as the incident date. In a public statement dated July 5, Ingram Micro said it had identified ransomware on certain internal systems. The company secured the relevant environment by taking certain systems offline, implementing additional mitigation measures, and launching an investigation with outside cybersecurity specialists.
What Information Was Affected?
The Texas Attorney General's record indicates that the information may have varied by person. The listed types include names, addresses, dates of birth, Social Security numbers, driver's license or other government identification numbers, medical information, and health-insurance information. It does not indicate that every information type applied to every person.
How Did Ingram Micro Respond?
The company secured the relevant environment, took certain systems offline, implemented mitigation measures, and launched an investigation with leading cybersecurity specialists. It also notified law enforcement. The Indiana record shows that consumer notices were sent on January 16, 2026, while the Texas record says notices were provided by mail.
What Should Affected People Do?
Notice recipients should check their letters for the information types that apply to them and review credit reports, financial accounts, health-insurance explanations, and unexpected medical-service records. People whose Social Security or identification numbers were involved may consider a fraud alert or credit freeze based on their circumstances and should independently verify unexpected messages requesting identity information.
Verification and editorial method
LeakData compares the incident name, date, affected-record count, and exposed data types with accessible sources. Unverified fields are not presented as facts, and records are updated when new evidence becomes available.
Report missing or incorrect information
