DisclosureLens
State AGConfirmed5 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 5 filings

OCUCO LIMITED — March 2025 breach

Clustered 5 filings across 5 jurisdictions · filing window Jul 11, 2025 Jul 28, 2025. View entity profile → Other incidents for this victim →

1 cross-filing discrepancyMerge100%

Determination

Confirmed

Members

5 filings

States

5

Affected · reported

240,961

First → last filing

Jul 11, 2025 Jul 28, 2025

Merge confidence

100%

incident inc_89585d556eea46a2 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe hacking. Intrusion Mar 28, 2025–Apr 1, 2025, discovered Apr 1, 2025 — the first regulatory filing landed 101 days later (flagged late). 240,961 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 3 more. Notifications rolled out on a 17-day schedule across 5 filings beginning Jul 11, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
101days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
17days

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 clocksWashington WA AG >90dTexas TX AG >30dLeak gap Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 28, 2025breach begins
Apr 1, 2025discovered
notification delay · 101 days
Jul 11, 2025first filing
Jul 28, 2025most 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 11MT AGMT AG noticefirst filing · 66 MT residentsday 0
  2. JUL 11WA AGWA AG notice24,833 WA residentsday 0
  3. JUL 11CA AGCA AG noticeno count statedday 0
  4. JUL 15TX AGTX AG noticestates nationwide total 240,961+4d
  5. JUL 28OR AGOR AG noticemost recent · states nationwide total 9,839+17d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 28, 2025Apr 1, 2025
MT AG
Discovered
Apr 1, 2025· 4d undetected
MT AG + WA AG + CA AG +1
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
MT AG + WA AG + CA AG +1
Attack vector
Misconfiguration
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)

240,961

Sum of filed state slices

64,556· 26.8% of stated

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

US240,961
TX39,657
WA24,833
MT66

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 filing5 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
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

17 days

Cadence

~1 / 4.3d

vs. multi-state median

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