mythsthe wider recordIngram Micro2025IT distribution / united states

everyone assumed:

once the orders ship again, the ransomware attack is over

what was actually true:

Ingram Micro was shipping orders in every region within a week of its July 2025 ransomware attack, and in January 2026 it wrote to employees and job applicants whose records were in the files the intruder took.

how it happened

  1. whoan intruderthe company has not said how they got in
  2. the gapinternal file repositoriesemployment and job applicant records
  3. thenransomware, systems offlineorders disrupted, back in every region by 9 July
  4. the result42,521 people notifiedper reporting on the Maine filing
the gap that let it happen the result

what everyone assumed

Ingram Micro has not said what it believed, so this belief is an inference from how the incident was reported. A ransomware attack on a distributor looks like an outage: orders stop, the website goes dark, customers wait. The company’s own updates in July 2025 tracked exactly that, region by region, until orders shipped again. Measured that way, the attack lasted about a week.

That reading is fair as far as it goes, because getting the business running is the urgent part. It leaves a second question open for much longer: which files did the intruder take, and whose records are in them?

what happened

On 5 July 2025 Ingram Micro said it had identified ransomware on certain of its internal systems. The statement, filed with the SEC under a Form 8-K on 7 July, says the company took some systems offline, brought in outside cybersecurity experts, notified law enforcement and was working to restore systems so that it could process and ship orders.

The company’s incident status page then tracked the recovery:

  • 7 July 2025. Subscription orders, including renewals, were available again globally, with limits on hardware orders.
  • 8 July 2025, afternoon Pacific time. The company said it believed the unauthorised access was contained, and that its investigation into the scope of the incident and the affected data was ongoing.
  • 9 July 2025, evening. The company said it was “now operational across all countries and regions” where it does business.

Ingram Micro’s 10-K for fiscal 2025, filed on 3 March 2026, adds that it restored the affected systems using backups, notified authorities and certain customers and partners, and that the incident did not cause a material interruption of its operations. That last point is the company’s own assessment.

The data side came later. A notice letter on Ingram Micro Inc. letterhead, dated 16 January 2026, says the company detected the incident on 3 July 2025 and found that an unauthorised third party took certain files from some of its internal file repositories between 2 and 3 July 2025. It says the company reviewed those files and had recently learned that some held the recipient’s personal information. According to the letter, the files include employment and job applicant records with names, contact details, dates of birth, government ID numbers such as Social Security, driver’s licence and passport numbers, and employment information such as work evaluations.

How the intruder got in is not on the record. Ingram Micro has not said. On 5 July 2025 BleepingComputer reported that unnamed sources believed the attackers first entered through the company’s GlobalProtect VPN, likely with compromised credentials. Palo Alto Networks, which makes GlobalProtect, told the outlet that none of its products were the source of the vulnerability or affected by the breach, and BleepingComputer updated its article on 8 July 2025 to make clear that the VPN gateway was not compromised or exploited. The story of a VPN account with a leaked password is told on the Colonial Pipeline page, and the guide on boxes at the network edge covers who holds those logins.

The ransomware group SafePay listed Ingram Micro on its leak site, according to SecurityWeek. That is the group’s claim. Ingram Micro has not named an attacker.

step by step

  1. 2 to 3 July 2025files leave the file repositoriesAn unauthorised third party takes files that include employment and job applicant records, according to the company's later letter.the assumption breaks here
  2. 5 to 7 July 2025Ingram Micro reports ransomwareIt takes systems offline, calls in outside experts and notifies law enforcement, then files the statement with the SEC.
  3. 9 July 2025operational in every regionThe company's status page says it is operational across all countries and regions where it does business.
  4. 16 January 2026letters to employees and applicantsThe letter says some of the taken files held the recipient's personal information, including government ID numbers.

how it surfaced

The orders came back in a week. The list of people came in January 2026. SecurityWeek and The Register reported on 19 January 2026 that Ingram Micro’s filing with the Maine attorney general put the number of people affected at 42,521, all of them employees or job applicants according to the letter’s description of the files. No source opened for this page splits that number between the two groups.

The costs ran on as well. The 10-K lists $6.2 million in fiscal 2025 for external services and other expenses in response to the incident, and the 10-Q for the quarter ended 26 September 2026 lists a further $3.4 million in the first 39 weeks of 2026. Ingram Micro’s chief executive said in the earnings release of 6 August 2025 that the attack had no impact on results for the quarter ended in June.

What the record shows is a two-day window in which files left internal repositories that held HR and recruiting records. The guide on old files and old sharing covers how such folders fill up and stay open, and blast radius covers how to count what one foothold can reach.

Backups bring the systems back. Nothing brings back the files that left.

The folders that hold ID numbers of staff, former staff and applicants are the mailing list for the letter you would have to send.

picture it at a company like yours

The company here is made up. The other two paths are not: they happened, and each links to the story.

your company
a normal dayYour company keeps scanned IDs, payslips and old applications in folders on the shared drive, because that is where HR has always saved them.
the gap nobody seesNobody has checked who can open those folders, or cleared out the applications of people who were never hired.a setting that leaves data open
  1. in this story
    the day it mattersAn intruder spends a couple of days inside, the systems come back within the week, and everyone calls it over.
    what it costs youMonths later you are writing to staff and to people who once applied, telling them their ID numbers left with the files.
  2. or it goes like this
    howA share link meant for one folder opens the whole storage account.
    what leavesbackups, passwords and private messageswho ends up with itanyone who finds the link
    it happenedMicrosoft AI data exposure, 2023
  3. or it goes like this
    howA default on a no-code app leaves its data readable without logging in.
    what leavespersonal records you collectedwho ends up with itanyone who looks
    it happenedPower Apps misconfiguration, 2021

sources

  1. Ingram Micro: Ingram Micro Issues Statement Regarding Cybersecurity Incident, 5 July 2025 (press release)
  2. Ingram Micro Holding Corporation, Form 8-K, Item 8.01, filed 7 July 2025 (SEC filing)
  3. Ingram Micro: Cybersecurity incident status page, updates of 5 to 9 July 2025
  4. Ingram Micro Holding Corporation, fiscal second quarter 2025 results, Exhibit 99.1 to Form 8-K, 6 August 2025 (SEC filing)
  5. Ingram Micro Holding Corporation, Form 10-K for fiscal year 2025, filed 3 March 2026 (SEC filing)
  6. Ingram Micro Holding Corporation, Form 10-Q for the quarter ended 26 September 2026, filed 29 October 2026 (SEC filing)
  7. Ingram Micro Inc.: Notice of data breach, letter dated 16 January 2026 (sample copy published online)
  8. SecurityWeek: 42,000 impacted by Ingram Micro ransomware attack, 19 January 2026
  9. The Register: Ingram Micro admits summer ransomware raid exposed thousands of staff records, 19 January 2026
  10. BleepingComputer: Ingram Micro outage caused by SafePay ransomware attack, 5 July 2025 (updated 6 to 8 July 2025)

← all myths

your turn

what you can do about it

  1. this week

    Find the shared folders that hold staff and applicant ID documents, and list who can open them.

    Search the shared drive and the HR folders for scanned passports, driver's licences, tax or social security numbers, payslips, appraisals and old applications. Write down who can open each folder, limit access to the people who need it, and delete applications older than the period your HR policy sets. Ingram Micro's letters of January 2026 went to employees and job applicants whose records sat in internal file repositories. If an intruder had two days inside your network, how many people would be on your list?

  2. go deeper

  3. if you're not sure where to start

    Run the offboarding checklist on one leaver. It covers every account and token to close when someone leaves.

    open the checklist →

the letter · every two weeks

one access gap in your inbox, with the fix.

Every issue takes one way access creeps in, shows a real incident where it went wrong, and ends with one thing to check that week. Written for the people who run the tools, without a security team behind them.

  • 1one mechanism, explained plainly
  • 2one real incident, taken apart
  • 3one step you can take on Monday

get the next issue

One email every two weeks. Your address stays here and is never passed to vendors. One click to unsubscribe. Privacy.