DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed13 filings · 12 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedransomhubhigh sensitivity
Merged incident · 13 filings

Rite Aid Corporation — June 2017 breach

Clustered 13 filings across 13 jurisdictions · filing window Jul 1, 2024 → Jul 15, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

13 filings

States

12

Affected · reported

2,200,000

First → last filing

Jul 1, 2024 → Jul 15, 2024

Merge confidence

100%

incident inc_b18d89caa33d4b43 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings and 1 unverified claim. Intrusion Jun 6, 2017–Jun 6, 2024, discovered Jun 6, 2024 — the first regulatory filing landed 25 days later (flagged late). 2,200,000 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 1 more. Notifications rolled out on a 14-day schedule across 12 filings beginning Jul 1, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
25days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 10d

Days between the first leak-site claim and the first regulatory filing. 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
14days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 6, 2017breach begins
Jun 6, 2024discovered
notification delay · 25 days
Jul 1, 2024first filing
Jul 15, 2024most 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. JUL 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JUL 11Leak siteransomhub postattacker claim · unverified+10d
  3. JUL 15SC AGSC AG notice33,685 SC residents+14d
  4. JUL 15MA AGMA AG notice59,708 MA residents+14d
  5. JUL 15OR AGOR AG noticestates nationwide total 2,200,000+14d
  6. JUL 15VT AGVT AG noticeno count stated+14d
  7. JUL 15WA AGWA AG notice96,270 WA residents+14d
  8. JUL 15IN AGIN AG noticestates nationwide total 2,200,000+14d
  9. JUL 15DE AGDE AG noticeno count stated+14d
  10. JUL 15NH AGNH AG noticestates nationwide total 2,200,000+14d
  11. JUL 15MT AGMT AG notice619 MT residents+14d
  12. JUL 15ME AGME AG noticestates nationwide total 2,200,000+14d
  13. JUL 15CA AGCA AG noticemost recent · no count stated+14d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 6, 2017 – Jul 30, 2018
SC AG
Discovered
Jun 6, 2024· 2557d undetected
IL AG + SC AG + OR AG +7
Data types
Behavior · Identity (basic) · Government ID · PII
SC AG + VT AG + WA AG +6
Attack vector
Unauthorized Access
SC 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)

2,200,000

Sum of filed state slices

263,463· 12.0% of stated

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

US2,200,000
WA96,270
MA59,708
NH36,121
SC33,685
ME30,137
IN6,923
MT619

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 filing12 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 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

14 days

Cadence

~1 / 1.2d

vs. multi-state median

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