DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed12 records · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedransomhubhigh sensitivity
Merged incident · 12 records

Tekni-Plex, Inc. — October 2024 breach

Clustered 12 records across 10 jurisdictions: 10 filings and 2 leak-site claims · filing window Sep 24, 2025 → Sep 26, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 records

States

10

Affected · reported

11,485

First → last dated filing

Sep 24, 2025 → Sep 26, 2025

Merge confidence

100%

incident inc_29d07bc1f5ab4320 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 2 unverified claims. Intrusion Oct 25, 2024–Dec 7, 2024, discovered Nov 18, 2024. 11,485 individuals reported across the linked filings. Data reported: Government ID, Financial account, Health (basic), and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
295days

Range of discovered_at dates across filings

Filing span
2days

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 >180dVermont✗ VT AG >45 bdayWashington✗ WA AG >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 25, 2024breach begins
Nov 18, 2024discovered · members disagree
Sep 24, 2025first dated filing
Sep 26, 2025most 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. DEC 7Leak siteransomhub postfirst record · attacker claim · unverifiedday 0
  2. DEC 7Leak siteransomhub postattacker claim · unverifiedday 0
  3. SEP 1IL AGIL AG noticefiling day not on record · no count stated—
  4. SEP 24NH AGNH AG notice80 NH residents+291d
  5. SEP 24IN AGIN AG noticestates nationwide total 11,485+291d
  6. SEP 24NE AGNE AG noticefiling day not on record · 8 NE residents—
  7. SEP 24VT AGVT AG noticeno count stated+291d
  8. SEP 24WA AGWA AG notice525 WA residents+291d
  9. SEP 24MA AGMA AG notice57 MA residents+291d
  10. SEP 24MT AGMT AG notice6 MT residents+291d
  11. SEP 24ME AGME AG notice1 ME residents+291d
  12. SEP 26TX AGTX AG noticemost recent · states nationwide total 11,485+293d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 25, 2024 – Dec 7, 2024
NH AG
Discovered
Nov 18, 2024NH AG + NE AG + VT AG +3Sep 9, 2025IL AG + TX AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
IL AG + WA AG + MA AG +6
Attack vector
Unauthorized Access
NH 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)

11,485

Sum of filed state slices

2,604· 22.7% of stated

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

US11,485
TX970
IN957
WA525
NH80
MA57
NE8
MT6
ME1

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

2 days

Cadence

~1 / 0.3d

vs. multi-state median

3.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.