Skip to content

Ransomware disrupts Grand Traverse County and Traverse City

Summary

Grand Traverse County Government logo

A June 12, 2024, ransomware attack disrupted the shared Grand Traverse County and Traverse City network, government records, payments, courts and dispatch tools. Emergency calls and radio communications continued through workarounds. Recovery remained incomplete in late June; later reporting described personal-information notifications.

Key facts

Timeline

  • Incident start:
    ? Earliest known or assessed start of malicious activity or incident activity.
  • First public signal:
    ? Earliest public indication of an outage, disruption, closure or other observable incident impact. The signal does not need to mention cybersecurity.
  • First public cyber evidence:
    ? Earliest credible public information connecting the incident or disruption to malicious cyber activity.
  • Official cyber disclosure:
    ? First official acknowledgment by the affected organization or an authoritative public body that the incident was cyber-related.
  • Last impact seen:
    ? Latest public indication that disruption, degraded operations, recovery work or unresolved impact was still ongoing.

Primary victim organization

Incident characteristics

Assessments

Attack mechanisms

  • Ransomware

    Malware that encrypts systems or data, typically accompanied by a ransom demand.

Data impacts

  • Data unavailable

    Authorized users could not access required data because of the incident, even when the data was not encrypted, deleted, or destroyed.

Operational impacts

  • Partial service outage

    A service, system, platform, or operational capability remained available only in part or with significant limitations.

  • Degraded service

    Services remained available but with reduced performance, reliability, functionality, capacity, or responsiveness.

  • Network outage

    Internal or external network connectivity was unavailable or materially impaired.

  • Internet access disruption

    The organization lost or materially restricted internet connectivity.

  • Phone service disruption

    Telephone, voice-over-IP, call-center, or related voice communication services were unavailable or materially impaired.

  • Internal systems unavailable

    Internal business, administrative, operational, or staff-facing systems were unavailable.

  • Application unavailable

    A specific application or software platform became unavailable or unusable.

  • Payment processing disruption

    The organization could not process, receive, issue, reconcile, or record payments normally.

  • Transaction processing disruption

    Business, financial, customer, administrative, or operational transactions could not be completed normally.

  • Records access disruption

    Staff, customers, patients, students, residents, or other users could not access records or case information normally.

  • Records processing disruption

    The organization could not create, update, search, file, approve, transmit, or otherwise process records normally.

  • Dispatch disruption

    Dispatch, routing, assignment, coordination, or response-management functions were unavailable or materially impaired.

  • Public safety operations disrupted

    Police, fire, emergency medical, corrections, emergency management, or other public-safety operations were materially affected.

  • Government services disrupted

    Public administrative, licensing, permitting, court, tax, records, benefits, or other government services were materially affected.

  • Event or activity cancellation

    Scheduled events, meetings, hearings, classes, procedures, programs, or other activities were canceled.

  • Service delay

    Services continued but with longer processing, response, delivery, or completion times.

  • Manual workaround required

    Staff or users had to rely on paper, telephone, in-person, offline, or other manual processes.

  • Alternate service channel required

    The organization redirected users to a different website, office, telephone number, email address, provider, or service channel.

  • Staff unable to work normally

    Employees or contractors were unable to perform normal duties because systems, data, facilities, or communications were unavailable.

  • Customer or public access restricted

    Customers, residents, patients, students, vendors, or members of the public faced access restrictions or could not use services normally.

Extortion indicators

  • Ransom demand

    The victim received a demand for payment in exchange for restoring access, decrypting systems, preventing disclosure, or stopping another threatened action.

Incident narrative

Analyst assessment

Grand Traverse County and Traverse City, Michigan, took their shared office network offline after detecting irregularities June 12, 2024. The city’s initial notice said county staff recognized the problem at 6:06 a.m. and subsequently identified ransomware. That is a detection and containment sequence, not a verified initial intrusion time. The county managed the network for both governments.

The county administrator told The Ticker that ransom demands appeared in “Read Me” emails and files. He said staff had not followed the supplied links. Officials initially reported no evidence of a mass transfer of information, while acknowledging that the confidentiality investigation remained incomplete. Our June 13 report drew on that local reporting.

Operational significance

The shutdown disrupted employee connectivity, government records, selected payments and court proceedings. Staff used mobile connections and alternative processes while computers were evaluated before reconnection. Some court dockets were canceled while other proceedings and filing channels continued. Initially available third-party payment services did not remain uniformly available: June 25 reporting described precautionary suspensions of selected water, sewer, tax and BS&A-integrated payments.

Emergency calls and first-responder radio communications continued. That continuity did not mean dispatch technology was unaffected. In the county dispatch center’s 2024 annual report, Director Jason Torrey said critical supporting systems were compromised and staff lost tools that normally made dispatch more efficient. Employees implemented backup procedures and improvised further workarounds.

A June 27 Record-Eagle report republished by Firehouse said computer-aided dispatch became operational June 25, although bugs remained. Officials estimated that about 80% of county infrastructure was back online, with document-management and other applications still requiring work. These are partial restoration milestones.

The city’s service-impact page says roughly half of water and sewer customers missed June billing and would receive June and July bills together, without late fees. It also lists restored services alongside phone-service gaps. The page was updated over time; its June 14 heading does not date every listed condition. The incident is assessed as presumed resolved, with June 27 providing dated evidence of incomplete restoration and no exact final recovery date established.

Confidence and uncertainty

Confidence is high in ransomware involvement and the shared-network disruption because an affected government explicitly acknowledged both. The dispatch center’s own account confirms loss of supporting tools while explaining how emergency response continued. Traverse City Light & Power used a separate network and was reported unaffected.

An October 2025 report said the county notified 782 people and quoted its notice describing personal information in compromised network locations. It identified names and Social Security numbers. This later notification qualifies the early assurance about an absence of observed mass transfer; it does not establish a public leak or provide a verified theft volume. Notification activity also does not extend the operational outage into 2025.

In The Ticker’s June 25 report, County Administrator Nate Alger said the attackers used the BlackSuit name while their identity remained unknown. This supports qualified attribution with medium confidence; it does not authenticate a group-controlled victim listing or independently establish the operators’ identity. Alger also said the county had not paid a ransom as of that report, which does not resolve every later financial action. The separate April 2024 Traverse City Area Public Schools incident and its Medusa claim do not identify the perpetrators here. The city’s November 2024 move toward separating IT services concerns governance after the attack, rather than proof of continuing outages.

Analytic gaps

The initial access method, precise intrusion window, full scope of copied information, encrypted systems, ransom amount and payment outcome remain unresolved. The complete county and city notification records need further review to distinguish their affected populations and findings. A dated final recovery statement is also needed; later changes to an evolving service page cannot supply an exact historical restoration date.

Threat actor and claim

Source: otherPublished:

Claim details

The Ticker reported June 25, 2024, that Grand Traverse County Administrator Nate Alger said the attackers used the BlackSuit name while their identity remained unknown. This is qualified attribution conveyed by a named affected-government official through local reporting, not an authenticated group-controlled victim-list claim. No verified original post URL or discovery timestamp is established. Alger said no ransom had been paid as of the report; that statement does not resolve later payment history. Separate Traverse City Area Public Schools and Medusa allegations are unrelated.

Organizations involved

Impacted locations

  • Antrim County, Michigan

    This county is within the judicial remit of the affected 13th Circuit Court and 86th District Court. The relationship represents court jurisdiction; reporting does not establish a countywide outage.

    Antrim County contains the affected district court’s Bellaire office. This is a physical anchor for the affected court; branch-specific disruption was not separately documented.

  • Bellaire, Michigan

    Bellaire contains the affected district court’s Antrim office at 205 E. Cayuga St. This is a physical anchor for the affected court; branch-specific disruption was not separately documented.

  • Grand Traverse County, Michigan

    The county government’s territory supplies its county service-area overlay, paired with the county organization. This shared-network incident also affected Traverse City; its separate municipal overlay is paired with the city organization.

    Grand Traverse County physically contains the affected county and city governments’ central offices at 400 Boardman Avenue. This physical county anchor is separate from the county government’s service-area overlay.

  • Leelanau County, Michigan

    Leelanau County contains the affected district court’s government-center office. This is a physical anchor for the affected court; branch-specific disruption was not separately documented.

    This county is within the judicial remit of the affected 13th Circuit Court and 86th District Court. The relationship represents court jurisdiction; reporting does not establish a countywide outage.

  • Suttons Bay Township, Michigan

    Suttons Bay Township contains the affected district court’s Leelanau office at 8527 E. Government Center Drive. This is a physical anchor for the affected court; branch-specific disruption was not separately documented.

  • Traverse City, Michigan

    Traverse City’s municipal territory is the affected city government’s service-area overlay, paired with its organization relationship. The overlay does not imply a uniform outage in every city service or establish Leelanau County government as a victim.

    Traverse City contains both affected governments’ central administrative offices at the Governmental Center, 400 Boardman Avenue. This physical office anchor accompanies the county and municipal service-area overlays.

Sources

Ransomware Strikes Grand Traverse County, Michigan

The report describes ransomware disrupting the shared Grand Traverse County and Traverse City network after June 12 irregularities, with both governments taking networks offline and using administrative workarounds.

Grand Traverse County & City of Traverse City Network Irregularities

Grand Traverse County detected network irregularities at 6:06 a.m. June 12 and took the county and Traverse City office networks offline as a precaution. The city’s notice identified ransomware and described the county’s management of the shared network. The detection time does not establish the original intrusion time.

Archive platform: Internet ArchiveArchived: Historical archive · not yet verifiedView archived copy
Ransomware Attack Brings Unknowns For GT County, City of TC

County officials described ransomware demands, network isolation and workarounds using hotspots. Some court work was canceled or interrupted. Initial findings showed no observed mass data transfer, while separately operated Traverse City Light & Power systems were reported unaffected.

Service Impacts: Network Disruptions

The city’s continually updated page documented interruptions and returns of phone, streaming, mapping and payment functions. Later entries described combining June and July water and sewer charges for about half of customers. The page’s initial June 14 date does not date every subsequent update.

City, County Revisit Services Following Ransomware Attack

Officials described roughly 70% recovery, phone and voicemail problems, precautionary payment suspensions and dispatch workarounds. The county administrator said the attackers used the BlackSuit name but their identity was unknown, and that no ransom had been paid.

Traverse City, MI, 9-1-1 System Hacked

Officials told the June 26 county board meeting that computer-aided dispatch had returned at 2 p.m. the previous day, with bugs remaining. About 80% of county systems were restored, but records and payment applications still needed work. Emergency calls and radio communications had continued during the disruption.

In Wake of Ransomware Attack, City Seeks to Separate IT Services from County

Traverse City considered separating its information technology services from Grand Traverse County after the June ransomware incident. Officials discussed insurer recommendations and ending the shared arrangement. The report describes a governance response, rather than proof of continuing November outages.

Grand Traverse Central Dispatch 911: 2024 annual report in March 2025 meeting packet

Grand Traverse Central Dispatch’s director said ransomware compromised critical support tools during 2024. Staff maintained emergency call-taking and radio communications using backup procedures and improvised arrangements, while normal dispatch technology was unavailable. The report documents impaired support systems rather than a total loss of 911 service.

Grand Traverse County, MI notifies victims of data breach that leaked SSNs

Comparitech reported that Grand Traverse County notified 782 people on Oct. 15, 2025, after personal information was identified in compromised network locations. The report described names and Social Security numbers. It is secondary reporting and does not independently establish a theft volume or public release.

See something that needs correction?

Signed-in members can report an error, update, or missing source.