Data breaches → Divine Skins
Was your data in the Divine Skins breach?
2026 · divineskins.gg · ~105,814 accounts exposedLow severity · 3/10
Divine Skins (divineskins.gg) suffered a data breach in 2026 that exposed around 105,814 accounts. If you had an account, some of your personal data may be circulating in leaked databases. The fastest way to know is to check your own email — free, in about 30 seconds, no password required.
What happened
In March 2026, the League of Legends custom skins service Divine Skins suffered a data breach. The incident was disclosed via the service's Discord server, where Divine Skins stated that an unauthorised third party accessed part of its systems, deleted all skins from the database and exposed email addresses and usernames. The data also contained a history of purchases made by users.
Breach details sourced from Have I Been Pwned, the industry-standard breach database. Risk analysis by Nullivo.
What was exposed, and why it matters
Not all breaches carry the same risk — what matters is which fields leaked. Here is what the Divine Skins breach exposed and what each item actually enables:
Links this leak to your other accounts — a reused username lets anyone build a profile of you across platforms.
Puts you on spam and phishing lists, and confirms to attackers that you hold an account with this service — which makes impersonation emails more believable.
Also listed in this breach: Email addresses, Purchases, Usernames.
What to do if you were affected
These steps are ordered for this specific breach — the most urgent action given what leaked comes first.
- Names and usernames: Search your usual username to see what else it exposes, and use distinct handles for sensitive accounts.
- Email addresses: Treat any message referencing this service with suspicion, and never act on links in unexpected emails.
- Check whether your own email appears in this breach — run a free scan to confirm before you spend time on the steps above.
How urgent is this now?
This breach is recent, so the data is actively traded and the risk is at its highest right now.
Remember: a breach can't be "un-leaked" — once a database is out, it exists in countless copies. The goal is to make the leaked data useless: change what can be changed, lock down what can't, and remove what has been republished.
Frequently asked questions
What data was exposed in the Divine Skins breach?
The Divine Skins breach exposed names and usernames, email addresses. Links this leak to your other accounts — a reused username lets anyone build a profile of you across platforms.
How many people were affected by the Divine Skins breach?
Around 105,814 accounts were exposed, making it a mid-sized breach.
What should I do if I had a Divine Skins account?
Search your usual username to see what else it exposes, and use distinct handles for sensitive accounts. You can check whether your own email appears in this breach with a free Nullivo scan — no password required.
Breaches that exposed similar data
If the Divine Skins breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.
- Was your data in the University of Nottingham breach? (2026, ~454,635 accounts)
- Was your data in the AnimeLeague breach? (2024, ~192,134 accounts)
- Was your data in the SuperDraft breach? (2024, ~300,187 accounts)
- Was your data in the E-Pal breach? (2022, ~108,887 accounts)
- Was your data in the Spytech breach? (2024, ~5,645 accounts)
- Was your data in the Fantasy Football Hub breach? (2021, ~66,479 accounts)