West Virginia Legislature Takes Systems Offline After Cyberattack
West Virginia's state legislature is responding to a cyberattack that has taken down its website and affected its IT systems. Ann Ali, deputy chief of staff for the House of Delegates, told Recorded Future News that the attack began on Thursday and was still continuing on Friday.
Ali said the relevant teams moved immediately to contain the incident and started an investigation with the help of outside cybersecurity specialists. As part of that work, access to certain Legislature IT systems has been temporarily disabled. Based on what is known so far, she said the incident appears to be limited to the Legislature's own computer systems, and that no other state agencies or offices are affected.
The investigation is ongoing. Ali did not respond to follow-up questions about whether the incident is a ransomware attack, and no hacking group had claimed responsibility as of Friday. The Legislature is made up of a Senate and a House of Delegates, with 134 members representing the state's 1.7 million residents.
The incident comes amid heavy pressure on public bodies in the United States. Several West Virginia municipalities have faced ransomware attacks in recent years, including the cities of Beckley and Westmoreland. Security research firm Comparitech tracked 132 ransomware attacks on U.S. government bodies in the third quarter, a 91% increase on the same period last year. At least 41 of those hit municipalities. This week, residents of South Portland, Maine, lost access to critical city services after a cyberattack, and Minnesota's Otter Tail County notified its 61,000 residents of a data breach caused by a July ransomware attack.
Why it matters
The Legislature's response shows that containing an incident often means deliberately taking systems offline, which disrupts normal operations even if the attacker is kept out. Any organisation that depends on a public website and internal IT should decide in advance who can authorise that shutdown and how it will work without those systems. The early claim that the incident is limited to one environment is also still unverified while the investigation continues.
What to do
- Define who can authorise disabling access to affected IT systems during an incident.
- Arrange an outside incident response specialist before you need one.
- Confirm which of your systems and services share infrastructure, so you can judge whether an incident is truly contained.
- Prepare a communications plan for when your website is unavailable.