
Municipal ransomware incident
What happened: Columbia City Manager Teresa Wilson said the City of Columbia, South Carolina, was hit by ransomware that took several online services offline. The city is working with the South Carolina Law Enforcement Division to contain the incident, identify affected systems and determine whether information may have been compromised.[1]
Reporting cutoff: October 24, 2026 at 12:18 AM EDT (04:18 UTC). WIS’s live report and the City of Columbia’s October 21 public notice were rechecked for this article.
What was working and what was not
| Status | Services named in the latest report | Reader takeaway |
|---|---|---|
| Operational | Police, fire, 911 communications, Columbia Water, utility services and broad online payment services. | The report did not describe a citywide public-safety, water or utility outage.[1] |
| Unavailable | MyColaSC, GIS, parks-and-recreation reservations and payment services related to Animal Services. | Affected departments established alternate processes, but no restoration timeline was available.[1] |
How the public account changed
The city’s October 21 notice said its technology department identified suspicious network activity, notified SLED and took steps while selected applications were affected. It did not identify ransomware at that time.[2]
WIS reported on October 23 that Wilson confirmed ransomware in a city video. The later statement is a material update, not evidence that a separate attack occurred.[1]
What remains unknown
No reviewed source identified the initial-access method, ransomware family, attacker, ransom demand, payment decision or whether data was accessed or acquired. The city said it would provide updates as more information is confirmed.[1][2]
Practical guidance for residents and businesses
Editorial guidance, not a city directive
- Use the city’s published website and established phone channels for service updates; verify any alternate payment or account request independently.
- Treat unsolicited messages claiming to restore access, collect a payment or verify an account as untrusted until the city confirms the channel.
- Keep receipts and reference numbers for requests submitted through temporary processes so they can be reconciled after systems return.
- If the city later issues a data-impact notice, follow the instructions for the specifically affected people and information rather than assuming every resident was exposed.
A continuity lesson for small organizations
Practical guidance: Small businesses and local agencies should pre-approve offline contact trees, manual intake procedures, payment-change verification and restoration priorities. Alternate workflows should preserve identity checks, privacy and recordkeeping rather than bypass them during an outage.
Read the City of Columbia notice
