DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed2 filings · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 2 filings

Epic Foods — October 2014 breach

Clustered 2 filings across 1 jurisdiction · filing window Mar 9, 2015 → Apr 21, 2015. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge89%

Determination

Confirmed

Members

2 filings

States

1

Affected · reported

—

First → last filing

Mar 9, 2015 → Apr 21, 2015

Merge confidence

89%

incident inc_db3e7be445ae4c34 · merged by deterministic · confidence 89%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filings describe malware. Intrusion Oct 2, 2014–Mar 13, 2015. Data reported: PCI, Financial account, Identity (basic), and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Filing span
43days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.

Sensitive data

financial_credentials

Incident timeline

Oct 2, 2014breach begins
Mar 9, 2015first filing
Apr 21, 2015most recent filing

No discovery date is recorded on any filing in this cluster, so the notification delay is not computable. Dashed segments fill in as filings merge.

Member cascade — every filing about this breach

  1. MAR 9CA AGCA AG noticefirst filing · no count statedday 0
  2. APR 21CA AGCA AG noticemost recent · no count stated+43d
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 2, 2014 – Dec 4, 2014
CA AG
Discovered
—
Data types
Financial account · Financial credentials · Identity (basic) · PCI
CA AG

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

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 filing2 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
0.89 · above the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (89% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

43 days

vs. multi-state median

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