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

The Neiman Marcus Group LLC — May 2020 breach

Clustered 9 filings across 9 jurisdictions · filing window Sep 30, 2021 → Oct 4, 2021 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

4,354,346

First → last dated filing

Sep 30, 2021 → Oct 4, 2021

Merge confidence

100%

incident inc_60a14289ee1b4f88 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe unauthorized access. Intrusion May 1, 2020–May 31, 2020, discovered May 1, 2021. 4,354,346 individuals reported across the linked filings. Data reported: PCI, Financial account, Authentication, and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
131days

Range of discovered_at dates across filings

Filing span
4days

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 clocksWashington✓ WA AG ≤30dOregon✓ OR AG ≤45dCalifornia✓ CA 60-day OK · 29dMaine✓ ME AG ≤30d · 22dFull clock table in Litigation Timeline

Sensitive data

authentication

Incident timeline

May 1, 2020breach begins
May 1, 2021discovered · members disagree
Sep 30, 2021first dated filing
Oct 4, 2021most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. SEP 30MA AGMA AG noticefirst filing · 112,471 MA residentsday 0
  3. SEP 30WA AGWA AG notice67,410 WA residentsday 0
  4. SEP 30OR AGOR AG noticestates nationwide total 4,354,346day 0
  5. SEP 30IN AGIN AG noticestates nationwide total 4,354,346day 0
  6. SEP 30CA AGCA AG noticeno count statedday 0
  7. SEP 30DE AGDE AG noticeno count statedday 0
  8. OCT 1ME AGME AG noticestates nationwide total 4,354,346+1d
  9. OCT 4NH AGNH AG noticemost recent · 11,557 NH residents+4d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 2, 2020 – May 17, 2020
WA AG
Discovered
May 1, 2021IL AG + DE AGSep 1, 2021WA AG + CA AG + NH AGSep 9, 2021OR AG + ME AGfilings disagree on discovery
Data types
Authentication · Credentials · Financial account · Identity (basic) · PCI
MA AG + WA AG + CA AG +3
Attack vector
Unauthorized Access
WA 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,354,346

Sum of filed state slices

229,381· 5.3% of stated

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

US4,354,346
MA112,471
WA67,410
IN31,992
NH11,557
ME5,951

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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing9 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
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

4 days

Cadence

~1 / 0.6d

vs. multi-state median

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