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

THE RESHAPOING AND NUTRITIONAL COMPANY LLC / — December 2024 breach

Clustered 5 filings across 5 jurisdictions · filing window Jan 12, 2025 Mar 13, 2025. View entity profile → Other incidents for this victim →

1 cross-filing discrepancyMerge100%

Determination

Confirmed

Members

5 filings

States

5

Affected · reported

307,000

First → last filing

Jan 12, 2025 Mar 13, 2025

Merge confidence

100%

incident inc_b05562f838ff46c7 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe malware. Intrusion Dec 7, 2024–Feb 9, 2025, discovered Dec 7, 2024 — the first regulatory filing landed 35 days later (flagged late). 307,000 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 60-day schedule across 5 filings beginning Jan 12, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
35days

Discovered → first regulatory filing

Discovery variance
2days

Range of discovered_at dates across filings

Filing span
60days

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 clocksOregon OR AG >45dMaryland MD AG >90dWashington WA AG >30dCalifornia CA 60-day OK · 34dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 7, 2024breach begins
Dec 7, 2024discovered · members disagree
notification delay · 35 days
Jan 12, 2025first filing
Mar 13, 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. JAN 12IN AGIN AG noticefirst filing · states nationwide total 307,000day 0
  2. JAN 30CA AGCA AG noticeno count stated+18d
  3. FEB 17WA AGWA AG notice3,080 WA residents+36d
  4. FEB 24OR AGOR AG noticestates nationwide total 305,000+43d
  5. MAR 13MD AGMD AG noticemost recent · states nationwide total 307,000+60d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 7, 2024
IN AG
Discovered
Dec 7, 2024MD AGDec 9, 2024CA AG + WA AGDec 10, 2024OR AGfilings disagree on discovery
Data types
Identity (basic) · Government ID
CA AG + WA AG + MD AG
Attack vector
Third-Party / Supply Chain
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)

307,000

Sum of filed state slices

20,075· 6.5% of stated

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

US307,000
MD14,478
WA3,080
IN2,517

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

60 days

Cadence

~1 / 15d

vs. multi-state median

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