Clustered 4 filings across 4 jurisdictions · filing window Apr 11, 2025 → May 15, 2025. View entity profile → Other incidents for this victim →
incident inc_c5399e441c9244e0 · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
PII
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
IN ME OR VT
all State AG
per-filing reported counts
State AGs report only their own residents; bars show per-filing counts.
Earliest sighting first · deep chronology in Litigation Timeline
Apr 11, 2024 → Apr 12, 2024
When the intrusion reportedly occurred, per the linked filings
Apr 21, 2024
Reported by VERMONT AG, MAINE AG filings
Dec 24, 2024
Reported by OREGON AG filing
Thede Culpepper Moore Munro & Silliman LLP notified consumers of a data breach discovered on April 21, 2024. Unauthorized access resulted in the copying of files containing names and other personal information. The firm engaged a cybersecurity firm, contained the incident, and offered one year of Experian IdentityWorks credit monitoring to affected individuals.
Portland, OR law firm Thede Culpepper experienced an external network breach April 11-12, 2024. Unusual activity was detected April 21, 2024, but file exfiltration was not confirmed until December 24, 2024. Names and additional personal identifiers were acquired. 437 total individuals affected; 1 Maine resident. Notifications sent April 11, 2025. Experian IdentityWorks Credit 3B (12 months) offered.
Affected (this filing): 1
Thede Culpepper Moore Munroe & Silliman LLP reported a data breach to the Indiana Attorney General. The breach occurred on 2025-04-11 and was reported on 2025-05-15. 1 Indiana residents were affected. 1,259 individuals affected in total.
Affected (this filing): 1,259
Thede Culpepper Moore Munroe & Silliman LLP reported a data breach to the Oregon Attorney General. The breach was reported on 2025-05-15. The breach occurred during 4/11/2024 - 4/12/2024. The breach was discovered on 12/24/2024. 1,259 individuals were affected. Notice was sent on 4/11/20245/15/2024.
Affected (this filing): 1,259
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.