Skip to content

Sheboygan cyberattack disrupts city network and exposes data

Summary

City of Sheboygan logo

An October 2024 cyberattack disrupted Sheboygan’s city network and prompted a ransom demand. Later notices reported 67,947 affected people.

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

Impacted locations

Critical infrastructure sector

Incident characteristics

Assessments

Attack mechanisms

  • Ransomware

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

  • Unauthorized access

    Unauthorized access to systems, accounts, networks, or data.

Data impacts

  • Data theft or exfiltration

    Data was copied, transferred, downloaded, or otherwise removed from the affected environment by an unauthorized party.

  • Data encryption

    Data was rendered inaccessible through unauthorized encryption, including ransomware-related encryption.

Operational impacts

  • Partial service outage

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

  • Network outage

    Internal or external network connectivity was 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.

  • Records processing disruption

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

  • Government services disrupted

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

  • 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.

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.

  • Encryption-based extortion

    The extortion activity involved unauthorized encryption of systems or data, with restoration or decryption conditioned on payment.

  • Leak-site listing

    The victim was listed on a threat actor or ransomware data-leak site as an alleged target or nonpaying victim.

Incident narrative

The City of Sheboygan, Wisconsin, discovered a network issue on Oct. 31, 2024, and isolated its IT network. Its Nov. 7 statement said specialists were assessing the problem and restoring functionality. Telephone lines remained available for people seeking city services.

On Nov. 10, the city confirmed unauthorized external access and a ransom demand. It said the network had been secured and forensic work continued. Containing access did not establish that every service had returned to normal.

The city’s Nov. 22 update acknowledged that unauthorized users had named it in a post and shared a screenshot listing file archives. Officials said no data had been publicly posted and no sensitive-data theft had been identified at that stage. Those findings were provisional.

Library board minutes from Nov. 20 describe effects across most city departments. Library Director Garrett Erickson said staff from several agencies were working from the library. The finance department had little access to municipal financial software, preventing preparation of budget reports. A report expected at the January meeting was a forecast, rather than proof of restoration.

A Dec. 17 update described continuing investigation and council-approved network upgrades. It did not identify an exact restoration date. Nov. 20 is the latest specifically dated operational impact established in the reviewed records. Later investigation and security spending do not establish continuous operational disruption.

The city later acknowledged an encryption event and affected personal information. WBAY’s June 5, 2025, report describes the city’s May 28 notice: the encryption event occurred Oct. 31, officials learned on May 14 that personal information was affected, and notification letters were mailed May 23. May 14 was a later data-review finding, rather than the initial discovery of the network incident.

Indiana’s breach register records 67,947 affected people, including 124 Indiana residents. The total should not be described as city residents. The Record reported stolen information that included Social Security numbers, state IDs and vehicle information. Information affected varied; the reviewed Massachusetts letter does not enumerate individual fields.

The Record identified a claim by Chort. A ransomware.live entry for sheboyganwi.gov was observed by the tracker Nov. 22; that timestamp does not establish the exact criminal posting or intrusion date. The claim remains distinct from confirmed attribution. The reviewed city statements do not establish a ransom amount, payment or initial access method.

The operational incident is presumed resolved because of the time elapsed and absence of a verified current outage. The exact final restoration date remains unknown. Network containment, later data notification and continuing forensic work are separate milestones.

Threat actor and claim

Listed as: sheboyganwi.govSource: ransomware.liveDiscovered:

Claim details

A ransomware.live entry attributes a listing for sheboyganwi.gov to Chort. Domain and short-name queries return the same lead; canonical City of Sheboygan query returned none. The tracker records discovery Nov.22,2024, not an exact attacker posting or intrusion date. Its description alleges database/files and a decision pending; this is not independent proof of volume or contents. Original city Nov.22 statement acknowledges an unnamed unauthorized-party post and screenshot listing file archives while reporting no public data at that stage. The Record later named Chort and reported personal-data theft; the city has not independently identified the operator in reviewed statements. Preserve allegation separately from high-confidence encryption/ransom findings, and preserve the already researched shared actor profile. No verified ransom payment or 200GB quantity adopted.

Organizations involved

Impacted location

  • Sheboygan, Wisconsin

    The City of Sheboygan municipality is the affected government’s service remit. Official council/department pages identify municipal functions. County public GIS exact City feature42/FIPS72975/full5511772975 establishes the municipality, distinct from the Town of Sheboygan and the county; current polygon submitted to Ops9556f6b8, not yet approved. This overlay connects the victim to its remit without asserting every resident, service or facility lost service. Do not infer county government, school district, public-library system or physical utility delivery interruption.

    Official current city pages and original Nov.7/10 letters identify CityHall828CenterAvenue,SheboyganWI53081. Official city Facebook publicprofile pin[-87.714097142139,43.751330708022] lies inside the exact county GIS City polygon; this is a publicprofile pin, not a surveyed geocode. Medium confidence in the administrative site anchor; no claim of a CityHall-specific outage or intrusion origin. Preserve existing municipality target; no new facility location.

Sources

See something that needs correction?

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