MalwareGovernmentGovernmentRansomwareRansom DemandedData ExfiltratedData PublishedTargetedIdentity (basic)Government IDFinancial accountMediumActive

City Of Columbus

bd_83d2c65f69b841b5 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Jul 18, 2024

Filed

Oct 18, 2024

To disclose

13 weeks

Affected

106state residents only

Linked

2 filings

Confidence

66%

Full breach record for City Of Columbus →

The City of Columbus, Ohio, disclosed a cybersecurity incident discovered on July 18, 2024, where a foreign threat actor attempted to deploy ransomware and solicit payment. The actor gained unauthorized access to IT infrastructure, exposing personal information including names, DOBs, SSNs, driver's licenses, and bank account details. Data was posted on the dark web. The City engaged cybersecurity experts and law enforcement. The investigation is ongoing. No specific affected individual count was provided.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 13 weeks / 92 days

Jul 18, 2024

Discovered

Oct 18, 2024

Filed

vs. sector median

+2 wks slower

This filing is one of 2 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (1) · sorted by filing gap

New Hampshire State AGbd_c3229be5e89157e62024-11-01 · +14dVerified

Name: City of Columbus, Ohio
norm: city of columbus ohio
Domain: columbus.gov

Name: City Of Columbus
norm: city of columbus
Domain: cityofcolumbus.org
Industry: Governmentllm

Discovered: Jul 18, 2024
Materiality determined: —
Notification sent: Oct 7, 2024
Affected individuals: 106state-resident count only
Data types: Identity (basic)Government IDFinancial account
Data elements: Social Security numberDate of birth
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1190 Exploit Public-Facing Application
Threat actor: ExternalFinancial
Regulator citations: working with law enforcement
Initial access: exploit_public_facing

During the incident: Department of Technology quickly identified the threat and took action to block unauthorized users from accessing the City's systems
Launched an investigation
Engaged cyber security experts to investigate and resolve the Incident
Working with law enforcement to bring those behind this Incident to justice
Working with cyber security experts to implement measures to prevent unauthorized access to the City's IT systems in the future
Changes made: Implement measures to prevent unauthorized access to the City's IT systems in the future
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 13 weeks(92 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 2 filings · 2 states

View merged incident ↗

South Carolina State AGOct 18 · first · this page

New Hampshire State AG+14d

Pattern: first filing Oct 18 (SC), last Nov 1 (NH) — a 14-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://consumer.sc.gov/sites/consumer/files/Documents/Security%20Breach%20Notices/TheCityofColumbus.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Oct 18, 2024
Raw hash: 1c66ea0c1bf8a7a532bf0747189519ff776c785510acf1cacbd0c9b92d713694

Linked disclosures

Regulatory filings (1) · sorted by filing gap

Reporting entityCity of Columbus, Ohio

Victim entityCity Of Columbus

Incidentdiscovered Jul 18, 2024

Stated responseDepartment of Technology quickly identified the threat and took action to block unauthorized users from accessing the City's systems

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceconsumer.sc.gov