devkitPro
HIGH RISKData breach — February 2019
In February 2019, the devkitPro forum suffered a data breach. The phpBB based forum had 1,508 unique email addresses exposed in the breach alongside forum posts, private messages and passwords stored as weak salted hashes. The data breach was self-submitted to HIBP by the forum operator.
search Check if you were affected — freeData exposed in this breach
What happened in the devkitPro data breach?
In February 2019, the devkitPro forum suffered a data breach. The phpBB based forum had 1,508 unique email addresses exposed in the breach alongside forum posts, private messages and passwords stored as weak salted hashes. The data breach was self-submitted to HIBP by the forum operator.
The exposed data included 3 types of personal information. Because passwords were exposed, users who reused their password on other sites are at particular risk. Learn more about what a data breach means for you.
Quick answer — was devkitPro hacked?
Yes. devkitPro was breached in February 2019. The breach exposed 1,508 records including email addresses, passwords, private messages. This breach has been independently verified. If your email was involved, your data may still be at risk today. Check if you were affected.
Why was the devkitPro breach so dangerous?
The devkitPro breach exposed 1,508 records — that is a large number of compromised accounts. The combination of email addresses, passwords, private messages makes this a high-risk breach that requires immediate action.
Because passwords were exposed, attackers can use credential stuffing to automatically test your devkitPro password against hundreds of other websites. If you reused your password anywhere, those accounts are now at risk. Read more about what happens to your data after a breach.
Don't wait to find out — check if your email was exposed in this breach now.
What data was stolen in the devkitPro breach?
Email addresses — used for phishing attacks and credential stuffing against your other accounts
Passwords — can be used to access your accounts directly or cracked to reveal your actual password
Private messages — may be combined with other breach data to build a profile for targeted attacks
Is the devkitPro breach still dangerous in 2026?
Yes. Stolen data from the devkitPro breach remains dangerous years after the incident. Research shows that over 65% of stolen credentials from older breaches have never been changed by the account holders. Attackers routinely compile data from multiple breaches to build complete profiles, and credentials from 2019 are still actively used in credential stuffing attacks today.
Personal information like email addresses, phone numbers, and dates of birth never expire. Even if you changed your devkitPro password, the other exposed data can be combined with information from other breaches to target you. Learn more about how long stolen data stays dangerous.
Frequently asked about the devkitPro breach
Approximately 1,508 user records were exposed in the devkitPro breach in February 2019.
Yes. Leaked credentials are actively used in credential stuffing attacks years after a breach. If you reused your devkitPro password elsewhere and haven't changed it, those accounts remain at risk today.
Enter your email in the free checker on EmailLeaked. We scan 12 billion+ breach records including the full devkitPro dataset and tell you instantly whether your email was exposed and what data was taken.
Change your devkitPro password immediately, change any other account where you used the same password, enable two-factor authentication on all important accounts, and monitor for phishing emails over the next 90 days.
Who was affected by the devkitPro breach?
The devkitPro data breach affected approximately 1,508 users who had accounts with the service. While not the largest breach on record, it still represents a significant number of compromised accounts in our database of 970+ known breaches.
If you ever created an account with devkitPro or used their services, your data may have been included in this breach. Check your email now to find out. You can also read our guide on what to do immediately after a data breach.
If your email was in the devkitPro breach
Change your devkitPro password immediately
Go to devkitPro and change your password right now. Use a strong, unique password that you have never used anywhere else.
Change any account sharing that password
If you used the same password on other sites, change it on every one of them. Attackers test stolen credentials on hundreds of popular sites within hours.
Enable two-factor authentication
Turn on 2FA on devkitPro and every important account. Even if your password is known, attackers cannot get in without the second factor.
Check your other accounts for this breach
Run a full email check to see every breach your email appears in — not just this one.
searchCheck all my breaches — freeOther major breaches
Was my email hacked?
Check if your email is compromised in seconds. Free, private, no signup. Scan 12 billion+ records across 970+ known breaches.
search Check my email now — it's freeNo signup required · Results in under 5 seconds · Your data is never stored