DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteHHS OCRState AGConfirmed11 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmedusahigh sensitivity
Merged incident · 11 filings

Signature Performance — January 2024 breach

Clustered 11 filings across 8 jurisdictions · filing window Jan 24, 2024 → Jun 12, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

7

Affected · reported

130,228

First → last filing

Jan 24, 2024 → Jun 12, 2024

Merge confidence

100%

incident inc_8929a8172f824481 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Jan 17, 2024–Jan 18, 2024, discovered Jan 18, 2024 — the first regulatory filing landed 22 days later. 130,228 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 3 more. Notifications rolled out on a 139-day schedule across 9 filings beginning Jan 24, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
22days

Discovered → first regulatory filing

Discovery variance
140days

Range of discovered_at dates across filings

Leak precedence
15days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
139days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksVermont⏱ VT AG >14 bdayLeak gap⏱ Leak >90dMaine✓ ME AG ≤30d · 22dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 17, 2024breach begins
Jan 18, 2024discovered · members disagree
notification delay · 22 days
Feb 9, 2024first filing
Jun 12, 2024most 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. JAN 24Leak sitemedusa postfirst filing · attacker claim · unverifiedday 0
  2. FEB 9VT AGVT AG noticeno count stated+16d
  3. FEB 9ME AGME AG noticestates nationwide total 7,122+16d
  4. FEB 9IN AGIN AG noticestates nationwide total 7,122+16d
  5. FEB 10MA AGMA AG notice9 MA residents+17d
  6. FEB 12NH AGNH AG notice6 NH residents+19d
  7. FEB 12MT AGMT AG notice41 MT residents+19d
  8. FEB 26Leak sitedispossessor postattacker claim · unverified+33d
  9. JUN 10HHS OCRHHS OCR noticestates nationwide total 130,228+138d
  10. JUN 10VT AGVT AG noticeno count stated+138d
  11. JUN 12MA AGMA AG noticemost recent · 33 MA residents+140d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 17, 2024 – Jan 18, 2024
VT AG
Discovered
Jan 18, 2024VT AG + ME AG + NH AG +1Jun 6, 2024VT AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
VT AG + NH AG + MT AG +3
Attack vector
Unauthorized Access
VT 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)

130,228

Sum of filed state slices

94· 0.1% of stated

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

US130,228
MT41
MA33
ME7
IN7
NH6

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 claim2 members

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing9 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 Aug 22, 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

139 days

Cadence

~1 / 13.9d

vs. multi-state median

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