Forever 21, Inc. — February 2018 breach
Clustered 2 filings across 1 jurisdiction · filing window Jun 1, 2018 → Jun 22, 2018. View entity profile → Other incidents for this victim →
incident inc_1ea20eab7d164dbe · merged by llm · confidence 81%
Litigation Timing
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.
Incident timeline
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
- JUN 1CA AGCA AG noticefirst filing · no count statedday 0
- JUN 22CA AGCA AG noticemost recent · no count stated+21d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Feb 15, 2018 – Mar 23, 2018 CA AG
- Discovered
- —
- Data types
- Employment · Health (basic) · Identity (basic) CA AG
- Attack vector
- Third-Party / Supply Chain 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
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
Merge provenance
- Method
- llm
- Confidence
- 0.81 · below the 0.85 auto-merge floor
- Audit
- Every link edge records its method, confidence and model + prompt versions (81% is the strongest edge).
Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.
Filing velocity
Spread
21 days
vs. multi-state median
2.6× 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.