Industrial ransomware Q3 2026 claims reached 1,266 industrial organizations worldwide, according to Dragos’s November 16 analysis of public disclosures and ransomware leak sites. That compares with 1,140 in Q2, an 11% increase in Dragos’s count. These are reported incidents and claims, not 1,266 independently verified breaches or plant shutdowns.
Manufacturing made up 876 of the Q3 records, or 69% of Dragos’s industrial total. Engineering firms, integrators, and equipment makers supporting operational technology (OT) accounted for 116; transportation and logistics accounted for 105. For buyers, third party risk management software offers a way to assess supplier exposure alongside the enterprise systems a plant cannot work without.
What Does the Industrial Ransomware Q3 2026 Count Measure?
Dragos compiled publicly disclosed victim data and ransomware groups’ data leak site posts for July through September 2026. The method makes the figures useful for comparing visible activity across sectors and quarters. A leak site post remains an adversary claim until independently established; a disclosure also does not automatically prove control-system compromise.
Dragos counted 1,020 industrial records in Q1, 1,140 in Q2, and 1,266 in Q3 2026 using its tracking method. The upward sequence shows more visible cases in its dataset. It does not by itself measure how many plants stopped, how long they stopped, or whether a change in disclosure behavior contributed.
The sector chart repeats Dragos’s Q3 categories, rather than adding separate datasets. Manufacturing’s visible concentration is clear, but its broad label spans construction-related, equipment, food, pharmaceutical, and other subsectors. The 116 OT ecosystem records describe supplier organizations, not 116 compromises of industrial controllers.
Why Does Manufacturing Dominate the Visible Claims?
Dragos reports that manufacturing’s share of industrial cases rose from 62% in Q1 to 65% in Q2 and 69% in Q3 2026. Its Q3 manufacturing breakdown includes 193 construction-related records and 184 equipment records. Food and beverage accounts for 90, compared with 57 in Q1 and 70 in Q2, according to Dragos.
The report links manufacturing’s exposure to enterprise resource planning (ERP), distributed sites, and tight production schedules. A failed ordering, scheduling, identity, or virtualization service can interrupt work even if controllers stay untouched. That is the useful planning distinction: test the systems that production depends on, then test the route back to service.
Dragos observed no Q3 2026 case in which a ransomware operator reached Stage 2 of the ICS Cyber Kill Chain or directly manipulated a control system. This is the scope of Dragos’s observation, not a claim that OT disruption cannot occur. Its report describes enterprise IT failures cascading into production or precautionary shutdown decisions.
Where Do OT Suppliers and Logistics Change the Exposure?
Dragos logged 116 Q3 2026 records among OT-related engineering services, integrators, and equipment manufacturers, nearly level with 117 in Q2. Its Q3 detail assigns 95 to ICS engineering and 21 to ICS equipment. A supplier can hold engineering files, remote access, or project documentation that a plant needs, even when the plant is not named on a leak site.
The report also counts 105 transportation and logistics records in Q3 2026, including 77 in logistics, 15 in maritime, and 13 in aviation. Scheduling, fleet, reservation, and shipment systems create a different route to disruption from controller manipulation. A manufacturer evaluating continuity should ask which delivery and service dependencies have a workable manual fallback.
Dragos describes a Q3 data theft campaign against product lifecycle management software, with 35 industrial claims attributed to Cl0p in its tracking. The report says the claims were not independently verified and that it observed no associated OT compromise or operational impact. Engineering files and supplier records can still be sensitive, so teams should scope data exposure before assuming a plant incident.
For a vendor review, document who owns each access path and how a supplier connects to production dependencies. Our supply chain risk analysis offers a separate framework for assessing a provider’s reach. That framework does not change what Dragos did or did not verify in this quarter.
How Concentrated Were the Ransomware Claims?
Dragos attributes 195 Q3 2026 industrial claims to Qilin and 167 to The Gentlemen. Together, those 362 claims represent 29% of Dragos’s 1,266 industrial records. The count of distinct ransomware brands claiming industrial victims rose from 70 in Q2 to 99 in Q3, so concentration and brand turnover occurred together.
Those are Dragos’s leak site and disclosure classifications, not independent attribution of every intrusion. The report notes that affiliates exploited exposed edge and enterprise applications and reused stolen remote access credentials. Some operators stole data before encryption or instead of it, which makes an encryptor alert an incomplete detection strategy.
Brandefense Blackhole counted 175 dark-chat posts matching the broad term “Dragos” from August 19 through November 17, 2026. The measured unit is matching posts, not industrial incidents, unique actors, or confirmed attacks. This separate research signal may overlap public discussion and cannot validate or be added to Dragos’s Q3 incident count.
Our Qilin profile gives background on the group, while Dragos remains the source for these quarterly figures. Teams using Cyber Threat Intelligence should keep a clear distinction between an actor’s public claim, an observed intrusion, and an operational impact. That distinction matters in executive reporting and supplier escalation.
What Should a Manufacturing Security Team Check First?
Start with the services that link enterprise IT to plant operations: remote access, identity, ERP, virtualization, and engineering workflows. Dragos says internet-facing edge devices and enterprise applications remained common entry points in Q3 2026. Its conclusion calls for asset visibility, multifactor authentication on remote access, rapid edge patching, credential hygiene, and controlled remote management tools.
Map every supplier account and support connection to a named owner, business purpose, and revocation path. Compare that map with production dependencies so responders know which remote service or design repository could affect delivery. This is our workflow drawn from the report’s exposure pattern, not a measured count of compromised suppliers.
- Inventory exposed accessIdentify edge appliances, remote access, and enterprise applications with owners.
- Protect privileged routesRequire multifactor authentication and review supplier and administrator accounts.
- Test production dependenciesRestore ERP, identity, and virtualization services needed by plant teams.
- Rehearse supplier lossVerify escalation contacts, access revocation, and manual shipping or engineering fallbacks.
During an alert, look for access to remote management systems, unusual privileged sessions, and unexpected data movement before treating encryption as the first signal. Separate evidence of enterprise service loss from evidence of controller access. If production stops, record which dependency failed and who made the shutdown decision.
Use the ransomware response checklist to structure containment and recovery responsibilities. Supplier reviews should ask whether a provider can revoke remote access promptly and restore the files a plant actually uses. A generic statement that backups exist is weaker than a tested restoration of those specific services.
How We Read the Figures
Dragos published its Q3 2026 industrial ransomware analysis on November 16, 2026. Its July through September dataset combines public victim disclosures with ransomware leak site postings. We quote its sector and group figures as reported records or claims and preserve its limits on verification and ICS impact.
Brandefense Blackhole’s August 19 through November 17 count is a separate broad-term dark-chat post count supplied for this draft. Its date range, unit, and collection method differ from Dragos’s quarterly case tracking. We have not merged, deduplicated, or summed the two datasets.
Frequently Asked Questions
Do Dragos’s 1,266 Q3 records mean 1,266 confirmed plant shutdowns?
No. Dragos combines public disclosures and ransomware leak site posts. Those records do not establish a verified breach or production stop in every case.
Were industrial controllers directly manipulated in the observed Q3 cases?
Dragos says it observed no Q3 2026 case reaching Stage 2 of the ICS Cyber Kill Chain or directly manipulating a control system.
What should a manufacturer test after reviewing the report?
Inventory remote access and supplier accounts, then test recovery of identity, ERP, and virtualization services required for production.
