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

Rockland Trust Company — November 2024 breach

Clustered 9 filings across 2 jurisdictions · filing window Jun 24, 2025 → Sep 23, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

2

Affected · reported

not comparable

First → last filing

Jun 24, 2025 → Sep 23, 2025

Merge confidence

100%

incident inc_13021aefc6164324 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filing describes a third-party compromise. Intrusion Nov 6, 2024, discovered Jun 30, 2025. Data reported: Government ID, Financial account, and Identity (basic). Notifications rolled out on a 91-day schedule across 9 filings beginning Jun 24, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Filing span
91days

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.

Regulatory clocksMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 6, 2024breach begins
Jun 30, 2025discovered
Jun 24, 2025first filing
Sep 23, 2025most 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 24MA AGMA AG noticefirst filing · 1 MA residentsday 0
  2. JUN 24MA AGMA AG notice2 MA residentsday 0
  3. JUL 15MA AGMA AG notice2 MA residents+21d
  4. JUL 15MA AGMA AG notice1 MA residents+21d
  5. JUL 15MA AGMA AG notice1 MA residents+21d
  6. JUL 18MA AGMA AG notice14 MA residents+24d
  7. JUL 18NH AGNH AG noticeno count stated+24d
  8. AUG 5MA AGMA AG notice2 MA residents+42d
  9. SEP 23MA AGMA AG noticemost recent · 2 MA residents+91d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 6, 2024
NH AG
Discovered
Jun 30, 2025· 236d undetected
NH AG
Data types
Financial account · Identity (basic) · Government ID
MA AG + NH AG
Attack vector
Third-Party / Supply Chain
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 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

91 days

Cadence

~1 / 11.4d

vs. multi-state median

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