Skip to content
DysruptionHub registry intelligence

Registry insights

See where documented incidents concentrate, who they affect and how their characteristics change over time.

Reporting period Last 12 months
188 Incidents Documented in this reporting window
Tempo

Incident activity

188 incidents dated in this period

Incident activity over time Sep 2025: 0; Oct 2025: 0; Nov 2025: 1; Dec 2025: 3; Jan 2026: 10; Feb 2026: 13; Mar 2026: 30; Apr 2026: 21; May 2026: 17; Jun 2026: 17; Jul 2026: 32; Aug 2026: 39; Sep 2026: 5 0 20 39 Sep 2025: 0 incidents Sep 2025 Oct 2025: 0 incidents Nov 2025: 1 incident Nov 2025 Dec 2025: 3 incidents Jan 2026: 10 incidents Jan 2026 Feb 2026: 13 incidents Mar 2026: 30 incidents Mar 2026 Apr 2026: 21 incidents May 2026: 17 incidents May 2026 Jun 2026: 17 incidents Jul 2026: 32 incidents Jul 2026 Aug 2026: 39 incidents Sep 2026: 5 incidents Sep 2026

Attribution and disclosure

32% with a named threat actor in the registry 60 of 188 incidents
96% with a recorded official cyber disclosure 181 of 188 incidents
52% officially disclosed on the first-signal date 95 of 181 incidents with comparable dates
13.2 mean days to later official disclosure Across 86 incidents disclosed after the first-signal date

Threat actors

Explore
  1. Qilin 9 5%
  2. LockBit 3 2%

6 threat actors tied at 2 incidents; this tied group is not shown.

Footprint

Geographic impact

Explore the incident map

State impact

Bubble area represents incident count; one incident may appear in multiple states.

Ranked by incident count; one incident may appear in multiple states.

State and territory impact bubbles Bubble area represents incident count. Texas: 18 incidents; California: 14 incidents; Georgia: 13 incidents; Michigan: 13 incidents; Minnesota: 13 incidents; Florida: 12 incidents; Massachusetts: 11 incidents; Pennsylvania: 9 incidents; Utah: 8 incidents; Virginia: 7 incidents; Wisconsin: 7 incidents; New Jersey: 6 incidents; Ohio: 6 incidents; Arizona: 5 incidents; Illinois: 5 incidents; Indiana: 5 incidents; Iowa: 5 incidents; Mississippi: 5 incidents; North Carolina: 5 incidents; Oklahoma: 5 incidents; South Carolina: 5 incidents; Tennessee: 5 incidents; New Hampshire: 4 incidents; New York: 4 incidents; Puerto Rico: 4 incidents; Alabama: 3 incidents; District of Columbia: 3 incidents; Kansas: 3 incidents; Maine: 3 incidents; Maryland: 3 incidents; Missouri: 3 incidents; Rhode Island: 3 incidents; South Dakota: 3 incidents; Washington: 3 incidents; West Virginia: 3 incidents; Alaska: 2 incidents; Arkansas: 2 incidents; Colorado: 2 incidents; Connecticut: 2 incidents; Idaho: 2 incidents; Montana: 2 incidents; New Mexico: 2 incidents; North Dakota: 2 incidents; Wyoming: 2 incidents; Delaware: 1 incident; Guam: 1 incident; Nebraska: 1 incident; Northern Mariana Islands: 1 incident; U.S. Virgin Islands: 1 incident 18 Texas 14 California 13 Georgia 13 Michigan 13 Minnesota 12 Florida 11 Massachusetts 9 Pennsylvania 8 Utah 7 Virginia 7 Wisconsin 6 New Jersey 6 Ohio 5 Arizona 5 Illinois 5 Indiana 5 Iowa 5 Mississippi 5 North Carolina 5 Oklahoma 5 South Carolina 5 Tennessee 4 New Hampshire 4 New York 4 Puerto Rico 3 Alabama 3 District of Columbia 3 Kansas 3 Maine 3 Maryland 3 Missouri 3 Rhode Island 3 South Dakota 3 Washington 3 West Virginia 2 Alaska 2 Arkansas 2 Colorado 2 Connecticut 2 Idaho 2 Montana 2 New Mexico 2 North Dakota 2 Wyoming 1 Delaware 1 Guam 1 Nebraska 1 Northern Mariana Islands 1 U.S. Virgin Islands

All 49 affected states and territories are shown.

  1. Texas 18 10%
  2. Georgia 13 7%
  3. Michigan 13 7%
  4. Minnesota 13 7%
  5. Florida 12 6%

Counties

Showing 6 of 45 counties with repeated impact. 6 counties tied at 3 incidents; this tied group is not shown. 213 additional counties each appeared in one incident.

Cities

Showing 6 of 31 cities with repeated impact. 25 cities tied at 2 incidents; this tied group is not shown. 366 additional cities each appeared in one incident.

Concentration

State-by-sector matrix

Each incident is counted once per state-sector pair.

Incident counts by state or territory and critical infrastructure sector
State or territoryGovernment Services and FacilitiesHealthcare and Public HealthWater and Wastewater SystemsInformation TechnologyEmergency ServicesCommercial Facilities
Texas10321
California6221
Georgia6231
Michigan33311
Minnesota52411
Florida62111
Massachusetts5222
Pennsylvania62
Affected ecosystem

Organizations and infrastructure

Organizations with repeated impact

Explore

205 additional organizations each appeared in one incident.

Organization types

2 organization types tied at 11 incidents; this tied group is not shown.

Critical infrastructure sectors

Incident status

  1. Resolved 77 41%
  2. Active 20 11%
Characteristics

Mechanisms and impacts

Explore relationships

Attack mechanisms

  1. Ransomware 46 24%
  2. Malware 11 6%

2 mechanisms tied at 3 incidents; this tied group is not shown.

Operational impacts

Data impacts

4 impacts tied at 3 incidents; this tied group is not shown.

Extortion indicators

2 indicators tied at 12 incidents; this tied group is not shown.

Public record

Assessment and transparency

Cyber assessment

  1. Confirmed 186 99%

Ransomware confidence

  1. Unresolved 78 41%
  2. Confirmed 38 20%
  3. Low 20 11%
  4. Medium 19 10%
  5. High 7 4%

Cyber transparency

  1. The organization publicly identifies the event as cyber-related.

  2. External sources identified the event as cyber-related before the organization publicly confirmed it.

  3. Only external sources publicly identify the event as cyber-related.

  4. The disruption is documented, but available public information does not yet establish cyber involvement.

Disruption transparency

  1. The organization publicly documents the resulting service disruption.

  2. Credible external sources document the disruption, but the organization does not clearly do so.

  3. No credible public source clearly documents service disruption.

How these figures are calculated

Figures describe published registry coverage, not the prevalence of cyber incidents overall. Incidents are grouped by their canonical incident date rather than publication date.

An incident is counted once within each category. Geographic totals use explicitly impacted incident locations and do not treat an organization headquarters as an impacted place. Municipal impacts roll up to their recorded county and state, with each incident counted once per place. Affected organization counts use primary, victim, operator and owner relationships. Critical infrastructure and organization taxonomies remain separate.

Threat actor figures include only actors attached through eligible public claims. Same-date disclosure compares the calendar date of the first public signal with the calendar date of the official cyber disclosure; it does not measure elapsed hours or response speed. Mean days to later disclosure is the arithmetic mean only among valid intervals greater than zero, so longer intervals have more influence. Missing, invalid or reverse-ordered date pairs are excluded. Empty or unknown values are not inferred.

Registry data last updated Sep 10, 2026.