DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed5 records · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 5 records

WK KELLOGG CO — December 2024 breach

Clustered 5 records across 4 jurisdictions: 4 filings and 1 leak-site claim · filed Apr 4, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 records

States

4

Affected · reported

4,093

First → last filing

Apr 4, 2025

Merge confidence

100%

incident inc_1a20b000f2594a70 · merged by human · confidence 100%

Part of the Cleo supply-chain incident (2025) — at least 2 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 4 regulatory filings and 1 unverified claim. The filings describe a third-party compromise. Intrusion Dec 7, 2024, discovered Feb 27, 2025 — the first regulatory filing landed 36 days later. 4,093 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
36days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
36days 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
0days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksMaine⏱ ME AG >30d · 36dLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 7, 2024breach begins
Feb 27, 2025discovered
notification delay · 36 days
Apr 4, 2025first filing
—watching for filings

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. FEB 27Leak sitecl0p postfirst record · attacker claim · unverifiedday 0
  2. APR 4ME AGME AG notice1 ME residents+36d
  3. APR 4IN AGIN AG noticestates nationwide total 4,093+36d
  4. APR 4NH AGNH AG noticeno count stated+36d
  5. APR 4MA AGMA AG noticemost recent · 10 MA residents+36d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 7, 2024
ME AG
Discovered
Feb 27, 2025· 82d undetected
ME AG + NH AG
Data types
Identity (basic) · Government ID · PII
ME AG + NH AG + MA AG
Attack vector
Third-Party / Supply Chain
ME 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)

4,093

Sum of filed state slices

32· 0.8% of stated

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

US4,093
IN21
MA10
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 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 Aug 22, 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

0 days

Cadence

~1 / 0d

vs. multi-state median

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