2023 · Data breach

PlayCyberGames

Breached 9 August 2023 · Published 31 August 2023 · playcybergames.com

THE HUMAN IMPACT

Behind the exposed accounts

In August 2023, PlayCyberGames which "allows users to play any games with LAN function or games using IP address" suffered a data breach which exposed 3.7M customer records.

Follow the story
A person using a laptop beside a desktop monitor
Logan Jeffrey / Unsplash · Personal research · context photograph, not an affected user
3,681,753Accounts exposed
65/100Severe severity
3Types of data
VerifiedBy HIBP

On 9 August 2023, PlayCyberGames was breached. 3,681,753 accounts were exposed, including email addresses, passwords, usernames. MyRecon rates it 65/100, severe. That is about 14% of the population of Australia.

FOLLOW THE RECORD

How the story unfolded

Open a step to read the detail. Missing dates stay unknown.

  1. 01Reported breach date

    2023-08-09

    Read the HIBP source record

  2. 02Entry point

    The published account does not explain the exact way the data was obtained.

    Read the HIBP source record

  3. 03Discovery and disclosure

    A separate discovery or company-disclosure date is not established by this feed record.

    Read the HIBP source record

  4. 04Added to the breach catalogue

    2023-08-31. This is the catalogue date, not necessarily the disclosure date.

    Read the HIBP source record

  5. 05Reported outcome

    3,681,753 accounts are listed in this breach. This is a count of accounts, not necessarily individual people. The reported exposed data includes Email addresses, Passwords, Usernames.

    Read the HIBP source record

Were you part of this breach?

Only a result for this incident is shown. On submission, your email is sent through MyRecon to XposedOrNot for a breach lookup. MyRecon does not save this check to your history. Provider coverage can be incomplete.

The detail that matters is six words long: MD5 hashes with a constant value in the salt field. A salt that never changes is not a salt. Its entire function is to be different for every record, so that two people who chose the same password do not produce the same hash and one precomputed table cannot be run against the whole file. Fix the value and you have plain MD5 with extra steps.

What makes this instructive rather than merely bad is that it passes inspection. The column exists. The field is populated. The word "salt" appears in the schema, in the code, and presumably in whatever security questionnaire the company answered. Everything is present except the property that made any of it worth doing, which is a far more common shape of failure than having no protection at all.

The last line of the record is the one with consequences for readers: multiple attempts to disclose the breach went unanswered. No reset emails were sent, no notice was published, and 3.7 million people were never told by the company that lost their credentials. If a password from a gaming account of yours is still in use somewhere else, this is the only notification you are going to get.

The story behind the breach

In August 2023, PlayCyberGames which "allows users to play any games with LAN function or games using IP address" suffered a data breach which exposed 3.7M customer records. The data included email addresses, usernames and MD5 password hashes with a constant value in the "salt" field. PlayCyberGames did not respond to multiple attempts to disclose the breach.

Breach description from Have I Been Pwned, used under a CC BY 4.0 licence.

How did it happen?

The published account does not explain the exact way the data was obtained.

What was the motive?

The published account does not establish the motive. We cannot tell what the attackers intended from the exposed data alone.

Reported demands or attempts to sell data describe what happened, rather than prove every attacker's intention.

What was the outcome?

3,681,753 accounts are listed in this breach. This is a count of accounts, not necessarily individual people.

The reported exposed data includes Email addresses, Passwords, Usernames.

What was exposed, and why it matters

Email addresses

The address becomes a confirmed, active target, expect more phishing, better aimed.

Passwords

Anyone reusing this password elsewhere has those accounts exposed too, credential stuffing is automated and tries them all within days.

Usernames

A handle links this account to every other place the same handle is used.

What to do if you were in it

Your next steps

Tick off the actions you have taken. Progress lasts while this page is open.

0 actions completed

Questions people ask about this breach

Was my email address in the PlayCyberGames breach?

Use the email box on this page. The result applies only to this incident. If the provider does not cover this breach, we say so. A missing match does not prove you were unaffected.

What data was leaked in the PlayCyberGames breach?

email addresses, passwords, usernames. Each one is explained above, along with what it means for the person it belongs to.

When did it happen, and when did it become public?

The breach is dated 9 August 2023. It was published to Have I Been Pwned on 31 August 2023, a gap of 22 days during which the data was already out.

Is the PlayCyberGames breach real?

Yes. Have I Been Pwned lists it as verified, meaning the data was checked against the source rather than taken on trust.

How many people were affected?

3,681,753 accounts. That is about 14% of the population of Australia. That is accounts rather than people, one person often has several.

Read next

Also in the archive

Case Files: how the landmark breaches actually happened →

Three kinds of content appear on this page and they are kept apart deliberately. The breach description is quoted from Have I Been Pwned under its licence. The severity score, the field-by-field explanation and the advice are computed from the record itself, every sentence derives from a number or a flag in it, which is what stops the analysis drifting from the evidence. Anything under the "MyRecon's take" byline is editorial: our reading of this breach, presented as opinion rather than as a finding.

← All breaches