DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed9 records · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedvicesocietyhigh sensitivity
Merged incident · 9 records

NuLife Med, LLC — March 2022 breach

Clustered 9 records across 6 jurisdictions: 8 filings and 1 leak-site claim · filing window May 9, 2022 → Dec 23, 2022 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 records

States

6

Affected · reported

92,436

First → last dated filing

May 9, 2022 → Dec 23, 2022

Merge confidence

100%

incident inc_f42ca37f812d4d21 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Mar 9, 2022–Mar 11, 2022, discovered Mar 11, 2022. 92,436 individuals reported across the linked filings. Data reported: Government ID, PII, PHI, and 4 more. Notifications rolled out on a 228-day schedule across 7 dated filings beginning May 9, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
33days

Range of discovered_at dates across filings

Filing span
228days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap✗ Leak >180dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Mar 9, 2022breach begins
Mar 11, 2022discovered · members disagree
May 9, 2022first dated filing
Dec 23, 2022most 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 and leak-site claim in this incident

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. APR 17Leak sitevicesociety postfirst record · attacker claim · unverifiedday 0
  3. MAY 9MT AGMT AG notice22 MT residents+22d
  4. MAY 9HHS OCRHHS OCR noticestates nationwide total 92,436+22d
  5. JUL 25HHS OCRHHS OCR noticestates nationwide total 3,805+99d
  6. DEC 19MA AGMA AG notice1,268 MA residents+246d
  7. DEC 19IN AGIN AG noticestates nationwide total 29,453+246d
  8. DEC 19ME AGME AG noticestates nationwide total 29,453+246d
  9. DEC 23NH AGNH AG noticemost recent · 339 NH residents+250d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 9, 2022 – Mar 11, 2022
MT AG
Discovered
Mar 11, 2022IL AG + MT AG + NH AGApr 13, 2022ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PHI · PII
MT AG + HHS OCR + NH AG +2
Attack vector
Unauthorized Access
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)

92,436

Sum of filed state slices

1,666· 1.8% of stated

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

US92,436
MA1,268
NH339
ME25
MT22
IN12

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 claim1 member

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

Press / market report

No press coverage linked yet.

State AG / regulator filing8 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
Reviewed
operator-reviewed Aug 23, 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

228 days

Cadence

~1 / 38d

vs. multi-state median

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