DisclosureLens
Leak SiteState AGConfirmed4 filings · 3 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmedusahigh sensitivity
Merged incident · 4 filings

U S #1364 FEDERAL CREDIT UNION — February 2024 breach

Clustered 4 filings across 4 jurisdictions · filing window Mar 6, 2024 Apr 1, 2024. View entity profile → Other incidents for this victim →

1 cross-filing discrepancyMerge100%

Determination

Confirmed

Members

4 filings

States

3

Affected · reported

14,275

First → last filing

Mar 6, 2024 Apr 1, 2024

Merge confidence

100%

incident inc_108eca83ca4b4da0 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings and 1 unverified claim. The filing describes unauthorized access. Intrusion Feb 21, 2024–Feb 22, 2024. 14,275 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Financial account. Notifications rolled out on a 25-day schedule across 3 filings beginning Mar 6, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Leak precedence
19days before filing

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
25days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Materiality delta · SEC filing delayno 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

Feb 21, 2024breach begins
Mar 26, 2024first filing
Apr 1, 2024most recent filing

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

  1. MAR 6Leak sitemedusa postfirst filing · attacker claim · unverifiedday 0
  2. MAR 26IN AGIN AG noticestates nationwide total 14,275+19d
  3. MAR 26MT AGMT AG notice2 MT residents+19d
  4. APR 1MA AGMA AG noticemost recent · 3 MA residents+25d
  5. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 21, 2024
IN AG
Discovered
Data types
Financial account · Identity (basic) · Government ID
MT AG + MA AG
Attack vector
Unauthorized Access
MT 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)

14,275

Sum of filed state slices

12,662· 88.7% of stated

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

US14,275
IN12,657
MA3
MT2

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 filing3 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 Jun 5, 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

25 days

Cadence

~1 / 8.3d

vs. multi-state median

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