The Money Store Data Breach Lawsuit Puts Mortgage Borrower Security in Focus

| 5 min read

The alleged 37-day gap between a cyberattack and borrower notification sits at the center of a new lawsuit against The Money Store. That interval matters because the usefulness of a warning can depend on how soon a borrower receives it: earlier notice gives people more time to review accounts, watch for suspicious activity or consider steps such as a credit freeze. The case also raises questions for mortgage lenders about protecting application data and explaining what happened when information may have been exposed. The allegations remain unproven.

Filed October 21, 2026, in U.S. District Court in New Jersey, the proposed class action names MLD Mortgage, Inc., which operates as The Money Store. The complaint alleges that attackers gained access to borrower information beginning on or around September 8. The data allegedly included names, Social Security numbers, birth dates, driver’s license details, taxpayer identification numbers and financial records. That mix can make a breach more consequential than the loss of contact details alone, since it combines identity information with sensitive financial material.

The named plaintiff, an Illinois resident who says he used the lender’s home loan services in 2025, alleges he first received notice on October 15. He claims the delay denied affected borrowers a timely chance to take steps such as freezing credit or monitoring accounts. A court will have to assess the notice timeline and the claimed harm; the complaint’s account is not a judicial finding. For borrowers, the practical question is whether the warning arrived early enough to help them respond.

Ransomware group’s claim remains unverified

The complaint cites a ransomware monitoring group’s attribution of the incident to an operation called “Storm.” It alleges Storm posted a claim on its dark web leak site around September 21, saying it had hacked The Money Store. The suit treats that post as evidence that the group accessed the lender’s network and published borrower data, but those claims have not been tested in court. A group’s online claim can be a lead in understanding an incident; on its own, it doesn’t establish what systems were reached or what information was taken.

The plaintiff also reports a rise in spam and scam emails, texts and phone calls after the alleged breach. He says physical spam letters began arriving at the property associated with his loan application. The filing links these experiences to the incident, but it does not establish their source. Timing may prompt a reasonable question, yet it doesn’t by itself show that the alleged attackers used the plaintiff’s information. (And this is the part most people overlook.)

Complaint details alleged security failures

The lawsuit says The Money Store fell short of the NIST Cybersecurity Framework Version 2.0 and the Center for Internet Security’s Critical Security Controls. It identifies 18 NIST controls it alleges the lender failed to meet, involving access management, data protection, incident response and network monitoring. These categories cover different parts of protecting information: who can reach it, how it’s secured, how a company detects suspicious activity and what it does after a problem is identified. The complaint’s list describes the plaintiff’s theory of the case, not a finding that each control was absent or breached.

The complaint also alleges violations of the Gramm-Leach-Bliley Act’s Privacy and Safeguards Rules. It says the lender lacked a written information security program, did not properly assess foreseeable risks to consumer data and failed to provide annual privacy notices to some customers whose information remained on file after their loans closed. Those are separate allegations about both data protection and customer communication. If you’re working in this space, the distinction matters: a breach claim can raise questions about technical safeguards, while notice and retained records raise questions about how a lender manages information over time.

To support its claims, the filing quotes the company’s privacy policy: “To protect your personal information from unauthorized access and use, we use security measures that comply with federal law.” The plaintiff argues the alleged breach shows the lender did not meet that stated commitment. A policy statement may become relevant when a complaint claims a company promised to protect information, though the quoted language alone doesn’t resolve whether the company met its obligations. The lawsuit will turn on evidence and legal arguments that aren’t set out in the quoted promise.

Proposed class size and relief sought

The complaint advances eight claims, including allegations of negligence, broken promises to protect data, statutory violations and invasion of privacy. It asks the court to declare the lender’s security practices inadequate and require improvements. The filing therefore seeks more than an individual remedy: it asks the court to consider whether the alleged practices affected a wider group and whether changes should be ordered. Those requests are claims for relief, not outcomes the court has granted.

The proposed class includes U.S. residents whose personal information was allegedly compromised. The filing says the number is not yet known but exceeds 100, and places the amount in dispute above $5 million. Those figures describe the complaint’s account of the proposed case; the class has not been established by a court. The eventual scope could depend on evidence about whose information was involved and whether the legal requirements for a class action are met.

Why the case matters to mortgage firms

For mortgage firms, the case puts the handling of loan application records under scrutiny: lenders collect identifiers and financial details that can expose customers to harm if misused. The allegations also focus attention on the time between discovering a possible intrusion and notifying borrowers. That interval can shape how much warning people receive, although the complaint’s timeline and its account of resulting harm remain disputed allegations. This is more significant than it looks.

And yet, the filing doesn’t establish that Storm caused the reported spam, that every named category of information was published, or that the lender violated the standards cited in the complaint. The court has not ruled on the allegations, and the case’s claims remain unproven. What this means for you, if you handle borrower records, is that security claims and communication timelines can face scrutiny together when a breach is alleged. The dispute will now test those claims against evidence.

Source: Christopher Johnson · www.mpamag.com