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

Norwex USA, Inc. — December 2024 breach

Clustered 11 filings across 11 jurisdictions · filing window Dec 1, 2024 → Jan 3, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

14,110

First → last filing

Dec 1, 2024 → Jan 3, 2025

Merge confidence

100%

incident inc_a505c2663f1c4ccb · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Dec 11, 2024, discovered Dec 11, 2024. 14,110 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Employment, and 1 more. Notifications rolled out on a 33-day schedule across 11 filings beginning Dec 1, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
4days

Range of discovered_at dates across filings

Filing span
33days

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 clocksSouth Carolina✓ SC CRA notice dueOregon✓ OR AG ≤45dVermont✓ VT AG ≤14 bdayCalifornia✓ CA 60-day OK · 8dMassachusetts✓ MA credit monitoring dueMaine✓ ME AG ≤30d · 8dRhode Island✓ RI AG ≤45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 11, 2024breach begins
Dec 11, 2024discovered · members disagree
Dec 1, 2024first filing
Jan 3, 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. DEC 1IL AGIL AG noticefirst filing · no count statedday 0
  2. DEC 23SC AGSC AG notice3,453 SC residents+22d
  3. DEC 23MT AGMT AG noticeno count stated+22d
  4. DEC 23DE AGDE AG noticeno count stated+22d
  5. DEC 23OR AGOR AG noticeno count stated+22d
  6. DEC 23VT AGVT AG noticeno count stated+22d
  7. DEC 23IN AGIN AG notice10,656 IN residents+22d
  8. DEC 23CA AGCA AG noticeno count stated+22d
  9. DEC 23MA AGMA AG notice1 MA residents+22d
  10. DEC 23ME AGME AG notice1 ME residents+22d
  11. JAN 3RI AGRI AG noticemost recent · no count stated+33d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 11, 2024
SC AG
Discovered
Dec 11, 2024IL AGDec 15, 2024SC AG + MT AG + DE AG +5filings disagree on discovery
Data types
Employment · Financial account · Identity (basic) · Government ID
SC AG + MT AG + DE AG +5
Attack vector
Unauthorized Access
SC AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Affected residents by state

per-state reported counts

IN10,656
SC3,453
MA1
ME1

State AGs report only their own residents; teal bars show each state's reported slice.

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

33 days

Cadence

~1 / 3.3d

vs. multi-state median

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