Ingram Micro, one of the largest IT distributors in the world, has confirmed that ransomware on internal systems knocked its ordering platforms offline worldwide over the July 4 holiday weekend. Customers — solution providers, resellers, and managed service providers — lost the ability to place orders online for more than two days before the company acknowledged the cause. A ransom note delivered to the distributor claims to come from the SafePay extortion group, though the gang had not named the victim on its leak site at the time of reporting. The incident has renewed scrutiny of the concentrated risk that distributors and MSPs carry for the downstream customers who depend on their portals.

What is confirmed so far

The disruption became visible on Thursday, when partners found the distributor's websites unreachable and online ordering unavailable. Ingram Micro stayed silent through Friday and most of Saturday. On Saturday evening it attributed the outage to ransomware, saying it had identified the malware on certain internal systems, isolated the affected environment by taking systems offline, brought in outside security experts, and notified law enforcement. The company said it was working to restore systems so it could resume processing and shipping orders, and apologized to customers and vendor partners. It also filed an 8-K form with the US Securities and Exchange Commission that same Saturday.

On Monday the distributor stood up a dedicated page for restoration updates. By that point subscription orders were flowing globally again, and phone and email ordering had been re-enabled for the UK, Germany, France, Italy, Spain, Brazil, India, and China. A Tuesday update extended phone and email ordering to Canada and Austria.

Availability was still uneven at the time of writing. The US site was reachable, but several subdomains and regional properties were down, replaced by a notice reading "Ingram Micro is currently experiencing a cybersecurity incident" alongside a link to the Saturday statement. Ingram Micro Xvantage, the platform used for purchasing software, hardware, and services, appeared to remain offline.

Timeline at a glance

WhenWhat happened
ThursdayPartner websites and online ordering go down ahead of the holiday weekend
Saturday eveningIngram Micro confirms ransomware on internal systems, isolates the environment, notifies law enforcement, files an 8-K
MondayRestoration update page launched; subscription orders restored globally; phone/email ordering live in UK, Germany, France, Italy, Spain, Brazil, India, China
TuesdayPhone/email ordering extended to Canada and Austria
July 8, 2025, 4 p.m. ETStory updated with additional information from the company

Who is claiming the attack

Attribution remains open. BleepingComputer was first to report that the ransom note handed to Ingram Micro presents itself as SafePay. SafePay's dark web leak site did not list the distributor, which is not unusual: extortion crews frequently hold off on publicizing a victim while they negotiate privately, sometimes for days.

SafePay is a relatively new operation, first spotted by threat analysts in 2024, but it has scaled quickly. According to NCC Group's Threat Pulse for May, it was the most active ransomware group that month, responsible for 18% of all attacks recorded. Notably, SafePay's leak site states that the group "has never and does not provide the RaaS" — a departure from the ransomware-as-a-service model in which operators license code, tooling, and even initial access to affiliates for a cut of the payout.

Downstream exposure is the bigger worry

Restoring order intake does not close the incident. Partners are tightly integrated with distributor platforms for purchasing, provisioning, and account management, and those integrations often run on stored credentials, API keys, and delegated permissions. One MSP executive, speaking on condition of anonymity, said his firm fears attackers could pivot from Ingram Micro's platforms into customer networks. His company was in the process of stripping third-party privileged access from its Microsoft tenant to eliminate that path.

The concern is well founded. MSPs hold deep, often administrative access to their own clients, which makes them a force multiplier for intruders. Almost exactly four years earlier, affiliates of the since-defunct REvil gang exploited a zero-day in Kaseya's VSA remote management product to compromise roughly 1,500 MSP clients in a single sprawling campaign — the canonical example of a trusted management plane turned into a distribution channel for ransomware.

Technical background

This section describes how ransomware intrusions of this class generally unfold and is not a reconstruction of the Ingram Micro incident.

Enterprise ransomware operations rarely begin with encryption. The common sequence is:

  1. Initial access through exposed remote-access services (VPN appliances, RDP, Citrix gateways), stolen credentials from infostealer logs, phishing, or exploitation of an unpatched internet-facing appliance.
  2. Privilege escalation and credential harvesting — dumping LSASS, Kerberoasting, or pulling secrets from configuration management and password vaults.
  3. Discovery and lateral movement using native tooling (PsExec, WMI, SMB, RDP) to reach domain controllers, hypervisors, and backup infrastructure.
  4. Defense evasion — disabling endpoint protection via group policy or signed vulnerable drivers, clearing logs, and deleting shadow copies to prevent local recovery.
  5. Exfiltration before encryption to support double extortion, followed by mass encryption and ransom-note drops across file shares.

Because backup destruction is a standard step, recovery outcomes hinge on whether immutable or offline copies exist and whether restoration has ever been tested at scale.

Detection and mitigation

Generic hunting and hardening measures that apply to this class of intrusion:

Look for shadow-copy and backup-catalog destruction, a near-universal precursor to encryption:


# Windows event log: process creation (4688) for destructive backup commands
wevtutil qe Security /q:"*[System[(EventID=4688)]]" /f:text | \
  grep -Ei "vssadmin|wbadmin|bcdedit|diskshadow"

Audit for remote-execution tooling and service creation in the days preceding an outage:


# Example: search Sysmon process-creation telemetry for lateral-movement binaries
grep -Ei "psexec|wmiexec|smbexec|winrs" /var/log/sysmon/process.log

Harden the control planes that partners and vendors depend on:

  • Require phishing-resistant MFA on all remote access and administrative portals; remove legacy authentication protocols.
  • Inventory third-party and delegated access — OAuth grants, enterprise applications, API tokens — and revoke anything not actively needed. Rotate credentials shared with distributors and integrators after any suspected exposure.
  • Segment management infrastructure from user networks and restrict SMB/RDP between workstations.
  • Keep at least one backup copy offline or immutable, and rehearse full-environment restores rather than single-file tests.
  • Enable and centralize logging for identity, endpoint, and network telemetry, with retention long enough to cover dwell time measured in days to weeks.
  • Maintain an out-of-band ordering and communications process so that business operations survive the loss of a primary web platform.

For partners, the practical lessons are the same ones the Kaseya campaign taught: treat every integration into a supplier's platform as an attack surface, scope its permissions to the minimum, and be ready to sever it quickly.