INTELLIGENCEReference · public sources
← Incidents

Incident reportCyberattack (possible ransomware)Report version 1 · November 21, 2026

West Virginia Legislature cyberattack

The West Virginia Legislature shut down its systems and remote access after detecting a cybersecurity incident on November 19, 2026. Some systems remained offline.

ReportedAttribution: Not attributedReference data · public sources

01Executive assessment

  • ReportedOn November 19, 2026, the West Virginia Legislature identified a cybersecurity incident. [1]
  • ReportedSome systems remained offline as of Friday afternoon. [1]

Implication: organizations in the affected sectors should confirm whether the access paths described in the sources apply to their own environment. A matching sector or technology is a reason to examine exposure, not evidence of compromise.

02What happened

The West Virginia Legislature shut down its systems and remote access after detecting a cybersecurity incident on November 19, 2026. Some systems remained offline.

Incident type
Cyberattack (possible ransomware)
Event period
November 19, 2026
Date precision
day
Evidence basis
Local news report confirmed by a spokesperson
Sectors
Public sector

As stated by the cited reporting. Current collection, November 2026.

03Evidence chronology

Publication dateDevelopmentTypeSource
November 19, 2026Incident identified; systems shut down.Organization statement (reported)[1]
November 20, 2026Dominion Post reports the cyberattack.News report[1]

Event dates, source publication dates and our observation time (November 21, 2026) are recorded separately. Observation time is when DarkFire first collected the record, not when the activity occurred.

04Targets and geography

TargetRoleLocationPrecision and basis
West Virginia LegislatureAffected organization, named by reportingCharleston, West Virginia, United Statescity · Organization location named by reporting

Locations describe affected organizations or countries as stated by the sources. They never indicate where an attacker operates from.

05Attribution assessment

Attributed actor
Not attributed
Assessed by
No assessment
Confidence
unknown
Sources

DarkFire aggregates attribution published by the named assessing organization; it does not make its own attribution. Event evidence, actor attribution and location precision are separate judgments.

06Technical behavior

No incident-specific procedure evidence has been recorded yet.

Techniques listed here are the behaviors described for this incident, not the actor's full ATT&CK catalog.

EVIDENCEACTOR AND TECHNIQUESThe Dominion PostNovember 20, 2026West Virginia Legislatu…

07Software and indicators

No publicly shareable indicators are recorded for this incident.

08Business exposure and priorities

Organizations in public sector should review whether they share the conditions described in the sources: the same technology, supplier relationships or access paths. Relevance is a reason to examine exposure, not a finding of compromise.

09Defensive actions

No actor-level defensive guidance is linked.

From the dossier. For each action, name a control owner, the supporting evidence and a completion criterion.

10Analytic gaps

  • The core claims rest on a single publishing organization; independent corroboration has not been recorded.
  • Whether access persists at any affected organization is unknown unless newer evidence is published.

11Source notes and changes

  1. [1]Legislature responds to cyberattack on networkThe Dominion Post · published November 20, 2026 · collected November 21, 2026

Version 1, published November 21, 2026. No corrections recorded. Report an error to have it reviewed; corrections and retractions keep the previous version visible.