Between 2018 and October 2022, 330 individual ransomware attacks were carried out against US government organizations, potentially impacting more than 230 million people and costing an estimated $70 billion in downtime alone.
Over the last few years, ransomware has become a huge cause for concern for all kinds of organizations. This is no more true than in government entities, where attacks can cause huge disruptions to key infrastructures and services, such as 911 dispatch centers, sheriff’s offices, city councils, and utilities. Government employees are often left stranded without their systems and have to resort to pen and paper. In some cases, organizations may be able to restore lost data using backups, but in many cases, they are forced to either pay extortionate ransom demands or make the costly decision to rebuild their systems from scratch.
So, what is the true cost of these ransomware attacks across government agencies in the US, how has the ransomware threat changed over the last five years, and what has happened so far in 2022?
To find out, our team gathered information on ransomware attacks that affected government organizations since 2018. The majority of these attacks are aimed at stopping processes, interrupting services, and causing disruption, not stealing data. Therefore, to gauge the impact, we’ve looked at the population of the town, city, or state affected to see how many people could have been impacted by these disruptions.
Our team sifted through several different resources—specialist IT news, data breach reports, and government websites—to collate as much data as possible on ransomware attacks on US government providers. We then applied data from studies on the cost of downtime to estimate a range for the likely cost of ransomware attacks to government organizations. Due to the limitations with uncovering these types of breaches, we believe the figures only scratch the surface of the problem.
Key findings from 2018 to October 2022
- 330 individual ransomware attacks on government organizations–2019 saw the highest number, accounting for 35 percent (116) of all attacks
- 523,942 individual records affected since 2018–2021 saw the highest number of breached records, accounting for nearly 39 percent (202,376) of the total
- Just over 230 million individuals may have been impacted by these attacks (through services being unavailable, for example)–2019 accounted for around 33 percent (76,900,161) of this
- Ransomware amounts varied from $1,000 to $5.3 million
- Hackers demanded nearly $36.5 million (72 ransom amounts were revealed)
- Hackers received $5 million in payments from 27 of these 72 cases–however, entities are more likely to disclose that they haven’t paid the ransom than if they have
- Downtime varied from minimal disruption (thanks to frequent data backups) to five months (152 days) as noted by the City of New Bedford in 2019
- On average, government organizations lost 17 days to downtime, varying from six days in 2022 to over 20 days in 2018
- Based on the average downtime per year, government organizations lost an estimated 5,642 days to downtime
- The overall cost of these attacks is estimated at $70.4 billion–2019 accounted for 34 percent ($23.7bn) of these costs
- Ryuk, Sodinokibi, DoppelPaymer, and Conti were the most prolific hackers (where the entity disclosed the hacker name or the hacker claimed responsibility for the attack)
Which state had the most ransomware attacks on government organizations from 2018 to October 2022?
If we look at overall figures by state, there isn’t too much of a surprise. One of the most heavily-populated states in the US, Texas, had the highest number of attacks (35) and the greatest number of people impacted (72.5 million). This was followed by Georgia with 25 attacks and 23.9 million people potentially affected. Making up the rest of the top five most affected states were California (19 attacks), Florida (18 attacks), and Pennsylvania (14 attacks).
The reason for such a high number of people being affected in Texas is due to two statewide departments being attacked – the Texas Court of Administration and the Texas Department of Transportation. These attacks potentially impacted each Texan twice.
However, the second-most-impacted state based on the percent of the population affected is Georgia. Much the same as Texas, Georgia’s state’s population may also have been affected twice due to the Georgia Department of Public Safety and Georgia’s Administrative Office of the Courts suffering ransomware attacks in 2019.
How much did these ransomware attacks cost government organizations?
As we’ve already seen, ransom demands varied dramatically, ranging from $1,000 to $5.3 million. Only 22 percent of the organizations impacted revealed the specific ransom amount demanded. Understandably, organizations don’t want to discuss ransom amounts or whether they have paid these as doing so may incentivize further attacks.
In 2021, North Carolina and Florida introduced cybersecurity laws that ban government entities from paying ransom demands. Since their introduction, both states have witnessed two government ransomware attacks. While few in number, these do coincide with a general dip in government ransomware attacks US-wide. Therefore, it is difficult to say whether or not the new laws have had any effect on hackers targeting government organizations within these states.
Some of the largest ransom payments from 2018 to September 2022 include:
- In July 2019, the City of New Bedford received a ransom demand of $5.3 million after being attacked by the notorious ransomware group Ryuk. The city refused to pay the ransom but did disclose that the total cost of the incident hit $1 million.
- Just 3 months ago, in August 2022, the City of Wheat Ridge was attacked by the ALPHV/Black Cat ransomware strain and was instructed to pay $5 million in ransom. The city refused to pay but did struggle to get systems back up and running even three weeks later.
- In February 2020, North Miami Beach Police Department also received a ransom demand for $5 million. There is very little information about this attack and it is still unknown if any payment was made, how much downtime occurred as a result, or which group is responsible.
- In June 2019, the City of Riviera Beach paid the highest known ransom in recent years, a total of $594,000 was paid to Ryuk (although this has not been confirmed).
- In April 2021, the Washington Metropolitan Police Department faced a $4 million ransom demand. It is unknown whether that was paid but Babuk was recognized as the attacking group responsible.
- In April 2019, Imperial County in California was also attacked by Ryuk ransomware, the hackers demanded $1.2 million in ransom, which was refused by the county. The county did reveal that the total cost of the incident amounted to $4 million with six days of downtime spent rebuilding their system.
- In March 2022, Plainfield Town received a ransom demand of $199,000 that officials refused to pay. They did, however, spend $350,000 on restoring systems, nearly double the ransom amount.
Adding in the cost of downtime to ransomware attacks
Unfortunately, even when organizations manage to avoid paying ransom, they are often left with extortionate costs as they try to restore their systems and add extra layers of security to prevent further attacks.
Systems can be taken down for hours, days, weeks, and even months. And as we’ve already noted, the average downtime across all years was 17 days. The cost of this downtime can vary dramatically.
A 2017 estimate places the average cost per minute of downtime across 20 different industries at $8,662. This would mean the cost of downtime to government organizations in the last five years has potentially amounted to over $70 billion. 2019 was the greatest year so far, making up nearly 34 percent ($23.7bn) of the total estimated cost of downtime.
While these figures seem astronomical, they are in line with some of the costs revealed by organizations in previous years (the true cost of attacks often takes over a year to calculate as recovery processes are ongoing).
- The City of Baltimore was attacked by RobbinHood ransomware in May 2019. It spent a reported $18.2 million recovering from this attack, the highest amount ever recorded.
- The City of Atlanta spent an estimated $17 million recovering from its SamSam ransomware attack in March 2018.
- The City of Tulsa, in May 2021 spent $2 million on recovery costs with a further $300,000 in costs every year from then with the introduction of cloud services.
- In January 2022, Bernalillo County spent $2 million in recovery costs, spending several days reconstructing affected systems.
- La Salle County in Illinois spent $500,000 in recovery costs in February 2020 after a ransomware attack.
- As mentioned above, the Town of Plainfield spent $350,000 in recovery costs in March 2022. With a population of just 15,000 people, this would have been a huge payment for them.
Ransomware attacks on government organizations by year
According to our findings, 2019 was the worst year for ransomware attacks on government organizations. It accounted for just over 35 percent of the cases from the last five years. The number of records affected slowly increased to a peak in 2021. The number of records lost in 2022 is less than half of 2021’s figures, but the average ransom amount was higher in 2022 than any other year so far.
- Number of attacks:
- 2022 (to October) – 27
- 2021 – 54
- 2020 – 90
- 2019 – 116
- 2018 – 43
- Number of records potentially impacted:
- 2022 (to October) – 59,873
- 2021 – 202,376
- 2020 – 198,393
- 2019 – 63,300
- 2018 – N/A
- Average ransom amount:
- 2022 (to October) – $1,197,200
- 2021 – $835,156
- 2020 – $550,414
- 2019 – $534,750
- 2018 – $59,813
- Ransom amounts demanded (known cases):
- 2022 (to October) – $5.99 milion (5 cases)
- 2021 – $6.68 million (8 cases)
- 2020 – $11 million (20 cases)
- 2019 – $11.8 million (22 cases)
- 2018 – $1.02 million (17 cases)
- Ransom amounts paid (known cases)
- 2022 (to October) – $787,000 (3 cases)
- 2021 – $391,250 (2 cases)
- 2020 – $1.75 million (9 cases)
- 2019 – $1.97 million (6 cases)
- 2018 – $123,324 (7 cases)
- Average downtime:
- 2022 (to October) – 5.96 days
- 2021 – 18.38 days
- 2020 – 19.05 days
- 2019 – 16.38 days
- 2018 – 20.34 days
- Downtime caused (known cases):
- 2022 (to October) – 42 days (7 cases)
- 2021 – 349 days (19 cases)
- 2020 – 781 days (41 cases)
- 2019 – 1,114 days (68 cases)
- 2018 – 427 days (21 cases)
- Estimated downtime caused (based on known cases and average in unknown):
- 2022 (to October) – 161 days
- 2021 – 992 days
- 2020 – 1,714 days
- 2019 – 1,900 days
- 2018 – 875 days
- Estimated cost of downtime:
- 2022 (to October) – $2bn
- 2021 – $12.4bn
- 2020 – $21.4bn
- 2019 – $23.7bn
- 2018 – $10.9bn
These waves of attacks may relate to different types of ransomware being developed. However, many organizations fail to disclose the type of ransomware used in the attack, so it is difficult to know if this is the case.
From those that did reveal the type of ransomware used, SamSam caused the most destruction in 2018. In 2019, Sobinokibi took precedence along with the Ryuk ransomware strain. Ryuk continued to wreak havoc throughout 2020 and 2021 but was joined by DopplePaymer and Conti. So far in 2022, ALPHV/Black Cat ransomware has become a dominant threat, being responsible for the four latest attacks on government organizations (Wheat Ridge, Alexandria, Fremont County, and Suffolk County), at the time of writing.
Ransomware attack costs on government organizations by year
TOTAL | 2022 (to October) | 2021 | 2020 | 2019 | 2018 | |||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
State | Attacks | # of People Potentially Affected | # of Records Affected | Cost of Downtime ($) | Attacks | # of People Potentially Affected | # of Records Affected | Cost of Downtime ($) | Attacks | # of People Potentially Affected | # of Records Affected | Cost of Downtime ($) | Attacks | # of People Potentially Affected | # of Records Affected | Cost of Downtime ($) | Attacks | # of People Potentially Affected | # of Records Affected | Cost of Downtime ($) | Attacks | # of People Potentially Affected | # of Records Affected | Cost of Downtime ($) |
Alabama | 7 | 659,184 | 1,600 | 1,188,953,050 | 0 | 0 | 0 | 0 | 1 | 414,809 | 1,600 | 37,419,840 | 4 | 215,104 | 0 | 693,514,368 | 1 | 17,231 | 0 | 204,312,326 | 1 | 12,040 | 0 | 253,706,515 |
Alaska | 2 | 112,164 | 0 | 1,014,576,595 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 112,164 | 0 | 1,014,576,595 |
Arizona | 1 | 54,018 | 0 | 87,312,960 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 54,018 | 0 | 87,312,960 | 0 | 0 | 0 | 0 |
Arkansas | 4 | 243,849 | 0 | 1,418,461,402 | 0 | 0 | 0 | 0 | 1 | 63,118 | 0 | 229,258,886 | 2 | 154,153 | 0 | 935,496,000 | 0 | 0 | 0 | 0 | 1 | 26,578 | 0 | 253,706,515 |
California | 19 | 9,020,784 | 9,670 | 3,942,803,808 | 0 | 0 | 0 | 0 | 5 | 2,110,191 | 0 | 633,143,693 | 5 | 2,102,519 | 9,670 | 1,324,662,336 | 7 | 1,419,744 | 0 | 1,810,371,859 | 2 | 3,388,330 | 0 | 174,625,920 |
Colorado | 7 | 6,780,520 | 0 | 1,521,864,893 | 2 | 79,614 | 0 | 336,279,629 | 0 | 0 | 0 | 0 | 1 | 30,687 | 0 | 237,615,984 | 3 | 911,483 | 0 | 424,091,520 | 1 | 5,758,736 | 0 | 523,877,760 |
Connecticut | 9 | 7,368,059 | 0 | 1,402,620,336 | 1 | 15,173 | 0 | 74,340,749 | 0 | 0 | 0 | 0 | 1 | 122,105 | 0 | 12,473,280 | 2 | 27,407 | 0 | 291,625,286 | 5 | 7,203,374 | 0 | 1,024,181,021 |
Delaware | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
District of Columbia | 2 | 689,545 | 0 | 433,571,213 | 0 | 0 | 0 | 0 | 1 | 689,545 | 0 | 229,258,886 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 204,312,326 | 0 | 0 | 0 | 0 |
Florida | 18 | 1,606,707 | 60,934 | 4,101,626,082 | 0 | 0 | 0 | 0 | 2 | 332,399 | 0 | 491,197,766 | 7 | 726,209 | 934 | 2,284,481,232 | 7 | 459,556 | 60,000 | 1,064,968,646 | 2 | 88,543 | 0 | 260,978,437 |
Georgia | 25 | 23,851,997 | 9,205 | 6,279,049,152 | 1 | 50,000 | 0 | 74,340,749 | 2 | 909,287 | 2,000 | 458,517,773 | 7 | 527,340 | 7,000 | 1,449,395,136 | 10 | 21,659,365 | 205 | 2,359,196,179 | 5 | 706,005 | 0 | 1,937,599,315 |
Hawaii | 1 | 190,000 | 0 | 229,258,886 | 0 | 0 | 0 | 0 | 1 | 190,000 | 0 | 229,258,886 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Idaho | 6 | 1,393,390 | 1,508 | 781,326,259 | 1 | 34,971 | 973 | 74,340,749 | 2 | 801,482 | 535 | 403,884,806 | 1 | 36,250 | 0 | 237,615,984 | 1 | 481,587 | 0 | 15,591,600 | 1 | 39,100 | 0 | 49,893,120 |
Illinois | 10 | 13,468,021 | 661 | 1,537,705,958 | 1 | 150,372 | 0 | 74,340,749 | 3 | 12,957,715 | 661 | 304,098,566 | 3 | 285,674 | 0 | 527,120,813 | 1 | 40,647 | 0 | 124,732,800 | 2 | 33,613 | 0 | 507,413,030 |
Indiana | 7 | 7,549,701 | 281 | 1,219,512,586 | 1 | 600 | 0 | 62,366,400 | 1 | 69,093 | 0 | 174,625,920 | 1 | 45,370 | 281 | 237,615,984 | 3 | 702,419 | 0 | 491,197,766 | 1 | 6,732,219 | 0 | 253,706,515 |
Iowa | 1 | 23,774 | 0 | 174,625,920 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 23,774 | 0 | 174,625,920 |
Kansas | 3 | 180,204 | 0 | 390,912,595 | 2 | 156,001 | 0 | 161,653,709 | 1 | 24,203 | 0 | 229,258,886 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Kentucky | 7 | 1,720,709 | 0 | 2,015,183,117 | 1 | 13,169 | 0 | 9,354,960 | 2 | 196,769 | 0 | 1,364,327,366 | 2 | 791,622 | 0 | 387,295,344 | 2 | 719,149 | 0 | 254,205,446 | 0 | 0 | 0 | 0 |
Louisiana | 10 | 6,144,586 | 0 | 1,536,209,165 | 2 | 81,545 | 0 | 148,681,498 | 1 | 10,471 | 0 | 87,312,960 | 2 | 780,288 | 0 | 475,231,968 | 5 | 5,272,282 | 0 | 824,982,739 | 0 | 0 | 0 | 0 |
Maine | 7 | 56,054 | 95 | 1,029,295,066 | 0 | 0 | 0 | 0 | 4 | 20,764 | 0 | 583,250,573 | 0 | 0 | 0 | 0 | 2 | 24,449 | 95 | 408,624,653 | 1 | 10,841 | 0 | 37,419,840 |
Maryland | 5 | 7,289,844 | 0 | 754,238,037 | 0 | 0 | 0 | 0 | 1 | 6,038,000 | 0 | 229,258,886 | 1 | 31,929 | 0 | 87,312,960 | 2 | 626,425 | 0 | 428,831,366 | 1 | 593,490 | 0 | 8,834,824 |
Massachusetts | 13 | 8,823,351 | 37,957 | 3,092,375,578 | 2 | 189,744 | 36,080 | 148,681,498 | 3 | 743,919 | 1,877 | 687,776,659 | 2 | 89,478 | 0 | 475,231,968 | 6 | 7,800,210 | 0 | 1,780,685,453 | 0 | 0 | 0 | 0 |
Michigan | 3 | 454,610 | 2,000 | 486,582,653 | 1 | 24,000 | 2,000 | 74,340,749 | 0 | 0 | 0 | 0 | 1 | 24,797 | 0 | 237,615,984 | 1 | 405,813 | 0 | 174,625,920 | 0 | 0 | 0 | 0 |
Minnesota | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Mississippi | 3 | 126,517 | 0 | 433,571,213 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 52,392 | 0 | 408,624,653 | 1 | 74,125 | 0 | 24,946,560 |
Missouri | 9 | 290,530 | 114,092 | 1,232,609,530 | 0 | 0 | 0 | 0 | 3 | 81,041 | 513 | 291,625,286 | 3 | 168,740 | 113,579 | 562,544,928 | 2 | 26,668 | 0 | 124,732,800 | 1 | 14,081 | 0 | 253,706,515 |
Montana | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Nebraska | 4 | 598,526 | 0 | 595,224,922 | 1 | 565,739 | 0 | 74,340,749 | 1 | 23,638 | 0 | 229,258,886 | 1 | 5,660 | 0 | 87,312,960 | 1 | 3,489 | 0 | 204,312,326 | 0 | 0 | 0 | 0 |
Nevada | 3 | 654,019 | 0 | 446,044,493 | 0 | 0 | 0 | 0 | 1 | 1,500 | 0 | 229,258,886 | 1 | 651,319 | 0 | 12,473,280 | 1 | 1,200 | 0 | 204,312,326 | 0 | 0 | 0 | 0 |
New Hampshire | 2 | 29,791 | 39,051 | 316,571,846 | 0 | 0 | 0 | 0 | 1 | 0 | 53 | 229,258,886 | 1 | 29,791 | 38,998 | 87,312,960 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
New Jersey | 8 | 1,385,612 | 14,599 | 2,017,802,506 | 1 | 330,151 | 14,599 | 74,340,749 | 0 | 0 | 0 | 0 | 3 | 372,316 | 0 | 1,459,997,424 | 3 | 657,269 | 0 | 433,571,213 | 1 | 25,876 | 0 | 49,893,120 |
New Mexico | 5 | 2,886,436 | 0 | 861,903,648 | 1 | 679,037 | 0 | 37,419,840 | 0 | 0 | 0 | 0 | 3 | 2,163,027 | 0 | 649,857,888 | 0 | 0 | 0 | 0 | 1 | 44,372 | 0 | 174,625,920 |
New York | 12 | 23,007,388 | 0 | 2,383,394,342 | 2 | 2,449,738 | 0 | 148,681,498 | 2 | 297,043 | 0 | 291,625,286 | 4 | 153,598 | 0 | 714,407,112 | 4 | 20,107,009 | 0 | 1,228,680,446 | 0 | 0 | 0 | 0 |
North Carolina | 13 | 11,828,423 | 2,134 | 4,539,525,523 | 1 | 65,000 | 0 | 74,340,749 | 1 | 4,175 | 0 | 229,258,886 | 3 | 451,695 | 2,134 | 1,783,679,040 | 5 | 10,902,182 | 0 | 689,273,453 | 3 | 405,371 | 0 | 1,762,973,395 |
North Dakota | 1 | 17,017 | 0 | 229,258,886 | 0 | 0 | 0 | 0 | 1 | 17,017 | 0 | 229,258,886 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Ohio | 12 | 2,671,009 | 189,421 | 3,208,127,616 | 0 | 0 | 0 | 0 | 2 | 1,241,009 | 189,008 | 458,517,773 | 1 | 390,357 | 413 | 124,732,800 | 6 | 985,824 | 0 | 2,067,570,893 | 3 | 53,819 | 0 | 557,306,150 |
Oklahoma | 4 | 452,317 | 0 | 579,134,390 | 0 | 0 | 0 | 0 | 1 | 401,190 | 0 | 229,258,886 | 2 | 41,563 | 0 | 324,928,944 | 1 | 9,564 | 0 | 24,946,560 | 0 | 0 | 0 | 0 |
Oregon | 4 | 203,733 | 0 | 553,065,235 | 1 | 127,216 | 0 | 37,419,840 | 0 | 0 | 0 | 0 | 2 | 66,749 | 0 | 261,938,880 | 0 | 0 | 0 | 0 | 1 | 9,768 | 0 | 253,706,515 |
Pennsylvania | 14 | 1,753,250 | 9,352 | 2,849,021,885 | 1 | 32,761 | 0 | 74,340,749 | 1 | 5,878 | 0 | 87,312,960 | 7 | 838,799 | 9,352 | 1,663,311,888 | 4 | 526,913 | 0 | 770,349,773 | 1 | 348,899 | 0 | 253,706,515 |
Puerto Rico | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Rhode Island | 6 | 508,850 | 6,221 | 965,930,803 | 2 | 392,397 | 6,221 | 148,681,498 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 4 | 116,453 | 0 | 817,249,306 | 0 | 0 | 0 | 0 |
South Carolina | 4 | 438,095 | 50 | 2,395,493,424 | 0 | 0 | 0 | 0 | 1 | 62,680 | 50 | 1,895,938,560 | 1 | 25,557 | 0 | 237,615,984 | 1 | 30,073 | 0 | 174,625,920 | 1 | 319,785 | 0 | 87,312,960 |
South Dakota | 2 | 12,993 | 0 | 478,225,555 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 7,291 | 0 | 224,519,040 | 1 | 5,702 | 0 | 253,706,515 |
Tennessee | 6 | 615,204 | 0 | 661,707,504 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 4 | 497,258 | 0 | 487,081,584 | 2 | 117,946 | 0 | 174,625,920 | 0 | 0 | 0 | 0 |
Texas | 35 | 72,503,050 | 8,017 | 6,981,918,480 | 2 | 1,986,100 | 0 | 99,287,309 | 2 | 9,085,605 | 0 | 229,258,886 | 10 | 59,122,481 | 5,017 | 2,476,195,546 | 20 | 2,305,368 | 3,000 | 3,923,470,224 | 1 | 3,496 | 0 | 253,706,515 |
Utah | 2 | 47,408 | 0 | 403,884,806 | 0 | 0 | 0 | 0 | 1 | 42,357 | 0 | 229,258,886 | 0 | 0 | 0 | 0 | 1 | 5,051 | 0 | 174,625,920 | 0 | 0 | 0 | 0 |
Vermont | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Virginia | 5 | 10,238,912 | 0 | 1,315,681,574 | 0 | 0 | 0 | 0 | 3 | 8,526,334 | 0 | 687,776,659 | 1 | 1,700,000 | 0 | 374,198,400 | 0 | 0 | 0 | 0 | 1 | 12,578 | 0 | 253,706,515 |
Washington | 6 | 2,262,662 | 9,091 | 1,108,188,562 | 0 | 0 | 0 | 0 | 1 | 1,800,000 | 0 | 1,559,160 | 2 | 105,032 | 9,091 | 124,732,800 | 2 | 356,428 | 0 | 728,190,086 | 1 | 1,202 | 0 | 253,706,515 |
West Virginia | 3 | 82,332 | 6,079 | 832,716,173 | 0 | 0 | 0 | 0 | 2 | 15,076 | 6,079 | 458,517,773 | 0 | 0 | 0 | 0 | 1 | 67,256 | 0 | 374,198,400 | 0 | 0 | 0 | 0 |
Wisconsin | 2 | 143,764 | 1,924 | 349,251,840 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 143,764 | 1,924 | 349,251,840 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Wyoming | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
How is 2022 looking for ransomware attacks on government organizations so far?
So far this year, we have noted 27 ransomware attacks on government organizations. This would suggest a lower amount than 2021, but with so many attacks often going unreported until months later, it is highly likely we will see an increase in the number of attacks, number of records affected, and amount of downtime.
We can already see this with the ransom demands made so far this year. The average ransom amount received by government organizations has hit the million-dollar mark for the first time: $1,197,200. While this is only an average based on the five known ransom demands this year, it does suggest that ransomware groups are asking for larger sums of money.
In general, 2022 so far has been far quieter for ransomware attacks across all industries, as our map of US ransomware attacks shows (updated daily). The same can be said for worldwide ransomware attacks too. It is often months later when organizations realize that records have been compromised that they are put forward into the public eye and can be confirmed as a ransomware attack.
Methodology
Using the database from our US ransomware attack map, our research found 330 ransomware attacks in total. From this, we were able to ascertain how much ransom had been demanded and how much had been paid.
In the case of Texarkana Water Utility, which affected residents in both Texas and Arkansas, the attack has been counted in both states (as an attack). But in yearly figures, it is included as a single attack. The same can be said for the Washoe Tribe of Nevada and California, which was added in the same way. Both of these were omitted from state totals for the cost of downtime due to the inability to divide the total amount lost by each state.
Only one attack cannot be pinpointed to a specific month and has been omitted from these comparisons. This was the Azusa Police Department attack that occurred in 2018.
If no specific figures were given for downtime, i.e. “several days,” “one month” or “back to 80% after 6 weeks” were quoted, we created estimates from these figures based on the lowest figure they could be. For example, several days was calculated as 3, one month was calculated as the number of days in the month the attack happened, and the number of weeks quoted in % recovery statements was used (e.g. 6 weeks per the previous example).
Researcher: Charlotte Bond