Incident · 8-K Item 8.01
loanDepot reports encryption of data and later notifies up to 16.9 million people
Compiled from public records. Updated 2026-11-13. By the cisonews.net Desk.
The loanDepot data breach affected 16,924,071 people, the total loanDepot.com, LLC reported to Indiana's attorney general for notices sent on February 23, 2024, for a breach dated January 3, 2024. loanDepot, Inc. told the SEC in an Item 8.01 Form 8-K dated January 8, 2024 that it had identified a cybersecurity incident in which an unauthorized third party reached certain systems and encrypted data. A second amendment filed after February 26, 2024 said the company would notify up to approximately 16.9 million individuals whose sensitive personal information was impacted. Indiana's attorney general later recorded 16,924,071 people affected in total.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.
What happened at loanDepot, and when?
The original filing says the company identified the incident and, on detecting unauthorized activity, took steps to contain it and began notifying regulators and law enforcement. The company described the third-party activity as access to certain company systems and the encryption of data. In response, it shut down certain systems while it worked to bring systems back online. The cover page lists January 4, 2024 as the date of the earliest event reported.
What loanDepot customer data was taken?
The filings do not list data fields such as Social Security numbers, account details or dates of birth. The only description is sensitive personal information, and the second amendment says affected people will be offered credit monitoring and identity protection at no cost. That amendment also says the company has contained the incident. The filings do not state whether the people are customers, employees or others.
How did the attack affect loanDepot's business?
The first amendment, filed January 22, 2024, attached a press release and said the company had not yet decided whether the incident was reasonably likely to materially affect its finances. The second amendment gave a view: a material effect on first quarter 2024 results, but not on full year 2024 results. It expects to record about $12 to $17 million of related expenses in that quarter, net of expected insurance recovery. The company also reports that it has been named in several lawsuits seeking monetary and injunctive relief.
How many people were affected by the loanDepot breach?
Indiana's attorney general lists loanDepot.com, LLC in its 2024 breach report, with notice sent on February 23, 2024 for a breach that occurred on January 3, 2024: 302,021 Indiana residents and 16,924,071 people affected in total. The total is the figure the organization reported to Indiana.
What did the loanDepot breach cost?
loanDepot's 2024 quarterly reports put figures on the January incident.
The 10-Q for the first quarter of 2024, filed on May 9, 2024, records $14.7 million of incident expenses, net of expected insurance recovery, in addition to lost revenue.
The third-quarter 10-Q, filed on November 12, 2024, credits a $20.0 million insurance claim receivable for most of a $19.6 million fall in professional and consulting costs. It also mentions guarantees paid on commissions because of volume lost during the incident.
How many Delaware residents were affected?
Delaware's attorney general lists a report from Loan Depot.Com, LLC dated February 23, 2024, for a breach it dates from January 3, 2024 to January 5, 2024, with 64,509 Delaware residents potentially affected. That count covers Delaware residents only.
How many Washington residents were affected?
Washington's attorney general lists a report from loanDepot.com, LLC on February 15, 2024, for a breach dated January 3, 2024, with 502,513 Washingtonians affected. The information it records as compromised is: name, Social Security number, financial and banking information and full date of birth. That count covers Washington residents only.
How many Massachusetts residents were affected?
Massachusetts' Office of Consumer Affairs and Business Regulation lists a report from loanDepot.com, LLC dated February 23, 2024 (breach 2024-355): 406,849 Massachusetts residents affected. The categories it marks as breached are Social Security numbers, financial account numbers and credit or debit card numbers. The report date sits next to the February 23, 2024 notice date that Indiana records, which ties this row to the same incident. That count covers Massachusetts residents only.
What is still unknown?
The filings give no date on which the company detected the activity and do not say how the third party gained access. They do not say whether data was copied or taken, beyond the encryption described. At the time of those filings, the company said it could not yet quantify the full scope of expenses, including costs of litigation or regulatory inquiries; the later 10-Q figures are set out above. The filings do not state a notification date, a letter enrollment deadline or a breakdown of the 16.9 million by state.
The rule behind an Item 8.01 filing
Item 8.01 (Other Events) is the item the SEC's Division of Corporation Finance encouraged companies to use for a cybersecurity incident they have not yet determined to be material, or have determined is not material. Its May 21, 2024 statement says a company that later determines the incident is material should file under Item 1.05 within four business days of that decision. Source: U.S. Securities and Exchange Commission, statement by the Director of the Division of Corporation Finance. The guide Item 8.01 versus Item 1.05: when a cyber incident moves between them reads the rule in full, and the glossary defines Form 8-K Item 1.05.
Other financial services incidents on cisonews.net
- ICW Group Holdings, Inc., Breach notice, first disclosed November 13, 2026
- Point72 Asset Management, L.P., Breach notice, first disclosed November 5, 2026
- The Vanguard Group, Inc., Breach notice, first disclosed November 4, 2026
- Hippo Analytics, Breach notice, first disclosed November 3, 2026; 176,128 affected in total (Indiana Attorney General)
- Baanx US Corp, Breach notice, first disclosed October 30, 2026; 6,594 affected in total (Indiana Attorney General)
Sources
- 2026-11-06 · AWashington State Office of the Attorney General, data breach notifications list, published November 6, 2026
- 2026-11-05 · AIndiana Attorney General, data breach year-to-date report (2024), published November 5, 2026
- 2024-01-08 · AloanDepot, Inc., Form 8-K (SEC EDGAR), published January 8, 2024
- 2024-01-22 · AloanDepot, Inc., Form 8-K/A (SEC EDGAR), published January 22, 2024
- 2024-02-27 · AloanDepot, Inc., Form 8-K/A (SEC EDGAR), published February 27, 2024
- 2024-05-09 · AloanDepot, Form 10-Q for the period ended 2024-03-31 (SEC EDGAR), published May 9, 2024
- 2024-11-12 · AloanDepot, Form 10-Q for the period ended 2024-09-30 (SEC EDGAR), published November 12, 2024
- 2026-11-06 · ADelaware Department of Justice, security breach notification database, published November 6, 2026
- 2026-11-06 · AMassachusetts Office of Consumer Affairs and Business Regulation, 2024 Data Breach Notification Report, published November 6, 2026
- 2024-05-21 · AU.S. Securities and Exchange Commission, statement by the Director of the Division of Corporation Finance, published May 21, 2024
Tier A: the organization itself (including notices it filed with a state attorney general), a regulator or SEC EDGAR. Tier B: established press. Each fact on this page carries its supporting passage in the page source.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.