DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SitePressState AGConfirmed8 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 8 filings

SRP Federal Credit Union — September 2024 breach

Clustered 8 filings across 6 jurisdictions · filing window Dec 5, 2024 → Mar 6, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

8 filings

States

5

Affected · reported

260,950

First → last filing

Dec 5, 2024 → Mar 6, 2025

Merge confidence

100%

incident inc_f41fb5ac23a34bc8 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings, 1 press report and 1 unverified claim. The filings describe unauthorized access. Intrusion Sep 5, 2024–Nov 4, 2024, discovered Nov 22, 2024 — the first regulatory filing landed 20 days later. 260,950 individuals reported across the linked filings. Data reported: Government ID, Financial account, PCI, and 2 more. Notifications rolled out on a 122-day schedule across 6 filings beginning Dec 5, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
20days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
6days 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
122days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksMaine⏱ ME AG >30d · 73dLeak gap⏱ Leak >90dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 5, 2024breach begins
Nov 22, 2024discovered
notification delay · 20 days
Dec 12, 2024first filing
Mar 6, 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. DEC 5Leak sitenitrogen postfirst filing · attacker claim · unverifiedday 0
  2. DEC 12NE AGNE AG noticeno count stated+6d
  3. DEC 12MA AGMA AG notice103 MA residents+6d
  4. DEC 12MT AGMT AG notice23 MT residents+6d
  5. DEC 12ME AGME AG noticestates nationwide total 240,742+6d
  6. FEB 3ME AGME AG noticestates nationwide total 260,950+59d
  7. MAR 6SC AGSC AG noticemost recent · 136,503 SC residents+90d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 5, 2024 – Nov 4, 2024
NE AG
Discovered
Nov 22, 2024· 78d undetected
NE AG + MT AG + ME AG
Data types
Financial account · Identity (basic) · Government ID · PCI · PII
MA AG + ME AG + MT AG +1
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)

260,950

Sum of filed state slices

136,669· 52.4% of stated

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

US260,950
SC136,503
MA103
ME40
MT23

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 report1 member

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing6 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

122 days

Cadence

~1 / 17.4d

vs. multi-state median

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