DisclosureLens
State AGConfirmed9 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 9 filings

Timios Inc. — July 2021 breach

Clustered 9 filings across 8 jurisdictions · filing window Jan 1, 2021 Oct 11, 2021. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

9 filings

States

8

Affected · reported

74,755

First → last filing

Jan 1, 2021 Oct 11, 2021

Merge confidence

100%

incident inc_5daad10837124248 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. Intrusion Jul 19, 2021–Jul 31, 2025, discovered Jul 19, 2021. 74,755 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 283-day schedule across 9 filings beginning Jan 1, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
11days

Range of discovered_at dates across filings

Filing span
283days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delayno leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksMaine ME AG >30d · 73dCalifornia CA 60-day OK · 50dMassachusetts MA credit monitoring dueSouth Carolina SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Jul 19, 2021breach begins
Jul 19, 2021discovered · members disagree
Jan 1, 2021first filing
Oct 11, 2021most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. SEP 18MT AGMT AG notice152 MT residents+260d
  3. OCT 11MT AGMT AG notice285 MT residents+283d
  4. OCT 11CA AGCA AG noticeno count stated+283d
  5. OCT 11IN AGIN AG noticestates nationwide total 74,755+283d
  6. OCT 11NH AGNH AG notice218 NH residents+283d
  7. OCT 11ME AGME AG noticestates nationwide total 74,755+283d
  8. OCT 11MA AGMA AG notice572 MA residents+283d
  9. OCT 11SC AGSC AG noticemost recent · 1,167 SC residents+283d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 1, 2025Jul 31, 2025
MT AG
Discovered
Jul 19, 2021IL AG + CA AGJul 30, 2021MT AG + NH AG + ME AG +1filings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · Government ID · PCI
MT AG + CA AG + NH AG +3
Attack vector
Ransomware
MT AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

74,755

Sum of filed state slices

4,469· 6.0% of stated

94% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US74,755
IN2,112
SC1,167
MA572
MT285
NH218
ME115

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing9 members

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

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

283 days

Cadence

~1 / 35.4d

vs. multi-state median

35.4× slower

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.