Memberclose LLC
ent_182d675fd5f1e143
Disclosures
4
State AG · 4 jurisdictions
Incidents
1
filings grouped by incident
Max affected reported
4,845
nationwide · State AG IN
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- Memberclose LLC
- Normalized
- memberclose— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- No match
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- None on record
Disclosure history (4)newest first
- ⛰️New Hampshire State AGas victim2026-01-20
Memberclose, LLC notified the New Hampshire Attorney General of a cybersecurity incident affecting 130 NH residents. Unauthorized access to a cloud application occurred around October 29, 2025, detected on October 30, 2025. Personal information including names, SSNs, and DOBs was exfiltrated. Memberclose engaged forensic investigators, secured the application, and provided 24 months of Kroll identity monitoring to affected individuals. Notifications were sent to residents on January 15, 2026.
- 🦞Maine State AGas victim2026-01-15
Memberclose LLC, a financial services company providing closing services, experienced an external hacking incident on October 29-30, 2025, in which an unauthorized party downloaded data from a cloud application. The breach was discovered on December 1, 2025. Compromised data included full names, dates of birth, and Social Security numbers. 4,845 individuals were affected total, including 48 Maine residents. Kroll credit monitoring was offered to affected individuals.
- 🍁Vermont State AGas victim2026-01-15
Memberclose LLC notified consumers of a data breach involving unauthorized access to a cloud application on October 29, 2025. Compromised data included names, dates of birth, and Social Security numbers. Memberclose engaged external cybersecurity professionals, secured the application, and offered complimentary identity monitoring services to affected individuals.
- 🏎️Indiana State AGas victim2026-01-15
Memberclose LLC reported a data breach to the Indiana Attorney General. The breach occurred on 2025-10-29 and was reported on 2026-01-15. 1 Indiana residents were affected. 4,845 individuals affected in total.