DisclosureLens
Leak SiteState AGConfirmed5 records · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedblack_bastahigh sensitivity
Merged incident · 5 records

Peco Foods Inc. — December 2023 breach

Clustered 5 records across 4 jurisdictions: 4 filings and 1 leak-site claim · filing window Jul 24, 2024 → Jul 25, 2024. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

5 records

States

4

Affected · reported

48,170

First → last filing

Jul 24, 2024 → Jul 25, 2024

Merge confidence

100%

incident inc_b06193fccf3d49b9 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Dec 4, 2023–Dec 6, 2023, discovered Dec 4, 2023 — the first regulatory filing landed 233 days later. 48,170 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
233days

Discovered → first regulatory filing

Discovery variance
171days

Range of discovered_at dates across filings

Leak precedence
218days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
1days

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 >180dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 4, 2023breach begins
Dec 4, 2023discovered · members disagree
notification delay · 233 days
Jul 24, 2024first filing
Jul 25, 2024most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing and leak-site claim in this incident

  1. DEC 19Leak siteblack_basta postfirst record · attacker claim · unverifiedday 0
  2. JUL 24VT AGVT AG noticeno count stated+217d
  3. JUL 24IN AGIN AG noticestates nationwide total 48,170+217d
  4. JUL 25MT AGMT AG notice4 MT residents+218d
  5. JUL 25ME AGME AG noticemost recent · states nationwide total 48,170+218d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 4, 2023
VT AG
Discovered
Dec 4, 2023MT AGMay 23, 2024ME AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
VT AG + MT AG + ME AG
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)

48,170

Sum of filed state slices

93· 0.2% of stated

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

US48,170
IN87
MT4
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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing4 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 Oct 29, 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.3d

vs. multi-state median

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