DisclosureLens
Leak SiteState AGConfirmed6 records · 4 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedakirahigh sensitivity
Merged incident · 6 records

Metrowest Community Federal Credit Union — September 2025 breach

Clustered 6 records across 4 jurisdictions: 5 filings and 1 leak-site claim · filing window Dec 29, 2025 → Mar 10, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 records

States

4

Affected · reported

20,722

First → last filing

Dec 29, 2025 → Mar 10, 2026

Merge confidence

100%

incident inc_4882c870f00b4a82 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Sep 1, 2025–Sep 3, 2025, discovered Sep 1, 2025 — the first regulatory filing landed 119 days later (flagged late); 1 later filing was also flagged late. 20,722 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 71-day schedule across 5 filings beginning Dec 29, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
119days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
65days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
71days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont✗ VT AG >45 bdayLeak gap⏱ Leak >30dMaine⏱ ME AG >30d · 190dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 1, 2025breach begins
Sep 1, 2025discovered
notification delay · 119 days
Dec 29, 2025first filing
Mar 10, 2026most recent filing

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

Member cascade — every filing and leak-site claim in this incident

  1. OCT 25Leak siteakira postfirst record · attacker claim · unverifiedday 0
  2. DEC 29VT AGVT AG noticeno count stated+65d
  3. DEC 29MA AGMA AG notice18,646 MA residents+65d
  4. MAR 6VT AGVT AG noticeno count stated+132d
  5. MAR 10IN AGIN AG noticestates nationwide total 20,722+136d
  6. MAR 10ME AGME AG noticemost recent · states nationwide total 20,722+136d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 3, 2025
VT AG
Discovered
Sep 1, 2025
VT AG + ME AG
Data types
Financial account · Identity (basic) · Government ID · PCI
VT AG + ME AG + MA AG
Attack vector
Unauthorized Access
VT 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)

20,722

Sum of filed state slices

18,788· 90.7% of stated

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

US20,722
MA18,646
ME132
IN10

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

71 days

Cadence

~1 / 17.8d

vs. multi-state median

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