Ninja Labz blog
WHODUNNIT: the fridges, the outages, and what the evidence actually says about Iran and Russia
Seven hundred French supermarkets lost their refrigeration in one October night and fifteen of them caught fire. A month later the United States had the worst week of technology outages in years and everyone asked the same question. Here is the question answered the way an analyst answers it, one claim at a time, with a grade on each. Iran did the fridges. Nobody did the outages.
The short version. Between 11 and 12 October an Iranian military unit switched off, overheated or otherwise wrecked the refrigeration at roughly 700 French retail sites. Food spoiled and at least fifteen fires started. France said so on 9 November, in public, with a technical report, named officers, arrest warrants and sanctions. That is as good as attribution gets. A second, wider wave on 1 and 2 November hit stores across at least eleven European countries, including British meat and produce suppliers and three sites of the French blood service; that one has not been pinned on anyone by any government, and the only people claiming it are pro-Russian hacktivist brands with a record of claiming things they did not do. Then, from 12 to 17 November, America had Microsoft 365 down for most of a day, a nationwide ground stop, Workday, AWS, United, Chase, Apple and the NSA’s internal network all wobbling in the same five days, and the internet decided it was obviously the same story. It was not. Every operator gave a cause. Three senior US officials said there was no cyber attack. The one public claim otherwise offered no evidence at all.
This is the article-length cut of a longer analysis we wrote for defence and intelligence readers. The long version grades every claim and lists every source; this one tells the story and keeps the grades. If you only read one line, read this: attribution follows the evidence, not the news cycle, and the two biggest stories of the autumn point in opposite directions.
How we grade a claim
“Linked to Iran” is not a finding. Before any verdict below we ask where the strongest public evidence for the claim sits on a seven-rung ladder, and we use the British intelligence community’s probability words so that “likely” means something specific.
| Rung | What it means | Example this autumn |
|---|---|---|
| 1 | A government names the actor and publishes the technical case; courts or sanctions follow | France on Shahid Kaveh |
| 2 | A government names the actor but keeps the evidence closed | Estonia on the GRU; Ukraine on its alert app |
| 3 | Independent researchers attribute, with tradecraft and indicators; more weight when several agree | Symantec, Sekoia and ESET on Russian espionage units |
| 4 | A government says “evidence points to” but will not commit | Belgium on Iran |
| 5 | The actor, or a persona, claims it | NoName057(16) and Z-Pentest on the second fridge wave |
| 6 | Anonymous sources in the press | Russia and a German drone maker |
| 7 | Pattern-matching with no evidence, however sincerely held | the “whistleblower letter” on the US outages |
Probability words, from weakest to strongest: remote chance, highly unlikely, unlikely, realistic possibility, likely, highly likely, almost certain.
Act one: the fridges
Modern commercial refrigeration is run by small industrial controllers, boxes on a plant-room wall that hold the temperature set-points, the defrost schedules and the alarms, and that increasingly sit on the internet so a maintenance contractor can check them from a van. A worrying number of them sit there with the factory password and firmware the maker stopped supporting years ago. Six unpatched vulnerabilities in one widely used family of controllers were public knowledge before any of this started.
On the night of 11 to 12 October, across France, those controllers started doing things nobody told them to. Set-points pushed up, compressors driven into failure, defrost cycles run back to back. By morning around 700 sites had lost their cold chain, stock was being skipped, and at least fifteen sites had fires, because a compressor made to run against its own protections eventually gets hot enough. The French response was fast and, unusually, loud. The national cyber agency took it, the police took it, and on 9 November the government attributed the whole operation to Shahid Kaveh, a cyber unit inside the Islamic Revolutionary Guard Corps, with a published technical report, named individuals, arrest warrants requested and sanctions sought. The same unit is the one the US government calls CyberAv3ngers, already blamed for tampering with controllers at American water utilities.
Verdict: highly likely Iran, rung 1 of 7. A government attribution with a published report and judicial follow-through is the strongest form there is. We have no reason to grade it lower and every reason not to grade it higher: “almost certain” is for confessions and captured operators, and the French report is what it is, an intelligence finding placed on the public record.
The second wave
Three weeks later, on 1 and 2 November, it happened again and it happened wider. Supermarkets in at least eleven European countries reported refrigeration failures over one weekend; more than a hundred stores in some counts. British meat and produce suppliers were among them. Three sites belonging to the French national blood service lost cold storage. On 5 November the US cyber agency and the FBI issued a joint warning about internet-exposed operational controllers, citing the European supermarket attacks by name, which tells you the Americans had seen the same controller family on their own networks.
Here the evidence changes shape. No government has attributed the second wave. Belgium’s authorities said the evidence points to Iran but called a formal finding premature. Two hacktivist brands aligned with Russia, NoName057(16) and Z-Pentest, claimed it on Telegram. Both have a record of claiming other people’s work, and neither offered anything a defender could check.
Verdict: realistic possibility Iran, rung 4 of 7. The method, the targets and the timing all rhyme with October, and Belgium’s hedge points the same way. But a rhyme is not a finding, and a Telegram boast from a group that boasts for a living counts against itself as much as for. The honest reading is that the same unit, or someone who learned from it, came back with a longer list, and that the pro-Russian brands either joined in with a shared playbook or claimed credit for weather they did not make.
Act two: the American week
Thursday 12 November, Microsoft 365 began failing: Exchange, Outlook, Teams, Copilot, Intune, with knock-on failures in Bing, DuckDuckGo and the search behind ChatGPT. Partial recovery took about eighteen hours, full restoration came on the morning of the 14th. Friday the 13th, the Federal Aviation Administration ordered a nationwide ground stop. Over the weekend Workday placed production tenants into maintenance, AWS’s biggest region had an authentication wobble, United delayed departures for about a hundred minutes, JPMorgan Chase had transaction delays. Monday the 17th, Apple’s iCloud and Apple Pay stumbled, and the NSA’s own internal network, NSANet, degraded.
Nine events in five days. Anyone would ask the question. Here is what each operator said, which is the evidence the question has to be answered from.
| Date | Who | What failed | Stated cause | Cyber attack? |
|---|---|---|---|---|
| 12 to 14 Nov | Microsoft | Exchange, Outlook, Teams, Copilot, Intune and search partners | A previously undetected defect that made networking gateway servers unresponsive under load, exposed by a network configuration change after an update | No, by Microsoft’s own cause summary |
| 13 Nov | FAA | Nationwide ground stop; air traffic telecoms | Excess data traffic destabilised legacy telecom gear during router replacement at a radio site in Arkansas; the roll-out has since been halted | No sign; final root cause still to be published |
| 13 to 14 Nov | Workday | Production tenants | A disaster-recovery issue left data inconsistent | No |
| 15 Nov | AWS | Authentication across 11 services in US-East-1 | Not stated; fixed the same day | None indicated |
| 16 Nov | United | Crew communications, weight-and-balance apps | Technology outage | “No sign of a cybersecurity incident” |
| 16 Nov | JPMorgan Chase | Transaction delays | A software bug in on-premises systems | No cyber link found |
| 17 Nov | Apple | iCloud, Apple Pay, Support | An internal update | “Not a cyberattack” |
| 17 Nov | NSA | NSANet | Scheduled maintenance; security patching after a PHP vulnerability | No evidence of attack, per the DNI |
Three officials spoke within a day of each other: the Secretary of Homeland Security, the Director of National Intelligence and the Secretary of State. All three said there was no cyber attack behind the week. Against that stands one document: an open letter styled as a whistleblower’s account, which asserts an Iranian operation with Russian help and cites nothing a technical reader could examine.
Verdict: highly unlikely that Iran or Russia caused the US outage week, rung 7 of 7 for the contrary claim. Nine unrelated systems, nine mundane causes, several of them the ordinary kind of change-window failure that happens when a big organisation touches its network on a Thursday. The simplest explanation fits every fact on record. The alternative requires three operators and three officials to be lying in the same direction in the same week, and a hostile state to have picked a set of targets with no common technology, no common supplier and no common effect. Correlation in time is not a method.
It is worth saying what did happen that week that was genuinely hostile, because it got lost. A remote-management vendor’s partner environment was breached and hundreds of hosts across dozens of organisations were touched. A web experimentation platform was compromised and malicious JavaScript reached about 178 customer sites. Neither was attributed to a state. Both were real. Neither trended.
Act three: Russia, properly
The question as usually asked lumps Russia in with the fridges. The evidence does not. In the same window Russia was doing what Russia does, and the grades are mixed because the evidence is.
- Sabotage, Estonia, 14 November. Estonia’s security service attributed a sabotage plot against the drone maker Threod Systems to the GRU, made eight arrests and announced border closures. Likely, rung 2. A government name without a published report.
- Ukraine’s Air Alert app, 1 November. The national alert app was hijacked to push fake nuclear and chemical warnings. Ukraine attributed it to Russia and, notably, admitted a retaliatory hack of Russia’s equivalent. Likely, rung 2.
- Espionage against NATO defence and government targets. Symantec, Sekoia, ESET and Trellix published on APT28, APT29 and Turla campaigns in the window, with tradecraft overlaps and indicators. Several vendors, independently, agreeing. Highly likely, rung 3.
- The German drone-software supply chain. Quantum Systems, which supplies Ukraine and the Bundeswehr, reported an update-server poisoning that reached ground drones. Russia is suspected on anonymous sourcing only; the company and prosecutors have named nobody. Realistic possibility, rung 6.
- Influence, US midterms. Graphika, NewsGuard and Clemson researchers attributed deepfake operations against candidates to Storm-1516 with high confidence; no US government statement. Likely, rung 3.
None of these caused an outage outside Ukraine. The disruptive Russian activity that does reach Western companies is the Russian-speaking ransomware ecosystem, which is criminal, tolerated rather than tasked, and in our own tracker just had its busiest week on record: 1,356 victims posted in thirty days, 48 of them British.
What our own sensors saw
We run a honeynet, a malware range and a threat graph, and we write a daily edition from them, so we can say what the internet-facing world looked like while all this was going on. Since 5 October our honeypots have logged 9,780 distinct source addresses. Russia accounts for 5.2 percent of them and Iran for 0.9 percent, and every one of those sessions is commodity scanning and brute force, the background hum of the internet. Nothing changed during the American outage week. Sixteen of the 54 vulnerabilities added to the US Known Exploited Vulnerabilities catalogue since 1 October are in firewalls, VPNs and gateways, the edge devices that state units actually use to get in, and that is the pattern worth a board’s attention, not the fridges.
So, whodunnit
| Claim | Verdict | Rung |
|---|---|---|
| Iran sabotaged French refrigeration, 11 to 12 October | highly likely | 1 |
| Iran was behind the 1 to 2 November European wave | realistic possibility | 4 |
| Iran or Russia caused the US outages of 12 to 17 November | highly unlikely | 7 |
| Russia (GRU) ordered the Estonian drone-maker sabotage | likely | 2 |
| Russia hijacked Ukraine’s Air Alert app | likely | 2 |
| Russian state units ran espionage against NATO targets | highly likely | 3 |
| Russia was behind the Quantum Systems supply-chain attack | realistic possibility | 6 |
| Russia ran deepfake influence against US candidates | likely | 3 |
Iran did the fridges, and a government has shown its working. Russia is running a steady campaign of sabotage, espionage and influence across Europe, strong in places and thin in others. Nobody did the American outage week; it did itself.
The lesson is not about Tehran or Moscow. It is that the same unpatched, internet-facing controller that a state unit sabotaged in France is sitting in British supermarkets, hospitals and bases this afternoon, with the factory password on it, and that when the next outage week comes the right first question is still “what did the operator say”, not “who benefits”.
The full analysis, with every claim graded and all 53 sources, is at ninjalabz.io/blog/iran-russia-attribution-ledger. Key public sources for this article: the French attribution as reported by The Record and The Hacker News; the second wave in SecurityWeek and The Record; the US warning in TechCrunch; the controller vulnerabilities in The Hacker News; Belgium’s position via Anadolu; the Microsoft outage’s own cause summary via Wikipedia’s incident page; the DNI’s statement via ABC News; the DHS Secretary via CNN; Estonia via ERR; the Air Alert app via CBS; Quantum Systems via Al Arabiya; the influence operation via FDD; and the NCSC’s Annual Review 2026.
ScottG · Ninja Labz · ninjalabz.io
Every morning at 06:00 UK an AI reads every threat-intel item from the last 24 hours and writes the paper, with receipts.
Read Probably Fine Daily