Cybersecurity

West Virginia Legislature Takes Website Offline After Cyber Incident: What We Know So Far

Published By Shivam Sharma7 min read
West Virginia State Capitol with its gold dome seen through a window, with a laptop showing a padlock icon in the foreground

West Virginia’s state legislature is responding to a cyberattack that has taken down its website and impacted its IT systems. The Legislature identified a cybersecurity incident on Thursday 19 November, shut down systems and remote access the same day, and its public website was down on Friday 20 November while officials work out what was compromised. The attack started on Thursday and continued through Friday, Ann Ali, Deputy Chief of Staff and Communications Director for the House of Delegates, told The Record. Whether it was ransomware, and whether any data was taken, has not been confirmed.

What happened, and when

The incident moved fast on Thursday, then went public on Friday. This is the timeline as the sources establish it:

When What happened
Thu 19 Nov, morning The Dominion Post reports IT staff noticed unusual activity on the Legislature’s internal computer systems; the IT team quickly shuts down its systems as well as remote access
Thu 19 Nov, afternoon West Virginia Pulse reports the incident began, or was discovered, that afternoon; the attack started on Thursday, Ali told The Record. The sources do not give a single agreed discovery time
Fri 20 Nov An internal memo goes to lawmakers; Ali issues the public statement; wvlegislature.gov was down as part of the review; some systems are still offline Friday afternoon, though the effects on legislative staff are described as minimal and work continues as normal
Sat 21 Nov The Record publishes its report; The Intelligencer / Sunday News-Register publishes the internal-memo details, including the specialist roster and the forensic question. As of our check on Sunday 22 November, no new official update had been found

Ali’s statement, as reported by the Dominion Post, opens: “On November 19, 2026, the West Virginia Legislature identified a cybersecurity incident affecting its information technology systems.” She continued: “However, based on what we know so far, the incident appears to be limited to the Legislature’s computer systems. We have no evidence showing that other state agencies or offices are affected.” And on the response: “Upon discovery, the relevant teams immediately took steps to contain the incident and began an investigation with the help of outside cybersecurity specialists. In connection with the investigation, access to certain Legislature IT systems has been temporarily disabled.”

Ali added that the investigation is ongoing and that “any relevant findings will be shared as soon as it is appropriate to do so.” Our own check of wvlegislature.gov on Sunday 22 November returned no response, which is consistent with the site still being down but proves nothing on its own, so this article does not claim the site was still down on 22 November. What is established is that it was down on Friday 20 November and no restoration had been announced then.

The specialist roster says what the statement will not

Officials will not say the word “ransomware.” Ali did not respond to The Record’s follow-up questions about whether it was a ransomware attack. The internal memo is the only official document to come close: it described Thursday’s unusual activity as “a possible ransomware attack.”

But the reporting names the outside specialists, and the roster is revealing. Charles River Associates, an independent forensic firm, is among the outside specialists investigating. Scott Koller, an attorney with the Los Angeles-based Clark Hill law firm who specialises in cybersecurity, is among the outside specialists reported by the Dominion Post. And Alvaka is on the job too, a firm that specialises in restoring systems after ransomware attacks. According to the memo, the West Virginia Office of Technology and the West Virginia Fusion Center are also involved.

That roster is our reading, not something officials confirmed, and the article labels it as such: hiring a firm that specialises in restoring systems after ransomware attacks is the strongest public signal about the incident’s likely nature. The memo’s own words stop at “possible,” and Ali’s silence on the question is one other data point, alongside the roster discussed above. Read together, they point in one direction without proving it.

The forensic question is stated plainly in the memo: “An important part of the forensic investigation is determining whether any confidential (or) sensitive information was accessed or compromised. The review is ongoing, and no conclusions have been reached yet. If the investigation finds that sensitive information (is) involved, the Legislature will evaluate and meet any notification or other obligations.” That sentence is the whole ballgame for anyone whose data might be involved, and it is the reason this article cannot tell you whether your information was taken: nobody knows yet, including the Legislature.

What should I do if I use the West Virginia Legislature’s website?

There is no specific protective step indicated by the sources yet. No data theft has been confirmed, and it is not yet known whether any personal information is involved. Wait for the Legislature’s own update, and as a general precaution, treat any message about the incident asking for your details as a fake.

  1. Check the Legislature’s official channels for the restoration update instead of trusting social media posts about it.
  2. Ignore any email or message claiming to be from the Legislature that asks for your password or personal details.
  3. Type wvlegislature.gov into your browser yourself instead of clicking a link in an email about the incident.
  4. A credit freeze or monitoring is a personal decision; no source recommends or rules it out yet.
  5. Keep a copy of any message you sent the Legislature this week, in case its reply is delayed.

That last point matters because the website is where West Virginians normally go to look up bills, find their lawmakers and read the state code. With the site offline, residents and local officials who count on it will have to wait a little while longer until it is back up. If you were waiting on a reply from a lawmaker’s office, a reply may be delayed because email and productivity sign-ins were affected, so keep a copy of any message you sent.

Why the impact is limited: the Legislature is not in session

The outage looks dramatic, a whole state’s legislature offline, but its practical impact is narrower than it first appears. The 2026 Regular Session adjourned sine die on 14 March 2026, and the Legislature is not due to convene again until 13 January 2027. There is no live lawmaking to interrupt. What is interrupted is public access: the bill lookup, the lawmaker directory and the state code that residents and local officials use every day.

The scale is real even so. The Legislature is split between a Senate and a House of Delegates with 134 total members representing the state’s 1.7 million residents, according to The Record. That is the difference between this incident and the local attacks in this watch: Winona County was a county government, and South Portland, Maine, was a city. This is a state-level body, and its public website serves an entire state. The containment was fast, though. The shutdown was on Thursday, and the statement came on Friday afternoon, more than a day after the activity was first noticed.

What the Legislature has not said

Six things remain unanswered, and the article lists them plainly rather than filling the gaps. Whether it was ransomware: Ali did not respond to the question, and the memo says only “possible.” Whether any data was taken: no source confirms or denies it, and the forensic review has reached no conclusions. Who was behind it: no hacking group has taken credit as of Friday, according to The Record. How the attacker got in: no vector has been disclosed. When the website and the disabled systems will be back: no restoration timetable has been announced. And whether legislator or staff personal data was involved: no source says specifically whether it was; the memo addresses confidential or sensitive information in general and says no conclusions have been reached yet.

What to watch next

The first thing to watch is a Legislature update confirming or ruling out ransomware, and the data-theft determination that follows it. The second is whether any group claims responsibility. The third is the restoration of wvlegislature.gov, which needs a fresh check rather than our inconclusive one. The fourth is the Nevada precedent: Governing reported that an August 2025 ransomware attack on Nevada affected more than 60 agencies and disrupted computer systems for nearly 30 days. Nevada was a confirmed ransomware attack affecting more than 60 agencies statewide; West Virginia is so far only a possible ransomware attack apparently limited to the Legislature’s systems. West Virginia’s systems were shut down on Thursday, the day the activity was noticed.

The honest summary, three days in: a confirmed incident, a website taken offline as part of the review, outside specialists involved in the investigation, and the two questions that matter, ransomware and data, still unanswered.