DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
HHS OCRState AGConfirmed13 filings · 12 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 13 filings

Unlimited Technology — October 2025 breach

Clustered 13 filings across 12 jurisdictions · filing window Jul 1, 2026 → Jul 23, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

13 filings

States

12

Affected · reported

3,836,316

First → last filing

Jul 1, 2026 → Jul 23, 2026

Merge confidence

100%

incident inc_3d9b748ac4214aef · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 13 regulatory filings. Intrusion Oct 2, 2025–Oct 10, 2025, discovered Oct 19, 2025 — the first regulatory filing landed 255 days later (flagged late). 3,836,316 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 3 more. Notifications rolled out on a 22-day schedule across 13 filings beginning Jul 1, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
255days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
22days

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 clocksWashington✗ WA AG >90dOregon✗ OR AG >45dMassachusetts✗ MA AG >90dTexas✗ TX AG >30dHIPAA✓ HHS notifiedSouth Carolina✓ SC CRA notice dueIowa✓ IA AG ≤5 bdayFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 2, 2025breach begins
Oct 19, 2025discovered
notification delay · 255 days
Jul 1, 2026first filing
Jul 23, 2026most 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. JUL 1IA AGIA AG noticefirst filing · no count statedday 0
  2. JUL 1IL AGIL AG noticeno count statedday 0
  3. JUL 21HHS OCRHHS OCR noticestates nationwide total 3,803,750+20d
  4. JUL 21WA AGWA AG notice724 WA residents+20d
  5. JUL 21DE AGDE AG noticeno count stated+20d
  6. JUL 21NH AGNH AG notice35,485 NH residents+20d
  7. JUL 21CA AGCA AG noticeno count stated+20d
  8. JUL 21OR AGOR AG noticestates nationwide total 3,836,316+20d
  9. JUL 21VT AGVT AG notice286 VT residents+20d
  10. JUL 21SC AGSC AG notice148,342 SC residents+20d
  11. JUL 21IA AGIA AG notice162,478 IA residents+20d
  12. JUL 22MA AGMA AG notice2,223 MA residents+21d
  13. JUL 23TX AGTX AG noticemost recent · states nationwide total 3,836,316+22d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 5, 2025 – Oct 10, 2025
IA AG
Discovered
Oct 19, 2025· 14d undetected
IA AG + IL AG + WA AG +7
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
IA AG + HHS OCR + WA AG +8
Attack vector
Unauthorized Access
IA 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)

3,836,316

Sum of filed state slices

626,902· 16.3% of stated

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

US3,836,316
TX277,364
IA162,478
SC148,342
NH35,485
MA2,223
WA724
VT286

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

22 days

Cadence

~1 / 1.8d

vs. multi-state median

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