
Key takeaways
- PayPal notified about 100 Working Capital customers in February 2026 after a code error exposed Social Security numbers and other PII for nearly six months.
- The exposure ran from July 1 to December 13, 2025, and PayPal says its systems were not breached, only a faulty code path inside one application.
- This is PayPal's second major incident since 2022, when a similar SSN-masking failure led to a $2 million NYDFS settlement in January 2025.
- Two separate phishing campaigns abused PayPal's own infrastructure in late 2025, showing attackers probe the platform continuously, not only during active breaches.
- Both incidents share a root cause: a monitoring lapse of who or what could actually reach sensitive customer data before it was too late.
PayPal's data breaches are a pattern of internal control failures, not isolated hacks. A 2022 error in how PayPal generated Form 1099-K and a 2026 code change in the PayPal Working Capital (PPWC) loan application both exposed Social Security numbers because no one was watching who, or what, could reach that field of data. NYDFS fined PayPal $2 million under 23 NYCRR Part 500 over the first incident. The second exposed roughly 100 customers' personal information for nearly six months before PayPal caught it.
Quick facts: PayPal's two data breaches
| Aspect | 2022 incident (1099-K SSN masking) | 2026 incident (PayPal Working Capital) |
|---|---|---|
| Disclosed | January 2023 (PayPal notification letters); January 2025 (NYDFS settlement) | February 10, 2026 (notification letters) |
| Exposure window | About 1.5 months between the error and its exploitation | July 1 to December 13, 2025 (about six months) |
| Data exposed | Name, date of birth, address, unmasked Social Security number | Name, email, phone, business address, Social Security number, date of birth |
| Customers affected | 34,942 accounts | About 100 |
| Root cause | Unmasked SSNs on downloadable 1099-K forms | A code change in the PPWC loan application |
| Outcome | $2 million NYDFS fine; 23 NYCRR Part 500 violation | Refunds, password resets, two years of Equifax credit monitoring |
What happened in PayPal's 2026 Working Capital data breach?
A software change to PayPal Working Capital (PPWC), PayPal's lending product for small business sellers, opened an access path to customer records that should never have been reachable from the application's front end. The flaw was live from July 1, 2025 until PayPal caught it on December 12, 2025, almost six months later.
PayPal rolled back the code change and cut off the unauthorized access the next day, December 13. Notification letters to affected customers are dated February 10, 2026, and PayPal's own filing with Massachusetts regulators lays out the same timeline, start to finish.
What data was exposed, and how many customers were affected?
PayPal's notification lists the exposed fields exactly: name, email address, phone number, business address, Social Security number, and date of birth. About 100 customers were affected, and a small number saw unauthorized transactions on their accounts, which PayPal refunded.
It is worth separating this PayPal data leak from a hack in the usual sense. PayPal has been explicit that this was an internal application error, not a network intrusion or a third party losing PayPal's data. That distinction matters for how you read the rest of this timeline: the vulnerability sat inside PayPal's own code, reachable to anyone who knew where to look, for five and a half months before anyone noticed.
PayPal's response: Password resets, refunds, and credit monitoring
PayPal's remediation followed the standard breach playbook: force password resets on affected accounts, refund the unauthorized transactions, and offer two years of Equifax credit monitoring and identity restoration.
Where the response gets less clean is the messaging. PayPal's public statement said its systems "were not compromised," while the breach notification itself says PayPal "terminated the unauthorized access to PayPal's systems." Both can be technically true, since the application was not hacked from outside and unauthorized access still had to be cut off, but the two statements read very differently depending on which one a customer sees first, a tension Forbes flagged directly.
The 2022 credential-stuffing breach and $2 million NYDFS settlement
PayPal's first major incident traces back to a 2022 change in IRS reporting rules that required PayPal to issue Form 1099-K to far more sellers than before. The form carries a Social Security number: the copy the IRS receives should show it in full, and the copy a user downloads should show only the last four digits. An implementation error meant some users could download a version with the full, unmasked number instead.
The New York State Department of Financial Services (NYDFS) found that this gap sat open for about 1.5 months before attackers found it, and that PayPal's thin login defenses, including a lack of mandatory multi-factor authentication, made it easy to exploit once they did. On January 23, 2025, NYDFS fined PayPal $2 million and found the company in violation of 23 NYCRR Part 500, New York's cybersecurity regulation for financial services firms, under the terms of its consent order.
What was the impact?
Threat actors exploited this vulnerability through credential stuffing, using stolen passwords reused across multiple sites to gain unauthorized access. Their objective was downloading users' 1099-K forms to obtain SSNs for identity theft activities, such as fraudulently opening credit cards. The situation was made worse by thin security controls, including a "lack of robust multi-factor authentication (MFA) or CAPTCHA systems for customer logins," which made account compromise far easier for attackers.
A pattern, not an isolated incident
The Working Capital breach is not PayPal's only security story from the back half of 2025. In December, researchers reported that scammers had found a way to abuse PayPal's own subscriptions feature: set up a fake subscription, cancel it to trigger a real "payment no longer active" email from PayPal's own servers, then route that email through a mailing list to attach a fabricated invoice and a fraudulent support number. Because the email genuinely came from paypal.com, it passed filters that would normally catch a spoofed sender. PayPal closed the loophole after it was reported.
Two months earlier, PayPal had warned users about a wave of "do not pay, do not phone" attacks, a telephone-oriented attack delivery (TOAD) scheme where a real PayPal invoice email for a purchase the recipient never made pushes them to call a number that connects to a scammer posing as support. None of these incidents share a root cause in the technical sense, but together with the two data breaches, they add up to more than bad luck. These PayPal security breaches and scams point to a gap in how continuously the company can see what its own systems, and the data moving through them, are actually doing.
How Bedrock Data could have helped
The 2022 and 2026 incidents have different root causes, an unmasked field on a tax form versus a code change that opened a new access path, but the same blind spot let both run for months. Neither required a sophisticated attacker. Both required nobody watching who, or what, could reach a specific field of sensitive data in production.
That is the gap Bedrock Data's Full-Context Entitlement Analysis is built to close. It maps the complete access chain for every identity, human and non-human, resolves nested groups and federated identity data, and ranks identities by how much sensitive data they can actually reach. In both cases, a new identity or application path reaching a store of unmasked SSNs would show up on the next scheduled scan of that source, not months later.
Feeding those findings into Bedrock Data's Metadata Lake keeps a running, queryable record of who can reach what, so a policy change or a new access path shows up as a deviation from baseline instead of disappearing into application logs nobody reviews until a breach notification is already being drafted. Pairing that visibility with ongoing access reviews and least-privilege enforcement keeps the access itself narrow, not just visible.
The same entitlement logic extends to AI agents now touching financial workflows. For agents that call tools through the AWS AgentCore MCP Gateway, Bedrock Data's Agent DLP inspects each call in real time and can block or redact an unmasked SSN before the agent returns it.
Reducing risk and brand damage
Across both incidents, PayPal is now carrying the cost of a $2 million regulatory fine and a second multi-month breach on top of the engineering time spent on remediation and the renewed scrutiny from regulators and the press. The 1.5-month gap between the 2022 error and its exploitation, and the nearly six-month gap in the 2026 incident, are both windows that continuous monitoring could have closed early.
The lesson compounds with each repeat incident. The cost of not knowing who can reach sensitive data does not stay flat; it grows with every incident a company absorbs.
What should affected PayPal users do?
If you received a PayPal breach notification letter, or you use PayPal Working Capital and have not seen one yet, a few steps can limit the damage:
- Change your PayPal password, and do not reuse it on any other site.
- Turn on multi-factor authentication, or switch to a passkey if PayPal offers one for your account.
- Review recent PayPal statements and your bank or card statements for charges you do not recognize.
- Check your credit report for new accounts you did not open, and consider a fraud alert or a credit freeze with the major credit bureaus.
- Enroll in the Equifax credit monitoring PayPal is offering before the enrollment window closes, if you are eligible.
See how Bedrock Data surfaces this kind of exposure
Both of PayPal's breaches ran for months because nobody had a live view of who and what could reach sensitive records. See how Bedrock Data's Post-Breach Forensics and Regulatory Compliance and Audit Automation solutions catch this kind of exposure before it becomes a notification letter. Schedule a demo to see it against your own environment.
FAQs
What happened in the PayPal data breach?
PayPal disclosed two separate incidents. In 2022, an error in how PayPal generated Form 1099-K let some users download a version showing an unmasked Social Security number, which NYDFS fined PayPal $2 million over in January 2025. In 2026, a code change in the PayPal Working Capital loan application exposed customer PII, including Social Security numbers, for almost six months before PayPal caught it in December 2025.
How many people were affected by the 2026 PayPal Working Capital breach?
PayPal's notification describes about 100 affected customers. A small number of those accounts saw unauthorized transactions, which PayPal refunded. PayPal's January 2023 notification put the 2022 incident at 34,942 accounts; the NYDFS consent order describes it as affecting tens of thousands of consumers.
Is this the same as PayPal's 2022 data breach?
No. The 2022 incident involved unmasked Social Security numbers on downloadable 1099-K tax forms and ended in a $2 million NYDFS settlement. The 2026 incident involved a separate code error in the PayPal Working Capital loan application that exposed a different set of customer records between July and December 2025. The two share a cause: undetected internal errors, not a connected technical flaw.
What should I do if I received a PayPal breach notification?
Change your PayPal password, enable multi-factor authentication, and review your account and bank statements for unauthorized charges. Enroll in the free Equifax credit monitoring PayPal is offering, and consider placing a fraud alert or credit freeze with the major credit bureaus. Keep the notification letter; you may need it to document the incident for your bank or insurer.
Has PayPal had other data breaches?
Not that PayPal has disclosed. Beyond the 2022 and 2026 incidents, scammers abused legitimate PayPal features in two 2025 phishing campaigns, but neither exposed PayPal-held customer data.
