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

Avery Products Corporation — July 2024 breach

Clustered 14 filings across 11 jurisdictions · filing window Jan 10, 2025 → Feb 11, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

14 filings

States

11

Affected · reported

67,000

First → last filing

Jan 10, 2025 → Feb 11, 2025

Merge confidence

100%

incident inc_78bff20073b54882 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 14 regulatory filings. The filings describe malware. Intrusion Jul 18, 2024–Jan 5, 2025, discovered Dec 9, 2024 — the first regulatory filing landed 32 days later. 67,000 individuals reported across the linked filings. Data reported: Authentication, Financial account, Financial credentials, and 3 more. Notifications rolled out on a 32-day schedule across 14 filings beginning Jan 10, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
32days

Discovered → first regulatory filing

Discovery variance
26days

Range of discovered_at dates across filings

Filing span
32days

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 clocksWashington⏱ WA AG >30dMaine⏱ ME AG >30d · 35dVermont⏱ VT AG >14 bdayOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Sensitive data

authenticationfinancial_credentials

Incident timeline

Jul 18, 2024breach begins
Dec 9, 2024discovered · members disagree
notification delay · 32 days
Jan 10, 2025first filing
Feb 11, 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 10WA AGWA AG noticefirst filing · 1,724 WA residentsday 0
  2. JAN 13NH AGNH AG notice372 NH residents+3d
  3. JAN 13MA AGMA AG notice1,791 MA residents+3d
  4. JAN 13ME AGME AG noticestates nationwide total 61,193+3d
  5. JAN 15NE AGNE AG noticeno count stated+5d
  6. JAN 15DE AGDE AG noticestates nationwide total 61,193+5d
  7. JAN 16OR AGOR AG noticestates nationwide total 61,100+6d
  8. JAN 16IN AGIN AG noticestates nationwide total 61,192+6d
  9. JAN 16CA AGCA AG noticeno count stated+6d
  10. JAN 29VT AGVT AG noticeno count stated+19d
  11. FEB 5NH AGNH AG notice400 NH residents+26d
  12. FEB 6ME AGME AG noticestates nationwide total 67,000+27d
  13. FEB 7MT AGMT AG notice308 MT residents+28d
  14. FEB 11CA AGCA AG noticemost recent · no count stated+32d
  15. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 18, 2024 – Jan 5, 2025
WA AG
Discovered
Dec 9, 2024WA AG + NH AG + ME AG +6Jan 4, 2025ME AGfilings disagree on discovery
Data types
Authentication · Financial account · Financial credentials · Identity (basic) · PCI · PII
WA AG + DE AG + VT AG +5
Attack vector
Ransomware
WA 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)

67,000

Sum of filed state slices

6,146· 9.2% of stated

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

US67,000
MA1,791
WA1,724
IN1,195
ME523
NH400
MT308
DE205

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

32 days

Cadence

~1 / 2.5d

vs. multi-state median

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