MemberSource Credit Union
bd_b2fc6079fb9d7fa0 · schema v1 · pii pii-v1
Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Safepay on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
MemberSource Credit Union is a not-for-profit financial cooperative based in Texas, USA. It provides a wide range of tailored financial services to its members, including savings and checking accounts, consumer loans, credit cards, mortgages, and investment services. It is member-owned and committed to providing competitive rates and fees.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jun 3, 2025
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (7) · sorted by filing gap
- Montana State AGbd_1fa68433c68e29442026-05-05 · +336dCandidate
- Nebraska State AGbd_1368db5c6ffe857e2026-05-07 · +338dVerified by operator
- Indiana State AGbd_61c95d24c3f146972026-05-07 · +338dVerified
- Massachusetts State AGbd_9aa063fac94e3ba32026-05-08 · +339dVerified
Show 3 more filings ↓Show fewer ↑up to 342d gap
- California State AGbd_9db84dbb566e334a2026-05-08 · +339dVerified
- Vermont State AGbd_c53f2485178b1a202026-05-08 · +339dVerified
- Texas State AGbd_aa1e8bc975a47fba2026-05-11 · +342dVerified
Filing propagation · 8 filings · 7 states
View merged incident ↗Pattern: first filing Jun 3, last May 11 (TX) — a 342-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
safepay
According to ransomware.live, SafePay emerged in September 2024 as a rapidly growing ransomware operation that explicitly disavows the RaaS model and manages all operations internally, claiming over 300 victims worldwide by mid-2025 with a high-profile early attack against UK telematics firm Microlise stealing 1.2 TB of data.