OCUSOFT INC. — June 2025 breach

Clustered 3 filings across 3 jurisdictions · filing window Jul 31, 2025 → Aug 1, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

3 filings

States

Affected · reported

397

First → last filing

Jul 31, 2025 → Aug 1, 2025

Merge confidence

100%

incident inc_ff719c45355e4e30 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings. Intrusion Jun 9, 2025–Jun 11, 2025, discovered Jun 19, 2025 — the first regulatory filing landed 42 days later. 397 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

42days

Discovered → first regulatory filing

Filing span

1days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

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.