GLOBALClaimed by CephalusFirst sightinglinked via cross-source match · 100%
Posted to leak site Aug 26, 2025bd_a7104fdbf8649143
LPL Financial DATA LEAK | (I FORGOT THE SIZE,BUT ITS HUGE)
Clustered 3 filings across 3 jurisdictions · filing window Aug 26, 2025 → Apr 27, 2026. View entity profile → Other incidents for this victim →
incident inc_1f9f8e5aed0940e7 · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
PII · Financial
ME NH
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
LPL Financial DATA LEAK | (I FORGOT THE SIZE,BUT ITS HUGE)
Nov 10, 2025
When the intrusion reportedly occurred, per the linked filings
Nov 20, 2025
Reported by MAINE AG, NEW HAMPSHIRE AG filings
LPL Financial LLC: phishing messages delivered malware to affiliated advisor devices (Nov 10-20, 2025), enabling unauthorized portal access and fraudulent securities transactions/transfers. Law enforcement notified; accounts restored. 1,581 total affected; 2 Maine residents. Experian 24-month credit monitoring offered.
LPL Financial LLC notified the New Hampshire Attorney General of a cybersecurity incident affecting four NH residents. Between Nov 20-25, 2025, phishing messages distributed malware to financial advisors' devices, granting unauthorized third-party access to LPL's encrypted web-based advisor portal. The incident exposed personal information (name, DOB, SSN, account numbers, email, phone) of four individuals. LPL restored accounts, engaged forensic experts, and is offering two years of credit monitoring. No identity theft was identified.
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.
Affected (this filing): 2
Affected (this filing): 4