DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed9 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedplayhigh sensitivity
Merged incident · 9 filings

PAC Strapping Products — March 2025 breach

Clustered 9 filings across 7 jurisdictions · filing window Jan 13, 2025 → Sep 4, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

6

Affected · reported

647

First → last filing

Jan 13, 2025 → Sep 4, 2025

Merge confidence

100%

incident inc_e99d3a12ddf44e9a · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 2 unverified claims. The filings describe a ransomware attack. Intrusion Mar 26, 2025–Apr 2, 2025, discovered Apr 2, 2025 — the first regulatory filing landed 124 days later (flagged late). 647 individuals reported across the linked filings. Data reported: PII, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 234-day schedule across 7 filings beginning Jan 13, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
124days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
203days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
234days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap✗ Leak >180dVermont✗ VT AG >45 bdayMaine✗ ME AG >90d · 125dFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Mar 26, 2025breach begins
Apr 2, 2025discovered
notification delay · 124 days
Aug 4, 2025first filing
Sep 4, 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 13Leak siteplay postfirst filing · attacker claim · unverifiedday 0
  2. APR 2Leak siteplay postattacker claim · unverified+79d
  3. AUG 4NE AGNE AG noticeno count stated+203d
  4. AUG 4IN AGIN AG noticestates nationwide total 647+203d
  5. AUG 5VT AGVT AG noticeno count stated+204d
  6. AUG 5ME AGME AG noticestates nationwide total 647+204d
  7. AUG 5NH AGNH AG notice3 NH residents+204d
  8. SEP 2NH AGNH AG notice3 NH residents+232d
  9. SEP 4MA AGMA AG noticemost recent · 14 MA residents+234d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 26, 2025
IN AG
Discovered
Apr 2, 2025· 7d undetected
NE AG + VT AG + ME AG
Data types
Financial account · Financial credentials · Identity (basic) · PCI · PII
NE AG + VT AG + ME AG +2
Attack vector
Ransomware
NE 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)

647

Sum of filed state slices

29· 4.5% of stated

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

US647
MA14
IN10
NH3
ME2

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

234 days

Cadence

~1 / 29.3d

vs. multi-state median

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