HackingGovernmentGovernmentVulnerability ExploitStolen CredentialsData ExfiltratedTargetedIdentity (basic)Government IDHighContained

City of Noblesville

bd_c18290be0be07d3b · schema v1 · pii pii-v1

Severity

High

Discovered

Nov 22, 2024

Filed

Feb 18, 2025

To disclose

27 days

Affected · nationwide

1,8411 in this filing

Linked

4 records

Confidence

65%

Full breach record for City of Noblesville →

City of Noblesville (IN) reported an external system breach (hacking) occurring between Oct 22 and Nov 21, 2024. Discovered Jan 22, 2025. 1,841 individuals affected, including 1 Maine resident. Data involved names and government identifiers (SSN). Notification sent Feb 18, 2025. Identity theft protection services offered.

J jump to incidentP pin to compareR raw source

Maine clockDiscovered Nov 22, 2024 → Filed with AG Feb 18, 202588d ⏱ ME AG >30d27 days discovery → filing

⚠ AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.

Incident timeline

undetected · 31 days

discovery → filing · 13 weeks / 88 days

Oct 22, 2024

Begins

Nov 22, 2024

Discovered

Feb 18, 2025

Filed

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

A leak claim by interlock about this victim was first seen 60 days before this filing.View originating leak claim

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Siteinterlockbd_f180a0d10a9dd1d72024-12-20 · +60dVerified

Regulatory filings (1) · sorted by filing gap

Indiana State AGbd_1b651f2b39b1d42d2025-01-07 · +42dVerified by operator

Press reports (1)

Pressinterlockbd_46e2e0cb75587b2d2024-11-26 · +84dCandidate

Name: City of Noblesville
norm: city of noblesville
Domain: noblesville.in.gov

Name: City of Noblesville
norm: city of noblesville
Domain: noblesville.in.gov
Industry: Governmentllm

Discovered: Nov 22, 2024
Breach occurred: Oct 22, 2024 – Nov 21, 2024
Undetected for: 31 daysoccurrence → discovery
Materiality determined: —
Notification sent: Feb 18, 2025
Affected individuals: 1,841state + nationwide
Data types: Identity (basic)Government ID
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1078 Valid AccountsT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Regulator citations: Filed notification with Maine Attorney General
Initial access: exploit_public_facing

During the incident: Contained the threat by disabling all unauthorized access to our network
Restored all data
Notified law enforcement
Engaged external cybersecurity professionals for forensics investigation
Conducted internal document review of impacted files
Changes made: Offered 12 months of identity theft protection services through IDX
Continually evaluate and modify practices and internal controls to enhance security and privacy
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 27 days(27 days from discovery to filing)
Compliance flags: ME AG >30d · 88dLeak >30d
Discovery-date grounding: AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.
Clock breakdown: Statute Window Elapsed Threshold Status
Maine
Discovered: Nov 22, 2024
→ Filed with AG: Feb 18, 2025
88d 30 days (soft) ME AG >30d

Statute	Window	Elapsed	Threshold	Status
Maine	Discovered: Nov 22, 2024 → Filed with AG: Feb 18, 2025	88d	30 days (soft)	ME AG >30d

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 2 filings · 2 states

View merged incident ↗

Indiana State AGJan 7 · first

Maine State AG+42d · this page

Pattern: first filing Jan 7 (IN), last Feb 18 (ME) — a 42-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://www.maine.gov/agviewer/content/ag/985235c7-cb95-4be2-8792-a1252b4f8318/7b368af8-b730-4730-9abd-13e2a105b897.html
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Feb 18, 2025
Raw hash: 8b0e157c87c294e0b8ee517d408a18c8a4eb318581dd466a6b80e9d1b7a72518

Linked disclosures

Ransomware claims (1)

Regulatory filings (1) · sorted by filing gap

Press reports (1)

Reporting entityCity of Noblesville

Victim entityCity of Noblesville

Incidentdiscovered Nov 22, 2024

Stated responseContained the threat by disabling all unauthorized access to our network

ComplianceME AG >30d

Extraction provenanceno artifact recorded

Source provenancewww.maine.gov