All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed5 filings · 5 statesUnverified claimConfirmedEnforcedmoderate sensitivity

Merged incident · 5 filings

Sears Holdings Corporation — September 2017 breach

Clustered 5 filings across 5 jurisdictions · filing window Apr 24, 2018 → May 18, 2018. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

5 filings

States

Affected · reported

4,490

First → last filing

Apr 24, 2018 → May 18, 2018

Merge confidence

100%

incident inc_480d2ad8939b4cfe · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe a third-party compromise. Intrusion Sep 27, 2017–Oct 12, 2017, discovered Mar 1, 2018 — the first regulatory filing landed 54 days later (flagged late). 4,490 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, PII, and 1 more. Notifications rolled out on a 24-day schedule across 5 filings beginning Apr 24, 2018. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

54days

Discovered → first regulatory filing

Discovery variance

25days

Range of discovered_at dates across filings

Filing span

24days

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 clocksOregon✗ OR AG >45dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

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.