Skip to content
cisonews.net

Incident · 8-K Item 8.01

Ingram Micro ransomware attack: July 2025 outage, stolen HR files, and letters to 42,521 people

Compiled from public records. Updated 2026-11-13. By the cisonews.net Desk.

The Ingram Micro data breach affected 42,521 people, the total Ingram Micro Inc reported to Indiana's attorney general for notices sent on January 16, 2026, for a breach dated July 2, 2025. The Ingram Micro breach was a ransomware attack in July 2025, and the people who got letters about it are mostly the company's own employees and job applicants. Ingram Micro detected the attack on July 3, 2025, and later found that an outsider took files from its internal file repositories on July 2 and 3. The files held employment and job applicant records with names, dates of birth, Social Security, driver's license and passport numbers, and health information. Indiana's attorney general records 42,521 people affected in total, 4,136 of them in Indiana, with letters sent on January 16, 2026.

Entries like this one, in Wednesday’s docket

Wednesdays

Unsubscribe any time.

What happened in the Ingram Micro ransomware attack?

Ingram Micro, which calls itself a technology company for the global IT sales channel, went public with the attack on Saturday, July 5, 2025. Its press release said it had identified ransomware on some internal systems, taken certain systems offline and brought in cybersecurity experts, and that it had notified law enforcement. The company said it was working to restore the systems so that it could process and ship orders again. It filed the release with the SEC on July 7 under Item 8.01, the "other events" item, rather than Item 1.05, the item for incidents a company has judged material.

The guide to Item 8.01 and Item 1.05 explains how companies use the two items. Ingram Micro's own later account is consistent with it. In its annual report it said the attack did not cause a material interruption of its operations or materially harm its business, financial condition or reputation. It restored the affected systems from backups.

DateWhat happenedSource
July 2 to 3, 2025Files taken from internal file repositories; breach dates in California's recordLetter; California record
July 3, 2025Ingram Micro detects the incidentLetter
July 5, 2025Press release: ransomware on internal systemsPress release
July 7, 2025Form 8-K, Item 8.01SEC EDGAR
August 6, 2025Second-quarter results: no impact on the June quarterEarnings release
January 16, 2026Letters dated and sent; Indiana's notice dateLetter; Indiana record
January 17 and 21, 2026Massachusetts and Texas log the noticeMassachusetts and Texas records
March 3, 202610-K reports the response costsForm 10-K

The letters went out 197 days after detection. California's record lists the breach as July 2 and July 3, 2025. The notice-delay guide compares gaps like this across the log.

What information was stolen in the Ingram Micro breach?

The stolen files were HR files. The letter says they include employment and job applicant records, with name, contact information, date of birth, and government ID numbers such as Social Security, driver's license and passport numbers. They also include health information found in employment records, such as medical or health insurance details, and employment information such as work evaluations. What was in the files varied from person to person.

Texas's record lists name, address, Social Security number, driver's license number, government-issued ID number, medical information, health insurance information, date of birth and "other". Massachusetts marks Social Security numbers, medical records and driver's licenses for its 139 residents.

How many people were affected by the Ingram Micro breach?

Indiana's record gives the total: 42,521 people. The state counts are 4,136 in Indiana, 3,079 in Texas and 139 in Massachusetts. Indiana's is the largest of the three state counts, nearly one in ten of the total. The SEC filings used for this entry give no count of people.

What did the attack cost Ingram Micro?

The 10-K for fiscal 2025 puts a number on it. Corporate expenses for the year included $6,168 thousand (about $6.2 million) of costs for outside services and other expenses in response to the July 2025 ransomware incident. The 10-K lists the kinds of cost: investigation, remediation, system restoration and improvements to its cybersecurity program. In August 2025, the chief executive said the attack early in July had no impact on the company's June-quarter results. The cost table in the after-the-8-K guide sets figures like this one beside other companies' filings.

What is Ingram Micro offering, and was my information involved?

The letter offers two years of free credit monitoring and identity protection through Experian IdentityWorks. Questions go to 833-931-5455, Monday to Friday, 8 a.m. to 8 p.m. Central time, quoting the engagement number in the letter. The sample letter filed in California says enrollment closed on April 30, 2026, so the code in a January letter may no longer work. The guide to credit monitoring offers covers what to do when an offer has lapsed.

If you worked at Ingram Micro or applied for a job there, and you got a letter dated January 16, 2026, your records were in the stolen files. Customers and vendors are not the group the letter describes: it speaks of employment and applicant records only. If you think you should have had a letter and did not, the number above is the company's channel.

What the filings leave open

  • How the attackers got in, and which group was behind the attack.
  • Whether Ingram Micro paid a ransom.
  • Whether any customer or partner data was in the stolen files; the letter covers only HR records.
  • How the 42,521 total splits between employees and job applicants.

How this disclosure's timing compares

Ingram Micro disclosed 0 days after the discovery date its filing gives. Across the 21 other filings under 8-K Item 8.01 on cisonews.net that date discovery to the day, the median gap is 3 days.

The rule behind an Item 8.01 filing

Item 8.01 (Other Events) is the item the SEC's Division of Corporation Finance encouraged companies to use for a cybersecurity incident they have not yet determined to be material, or have determined is not material. Its May 21, 2024 statement says a company that later determines the incident is material should file under Item 1.05 within four business days of that decision. Source: U.S. Securities and Exchange Commission, statement by the Director of the Division of Corporation Finance. The guide Item 8.01 versus Item 1.05: when a cyber incident moves between them reads the rule in full, and the glossary defines Form 8-K Item 1.05.

Other technology incidents on cisonews.net

  • DreamHost, Breach notice, first disclosed November 2, 2026
  • Photon Health, Breach notice, first disclosed October 28, 2026; affected: approximately 1706 Rhode Island residents
  • Indico Data Solutions, Breach notice, first disclosed October 27, 2026; affected: 79 Rhode Island residents
  • Stitch Connect Inc, Breach notice, first disclosed September 21, 2026; affected: 113,727 people in total (Indiana AG record)
  • IDScan.net, Breach notice, first disclosed September 18, 2026; 27,624 affected in total (Indiana Attorney General)

All technology incidents

Sources

  1. 2025-07-07 · AIngram Micro Holding Corporation, Form 8-K, Item 8.01 (SEC EDGAR), published July 7, 2025
  2. 2025-07-05 · AIngram Micro Holding Corporation, press release, Exhibit 99.1 (SEC EDGAR), published July 5, 2025
  3. 2025-08-06 · AIngram Micro Holding Corporation, second-quarter 2025 earnings release, Exhibit 99.1 (SEC EDGAR), published August 6, 2025
  4. 2026-03-03 · AIngram Micro Holding Corporation, Form 10-K for fiscal 2025 (SEC EDGAR), published March 3, 2026
  5. 2026-01-16 · AIngram Micro Inc., notice of data breach filed with the Massachusetts Office of Consumer Affairs, published January 16, 2026
  6. 2026-01-16 · AIngram Micro Inc., notification letter filed with the California Attorney General, published January 16, 2026
  7. 2026-11-11 · ACalifornia Attorney General, data breach notification record, published November 11, 2026
  8. 2026-11-11 · AIndiana Attorney General, data breach year-to-date report (2026), published November 11, 2026
  9. 2026-11-11 · ATexas Attorney General, data security breach reports, published November 11, 2026
  10. 2026-11-11 · AMassachusetts Office of Consumer Affairs and Business Regulation, data breach report (2026), published November 11, 2026
  11. 2024-05-21 · AU.S. Securities and Exchange Commission, statement by the Director of the Division of Corporation Finance, published May 21, 2024

Tier A: the organization itself (including notices it filed with a state attorney general), a regulator or SEC EDGAR. Tier B: established press. Each fact on this page carries its supporting passage in the page source.

Entries like this one, in Wednesday’s docket

Wednesdays

Unsubscribe any time.