DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed7 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 7 filings

TIO Networks USA, Inc. — January 2014 breach

Clustered 7 filings across 6 jurisdictions · filing window Dec 12, 2017 → Feb 2, 2018. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 filings

States

6

Affected · reported

1,600,000

First → last filing

Dec 12, 2017 → Feb 2, 2018

Merge confidence

100%

incident inc_80d5efdf7d254f95 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings. The filings describe unauthorized access. Intrusion Jan 1, 2014–Nov 10, 2017, discovered Nov 10, 2017 — the first regulatory filing landed 32 days later; 1 later filing was flagged late. 1,600,000 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 3 more. Notifications rolled out on a 52-day schedule across 7 filings beginning Dec 12, 2017. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
32days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
52days

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.

Regulatory clocksOregon✗ OR AG >45dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

authenticationfinancial_credentialsidentity_government

Incident timeline

Jan 1, 2014breach begins
Nov 10, 2017discovered
notification delay · 32 days
Dec 12, 2017first filing
Feb 2, 2018most 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. DEC 12MT AGMT AG noticefirst filing · 50 MT residentsday 0
  2. DEC 22CA AGCA AG noticestates nationwide total 1,600,000+10d
  3. DEC 22WA AGWA AG noticestates nationwide total 1,600,000+10d
  4. DEC 22NH AGNH AG noticestates nationwide total 1,600,000+10d
  5. DEC 28SC AGSC AG noticestates nationwide total 1,600,000+16d
  6. DEC 29OR AGOR AG noticestates nationwide total 1,600,000+17d
  7. FEB 2NH AGNH AG noticemost recent · 146 NH residents+52d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 1, 2014
MT AG
Discovered
Nov 10, 2017· 1409d undetected
MT AG + CA AG + WA AG +3
Data types
Authentication · Credentials · Financial account · Financial credentials · Identity (basic) · Government ID
MT AG + CA AG + WA AG +2
Attack vector
Unauthorized Access
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)

1,600,000

Sum of filed state slices

99,545· 6.2% of stated

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

US1,600,000
SC97,343
WA1,962
NH190
MT50

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 filing7 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

52 days

Cadence

~1 / 8.7d

vs. multi-state median

8.7× 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.