DisclosureLens
UnknownGovernmentGovernmentGovernment IDMedium

City of Coppell

bd_9d996aab498ce9f1 · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Jul 2, 2025

To disclose

—

Affected

1state residents only

Linked

4 filings

Confidence

95%
Full breach record for City of Coppell →

City of Coppell reported a data breach to the Massachusetts Office of Consumer Affairs and Business Regulation. The breach was reported on 2025-07-02. 1 Massachusetts residents were affected.

Leak gap clock✗ Leak >180d
⚠ no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.

Incident timeline — partial

? — ?

Breach window unknown

Jul 2, 2025

Filed

—

Corroborated · see linked filings

Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.

This filing is one of 4 about the same incident.View merged incident
A leak claim by ransomhub about this victim predates this filing by 252 days.View originating leak claim

Linked disclosures

Why this link?

Ransomware claims (1)

Regulatory filings (2) · sorted by filing gap

Filing propagation · 3 filings · 3 states

View merged incident ↗
Indiana State AGJun 19 · first
Massachusetts State AG+13d · this page
Texas State AG+14d

Pattern: first filing Jun 19 (IN), last Jul 3 (TX) — 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.