DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

loanDepot notifying 17 million customers after ransomware attack in January

Posted on February 26, 2024 by Dissent

On February 16, BlackCat added loanDepot to their dark web leak site, but without any data as proof. At the time, they claimed that LoanDepot had shown up in the negotiation chat, and had offered $6 million for the data and a decryptor, but allegedly claimed they could offer more after the weekend. But after the weekend, they reportedly never showed up again.

BlackCat also made a number of other allegations about LoanDepot and its incident management, but none of those claims are readily verifiable or refuted by DataBreaches and hence, are not being repeated.

This week, loanDepot submitted a breach notification to the Maine Attorney General’s Office. That report, filed by their external counsel, indicates that   16,924,071 customers were affected by the incident.

In its letter to those affected, loanDepot writes that they discovered the incident on January 4. Investigation revealed that data had been exfiltrated between January 3 and January 5 and may have impacted consumers’ name, address, email address, financial account numbers, social security number, phone number, and date of birth.

The notification letter does not mention that data were locked, or whether loanDepot had backups of consumer data that it could use to restore all functions and operations, but BlackCat states that the firm sought to purchase a decryptor from them during its negotiations. loanDepot’s notification letter of February 23 was silent about the impact of the attack on its functioning, but it has been posting status updates on its website since January 8. Those updates seem to suggest that most, if not all,  operations are functional again.

Affected consumers are being offered two years of complimentary services with Experian.


Related:

  • A business's cyber insurance policy included ransom coverage, but when they needed it, the insurer refused to pay. Why?
  • Before Their Telegram Channel Was Banned Again, ScatteredLAPSUS$Hunters Dropped Files Doxing Government Employees (2)
  • The Alliance That Wasn’t: A Critical Analysis of ReliaQuest’s Q3 2025 Ransomware Report
  • Heritage Provider Network $49.99M Class Action Settlement
  • Qilin Ransomware and the Ghost Bulletproof Hosting Conglomerate
  • Attorney General James Secures $14.2 Million from Car Insurance Companies Over Data Breaches
Category: Breach IncidentsFinancial SectorMalware

Post navigation

← School cyber incidents on Long Island: Reported cases rose sharply in 2023
Yes, Change Healthcare breach was us — BlackCat →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Suspected Russian hacker reportedly detained in Thailand, faces possible US extradition
  • Did you hear the one about the ransom victim who made a ransom installment payment after they were told that it wouldn’t be accepted?
  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • Lawmakers Warn Governors About Sharing Drivers’ Data with Federal Government
  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[at]databreaches.net
Mastodon: Infosec.Exchange/@PogoWasRight
Signal: +1 516-776-7756
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.