DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
HHS OCRState AGConfirmed11 filings · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 11 filings

Altos Inc — May 2025 breach

Clustered 11 filings across 4 jurisdictions · filing window Aug 1, 2025 → Aug 11, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

11 filings

States

4

Affected · reported

15,956

First → last dated filing

Aug 1, 2025 → Aug 11, 2025

Merge confidence

100%

incident inc_020ab5ba87034531 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. Intrusion May 30, 2025–May 31, 2025, discovered Jun 17, 2025 — the first regulatory filing landed 45 days later. 15,956 individuals reported across the linked filings. Data reported: Government ID, PHI, Identity (basic), and 1 more. Notifications rolled out on a 10-day schedule across 10 dated filings beginning Aug 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
45days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
10days

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 clocksMassachusetts✓ MA credit monitoring dueHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 30, 2025breach begins
Jun 17, 2025discovered
notification delay · 45 days
Aug 1, 2025first dated filing
Aug 11, 2025most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. AUG 1IN AGIN AG noticefirst filing · states nationwide total 15,956day 0
  2. AUG 1CA AGCA AG noticeno count statedday 0
  3. AUG 1NE AGNE AG noticefiling day not on record · no count stated—
  4. AUG 1MA AGMA AG notice9 MA residentsday 0
  5. AUG 11HHS OCRHHS OCR noticestates nationwide total 2,700+10d
  6. AUG 11HHS OCRHHS OCR noticestates nationwide total 1,634+10d
  7. AUG 11HHS OCRHHS OCR noticestates nationwide total 882+10d
  8. AUG 11HHS OCRHHS OCR noticestates nationwide total 1,011+10d
  9. AUG 11HHS OCRHHS OCR noticestates nationwide total 6,414+10d
  10. AUG 11HHS OCRHHS OCR noticestates nationwide total 1,520+10d
  11. AUG 11HHS OCRHHS OCR noticemost recent · states nationwide total 2,366+10d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 30, 2025
IN AG
Discovered
Jun 17, 2025· 18d undetected
CA AG + NE AG
Data types
Identity (basic) · Government ID · Health (basic) · PHI
CA AG + HHS OCR + NE AG +1
Attack vector
Misconfiguration
CA 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)

15,956

Sum of filed state slices

16· 0.1% of stated

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

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

10 days

Cadence

~1 / 1.1d

vs. multi-state median

1.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.