DisclosureLens
State AGConfirmed8 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 8 filings

Metabolic Maintenance Products, Inc. — October 2019 breach

Clustered 8 filings across 8 jurisdictions · filing window Dec 22, 2020 Dec 23, 2020. View entity profile → Other incidents for this victim →

1 cross-filing discrepancyMerge100%

Determination

Confirmed

Members

8 filings

States

8

Affected · reported

34,325

First → last filing

Dec 22, 2020 Dec 23, 2020

Merge confidence

100%

incident inc_f1fb00ccdec24b5e · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. The filings describe hacking. Intrusion Oct 1, 2019–Aug 20, 2020, discovered Sep 29, 2020 — the first regulatory filing landed 84 days later (flagged late). 34,325 individuals reported across the linked filings. Data reported: PII, PCI, Identity (basic), and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
84days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
1days

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 >45dMaine ME AG >30d · 85dWashington WA AG >30dFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Oct 1, 2019breach begins
Sep 29, 2020discovered
notification delay · 84 days
Dec 22, 2020first filing
Dec 23, 2020most 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. DEC 22MT AGMT AG noticefirst filing · 88 MT residentsday 0
  2. DEC 22IN AGIN AG noticestates nationwide total 34,325day 0
  3. DEC 23OR AGOR AG noticestates nationwide total 17,927+1d
  4. DEC 23ME AGME AG noticestates nationwide total 17,927+1d
  5. DEC 23WA AGWA AG notice709 WA residents+1d
  6. DEC 23MA AGMA AG notice260 MA residents+1d
  7. DEC 23NH AGNH AG notice56 NH residents+1d
  8. DEC 23CA AGCA AG noticemost recent · no count stated+1d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 1, 2019
IN AG
Discovered
Sep 29, 2020· 364d undetected
MT AG + OR AG + ME AG +3
Data types
Financial account · Financial credentials · Identity (basic) · PCI · PII
MT AG + WA AG + 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)

34,325

Sum of filed state slices

1,858· 5.4% of stated

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

US34,325
IN718
WA709
MA260
MT88
NH56
ME27

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

1 days

Cadence

~1 / 0.1d

vs. multi-state median

8.0× faster

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.