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

Forever 21, Inc. — April 2017 breach

Clustered 5 filings across 5 jurisdictions · filing window Dec 28, 2017 → Jan 3, 2018. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

5 filings

States

5

Affected · reported

—

First → last filing

Dec 28, 2017 → Jan 3, 2018

Merge confidence

100%

incident inc_3f61b8f4fe9b47d0 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filing describes unauthorized access. Intrusion Apr 3, 2017–Nov 18, 2017, discovered Oct 1, 2017 — the first regulatory filing landed 88 days later (flagged late). Data reported: Financial account, PII, PCI, and 2 more. Notifications rolled out on a 6-day schedule across 5 filings beginning Dec 28, 2017. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
88days

Discovered → first regulatory filing

Discovery variance
15days

Range of discovered_at dates across filings

Filing span
6days

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

Sensitive data

financial_credentials

Incident timeline

Apr 3, 2017breach begins
Oct 1, 2017discovered · members disagree
notification delay · 88 days
Dec 28, 2017first filing
Jan 3, 2018most recent filing

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

Member cascade — every filing about this breach

  1. DEC 28OR AGOR AG noticefirst filing · no count statedday 0
  2. DEC 28WA AGWA AG noticeno count statedday 0
  3. DEC 28CA AGCA AG noticeno count statedday 0
  4. DEC 28NH AGNH AG noticeno count statedday 0
  5. JAN 3SC AGSC AG noticemost recent · no count stated+6d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 3, 2017 – Nov 18, 2017
OR AG
Discovered
Oct 1, 2017WA AGOct 15, 2017CA AG + NH AG + SC AGOct 16, 2017OR AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · PCI · PII
WA AG + CA AG + NH AG +1
Attack vector
Unauthorized Access
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 filing5 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
Reviewed
operator-reviewed Jun 12, 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

6 days

Cadence

~1 / 1.5d

vs. multi-state median

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