17.6 million
Prosper, a major peer-to-peer lending platform, has suffered a large-scale data breach impacting an estimated 17.6 million user accounts. The compromised data, which includes personally identifiable information (PII) such as full names, email addresses, and phone numbers, has been verified and added to the Have I Been Pwned database. This incident creates a significant and immediate risk for affected individuals, who are now prime targets for sophisticated phishing attacks, identity theft, and other forms of fraud. All Prosper users should assume they are affected and take immediate steps to secure their accounts and remain vigilant against suspicious communications.
On October 17, 2025, the 'Have I Been Pwned' service announced the addition of the Prosper breach data, following confirmation from the company of unauthorized access to its systems. While the specific threat actor and attack vector have not been disclosed, the scale of the breach indicates a significant failure in data protection controls. The exfiltrated data provides malicious actors with a rich dataset to craft highly convincing and personalized attacks.
The primary threats to the 17.6 million affected users are:
The breach involves the exfiltration of a large database of user PII. The attack likely involved an adversary gaining access to a production database or a backup containing customer information. Common attack paths for this type of breach include:
T1190 - Exploit Public-Facing Application: Exploiting a vulnerability in a web application connected to the database.T1078 - Valid Accounts: Using compromised credentials of an employee or service account with access to the data.T1530 - Data from Cloud Storage Object: Accessing a misconfigured or poorly secured cloud storage bucket (e.g., AWS S3) containing the user data.Once access was gained, the threat actor would have used a technique like T1020 - Automated Exfiltration to transfer the large volume of data out of Prosper's environment.
The business impact on Prosper includes significant reputational damage, potential regulatory fines for data protection failures, and costs associated with incident response and customer support. For the 17.6 million affected individuals, the impact is direct and personal. The breach erodes trust and exposes them to a long-term risk of financial fraud and identity theft. The inclusion of the data in 'Have I Been Pwned' is a double-edged sword: it provides easy notification for users but also confirms the data's availability to a wider audience of malicious actors.
haveibeenpwned.com and enter your email address to confirm if you were part of this breach.Prosper breach now confirmed to include Social Security Numbers, physical addresses, and income levels for 17.6M users.
Encrypting sensitive customer data both at rest and in transit can prevent it from being usable even if exfiltrated.
Enforcing MFA for both customer accounts and internal administrative access to databases can prevent account takeover and unauthorized data access.
Mapped D3FEND Techniques:
For users affected by the Prosper breach, the single most effective action is to enable multi-factor authentication on all sensitive accounts, especially financial ones. Given that the breach exposed phone numbers, which are vulnerable to SIM swapping, users should prioritize authenticator apps (like Google Authenticator, Microsoft Authenticator, or Authy) or hardware security keys (like a Yubikey) over SMS-based 2FA. For organizations like Prosper, this incident underscores the necessity of mandating MFA for all customer accounts and, critically, for all internal employees and systems with access to sensitive data. Implementing MFA would have made it significantly harder for an attacker to gain access to the database using potentially compromised credentials, a common vector for such breaches.
To prevent or detect a breach like the one at Prosper, organizations must implement Resource Access Pattern Analysis, particularly on critical data stores like customer databases. Security teams should establish a baseline of normal access patterns: which applications and user accounts access the database, from where, at what times, and how much data they typically query. A system should then be configured to alert on significant deviations from this baseline. For example, an alert should trigger if a service account that normally performs small, transactional queries suddenly attempts to export the entire 17.6 million-record user table. Similarly, access from an unfamiliar IP address or at an unusual time of day should be flagged. This behavioral analysis can detect a breach in progress before the data exfiltration is complete, allowing for a rapid response.
The Prosper data breach, affecting 17.6 million users, is added to the 'Have I Been Pwned' database.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats