Udemy
1.4 million users and instructors. Email addresses, names, and financial payout information—PayPal accounts, bank transfers, check details. The data that pays content creators is now in attacker hands.
What happened?
On April 24, 2026, ShinyHunters posted a "Pay or Leak" warning on their data leak site, claiming to have compromised Udemy's Salesforce environment and stolen 2.3GB of data containing over 1.4 million records. They gave Udemy until April 27 to respond. When the deadline passed without payment, ShinyHunters released the full dataset.
What data was actually inside?
1.4 million unique email addresses of customers and instructors. Names. Physical addresses. Phone numbers. Employer information. And critically: instructor payout methods—PayPal account details, bank transfer information, and check payment records.
Udemy isn't just a learning platform. It's a marketplace where instructors earn money from course sales. The payout data reveals how thousands of content creators receive their income. That's financial targeting information—the kind that enables wire fraud, account takeover, and payment redirection attacks.
Who gets hurt and how?
Two groups: students and instructors. Students face the usual credential stuffing and phishing risks. But instructors face something more specific: attackers now know how they get paid. PayPal accounts can be targeted for takeover. Bank transfer details enable payment redirection fraud. Check recipients can expect convincing phishing attempts.
Udemy has over 70 million students and 75,000 instructors. Even if the breach only captured a fraction of that user base, 1.4 million records represents a significant portion of active, paying customers and revenue-generating creators.
What did they think they were doing right?
Running a successful online learning marketplace. Udemy processes millions of transactions, manages instructor payouts across multiple payment methods, and serves learners in 180+ countries. That scale requires enterprise infrastructure—CRM systems to manage relationships, payment systems to handle disbursements, support systems to handle inquiries.
ShinyHunters claimed the data came from Salesforce. The same attack pattern they've used against 7-Eleven, Zara, and dozens of other organizations. Udemy likely believed their Salesforce instance was a secure place to manage instructor relationships and payment information. It was—until it wasn't.
What did they not know about their own data?
Udemy has not made an official statement about the breach or what data was exposed. That silence is telling. Either they're still determining the scope, or they're hoping the story fades without public acknowledgment.
But Have I Been Pwned has already indexed the data. 1.4 million email addresses are now searchable. The question isn't whether the breach happened—it's whether Udemy knew that instructor payment methods were stored alongside contact information in a system accessible through a single Salesforce compromise.
If you use Salesforce, you probably have the same data types—emails, names, addresses, phone numbers. Do you know which fields contain PII?
What does attribution look like the morning after?
ShinyHunters has made education a priority target. They previously breached India's Unacademy platform, stealing over 10 million user accounts. In 2026, they've hit McGraw-Hill, Harvard University, and now Udemy. The education sector's combination of large user bases, payment data, and historically underfunded security makes it attractive.
For Udemy, the breach creates a trust problem with instructors—the people who generate the platform's content and revenue. If creators don't trust that their payout information is secure, they may move to competing platforms. The breach cost isn't just notification letters; it's potential instructor attrition.
What would have changed the outcome?
Knowing that instructor payout data—PayPal accounts, bank details—was accessible from the same environment as contact information.
Payment methods are some of the most sensitive data a platform holds. They should be compartmentalized, access-controlled, and audited separately from general CRM data. The question is whether anyone at Udemy had mapped which Salesforce objects contained financial information and who could access them.
ShinyHunters got everything in one breach: contact info, employer data, payment methods. A single Salesforce compromise shouldn't expose the full range of sensitive data a platform holds. Unless nobody knew it was all in the same place.
Udemy found out the hard way.
Your team could spend the next 6 months rebuilding systems, notifying customers, and answering legal questions. Or you could spend 24 hours finding out what's actually at risk.