← Breach analysis by the Dual Vulnerabilities framework

loanDepot Ransomware and data theft (ALPHV/BlackCat, 2024)

2024 · United States · K - Financial and insurance activities · Ransomware attack with mass data theft and multi-week service outage

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Ransomware attack with mass data theft and multi-week service outage

Dual vulnerability type

Strategy to Execution

Evidence coverage: 3/6 stages, weight 16/60

Decisive stage: egress (clearest evidence) · Alternative: Expertise to Execution

Why this classification

(1) loanDepot is a supervised, publicly listed nonbank mortgage servicer (roughly 6,000 employees, over $140 billion in serviced loans, EuRepoC sector finance / critical infrastructure) holding the crown-jewel personal data - names, dates of birth, Social Security numbers, financial account numbers - of some 16.9 million Americans; the strategic expectation on that posture is protected, monitored data holdings and a servicing estate whose core can be isolated without going dark, a commitment its own SEC and state-AG filings evidence. (2) In practice a single ALPHV/BlackCat intrusion (entry vector never disclosed - it is not load-bearing for this classification) running January 3-5, 2024 encrypted files and took that data out unseen; the company's effective containment was a precautionary shutdown of payments, phone lines and every customer portal that left borrowers unable to pay for about a week (restored by January 19), and its investigation could not say what data was taken even on January 22, delivering categories and the final 16,924,071 count only on February 23-26, after ALPHV had posted the victim on its leak site on February 16, with the stolen volume never disclosed and the incident cost later reported at $12-17 million. (3) The doctrinal expectations existed and were publicly owned, yet they did not translate into operational reality: no egress barrier detected or interrupted a multi-million-record transfer, the architecture was so coupled that containing one intrusion meant a whole-estate outage, and forensic scoping dragged on for six-plus weeks - a doctrinal-to-material gap, Strategy to Execution, not merely weak security; the classification rests on the egress stage, with containment pointing to the same type. A secondary pattern sits in the response stage (Strategy to Leadership): disclosure stayed incomplete and conservative until the attacker's leak forced the specifics. RM04 (Strategy to Execution lens): architecture concentrated the whole customer-facing estate - payments, phones, portals - behind systems the single intrusion reached, so the only viable containment was a company-wide precautionary shutdown that materially amplified the impact (causal role: Amplifying). RM35 (Strategy to Execution lens): egress expectations for a supervised lender holding SSNs and account data of 16.9 million individuals were never translated into an effective operational barrier - the data left during January 3-5 without detection or interruption (causal role: Amplifying). RM33 (Strategy to Execution lens): logging and evidence-preservation requirements were not implemented to the point where scope stayed undetermined - which data, how much, how many people were open questions for over six weeks and the volume was never established (causal role: Obscuring).

Evidence by stage

Risk markers

Sources

Notes

EuRepoC row; victim, country (receiver_country) and year (start_date 06.01.2024, attack window January 3-5) taken from the case file; attribution is the group's own leak-site claim of February 16, 2024 as reported by BleepingComputer. The initial access vector of this incident was never disclosed - the phishing/legacy-authentication/MFA-bypass details circulating in some write-ups belong to loanDepot's earlier breach (August 2022 intrusion, disclosed May 2023), not to this one; they were deliberately not used, and no recurring-weakness or authentication marker is coded because no source shows this intrusion used a comparable weakness. ALPHV's claims (a USD 6 million offer, loanDepot 'cutting corners', 4 TB of undisclosed extra data, statements about its CIO) are unverified attacker claims reported via press and are not load-bearing for the classification. The February 23 notification letter itself (Maine AG portal) could not be opened directly and is cited as reported by Cybernews, Bitdefender and SecurityWeek quoting the filing; a Hawaii copy of the letter returned 404 at link-check time and is not cited. EuRepoC records a US law-enforcement legal response; no regulator finding on loanDepot's controls was available at analysis date, and class actions were pending. Cost figure of $12-17 million per National Mortgage Professional, citing the company's regulatory filing. Link check: sec.gov blocks automated access (HTTP 403); the page was opened and read during research. Link check: nationalmortgageprofessional.com blocks automated access (HTTP 403); the page was opened and read during research. Unattended run: nothing was skipped for consent.