MyRecon OSINTBurger King Russia
Behind the exposed accounts
In October 2024, news of a data breach exposing Burger King Russia customers broke following an August attack on the Mindbox marketing automation platform.
Follow the story
On 25 August 2024, Burger King Russia was breached. 3,155,792 accounts were exposed, including dates of birth, email addresses, genders. MyRecon rates it 61/100, severe. That is about 12% of the population of Australia.
How the story unfolded
Open a step to read the detail. Missing dates stay unknown.
02Entry point
The published account does not explain the exact way the data was obtained.
03Discovery and disclosure
A separate discovery or company-disclosure date is not established by this feed record.
04Added to the breach catalogue
2026-09-21. This is the catalogue date, not necessarily the disclosure date.
05Reported outcome
3,155,792 accounts are listed in this breach. This is a count of accounts, not necessarily individual people. The reported exposed data includes Dates of birth, Email addresses, Genders, Geographic locations, Names, Phone numbers.
The important boundary in this record is a marketing platform. Have I Been Pwned attributes the customer-data exposure to an attack on Mindbox and describes records spanning 2018 to August 2024. A person can appear in an old marketing dataset even if they no longer use the restaurant's account or app. The addition date in a breach index is also different from the date the incident occurred.
The source lists names, contact details, birthdays and approximate location, and reports the company's statement that payment and passport details were not included. That statement should not be expanded into either a guarantee that no other risk exists or a claim that cards were stolen. The listed fields can help make a fake loyalty reward or account-support message sound personal. This is a risk interpretation, not a report of an observed follow-on scam.
If you receive an unexpected reward or account message, open the official app or a known website yourself. A correct name or birthday does not authenticate the sender. Do not send a one-time code in reply or enter payment details through the message. Report suspicious communication using the service's official support channel and your normal email or device reporting controls.
For a company reviewing its own exposure, this case illustrates why account deletion and marketing-data retention need separate questions. Ask which provider holds historical contact records, what the retention policy covers and how a deletion request propagates to that provider. These are review questions, not a claim about the current Mindbox configuration. The available description does not give the exact intrusion mechanism, so this article leaves that cause unresolved.
The story behind the breach
In October 2024, news of a data breach exposing Burger King Russia customers broke following an August attack on the Mindbox marketing automation platform. The breach exposed 3.2M unique email addresses along with names, genders, dates of birth, phone numbers and approximate geolocations, with the data spanning 2018 to August 2024. Burger King Russia acknowledged the incident and advised it did not include payment or passport details.
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,155,792 accounts are listed in this breach. This is a count of accounts, not necessarily individual people.
The reported exposed data includes Dates of birth, Email addresses, Genders, Geographic locations, Names, Phone numbers.
What was exposed, and why it matters
Dates of birth
One of the three things call centres ask to verify identity, and it never changes.
Email addresses
The address becomes a confirmed, active target, expect more phishing, better aimed.
Genders
Small on its own; useful to anyone assembling a fuller profile.
Geographic locations
Where the account was used, which narrows a person down further than most people expect.
Names
Turns an anonymous address into an identified person, which is what makes targeted phishing possible.
Phone numbers
Enables SIM-swap attacks against SMS two-factor codes, and puts the number on scam-call lists indefinitely.
What to do if you were in it
Questions people ask about this breach
Was my email address in the Burger King Russia 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 Burger King Russia breach?
dates of birth, email addresses, genders, geographic locations, names, phone numbers. 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 25 August 2024. It was published to Have I Been Pwned on 21 September 2026, a gap of 758 days during which the data was already out.
Is the Burger King Russia 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,155,792 accounts. That is about 12% 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.