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

CITIZENS FINANCIAL GROUP, INC. — April 2017 breach

Clustered 11 filings across 2 jurisdictions · filing window Jun 7, 2017 → Oct 4, 2017. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

2

Affected · reported

not comparable

First → last filing

Jun 7, 2017 → Oct 4, 2017

Merge confidence

100%

incident inc_43667fd639904851 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe a physical incident. Intrusion Apr 1, 2017–Sep 7, 2017, discovered May 25, 2017 — the first regulatory filing landed 13 days later. Data reported: PCI, Financial account, Identity (basic), and 2 more. Notifications rolled out on a 119-day schedule across 11 filings beginning Jun 7, 2017. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
13days

Discovered → first regulatory filing

Discovery variance
113days

Range of discovered_at dates across filings

Filing span
119days

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.

Sensitive data

authenticationfinancial_credentials

Incident timeline

Apr 1, 2017breach begins
May 25, 2017discovered · members disagree
notification delay · 13 days
Jun 7, 2017first filing
Oct 4, 2017most 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. JUN 7MA AGMA AG noticefirst filing · 3 MA residentsday 0
  2. JUN 7NH AGNH AG notice7 NH residentsday 0
  3. JUL 6MA AGMA AG notice1 MA residents+29d
  4. JUL 7NH AGNH AG notice1 NH residents+30d
  5. JUL 31MA AGMA AG notice4,542 MA residents+54d
  6. AUG 1NH AGNH AG notice3 NH residents+55d
  7. AUG 2MA AGMA AG notice7 MA residents+56d
  8. AUG 29NH AGNH AG notice1 NH residents+83d
  9. SEP 6MA AGMA AG notice4 MA residents+91d
  10. OCT 4NH AGNH AG notice3 NH residents+119d
  11. OCT 4MA AGMA AG noticemost recent · 213 MA residents+119d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 1, 2017 – Apr 30, 2017
NH AG
Discovered
May 25, 2017NH AGJun 23, 2017NH AGJul 9, 2017NH AGAug 14, 2017NH AGSep 15, 2017NH AGfilings disagree on discovery
Data types
Authentication · Financial account · Financial credentials · Identity (basic) · PCI
MA AG + NH 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 filing11 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

119 days

Cadence

~1 / 11.9d

vs. multi-state median

19.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.