Security Guides
Burger King Japan App Breach (About 11.18 Million Records): Names, Birth Dates and Phone Numbers Leaked — What Members Should Do
BK Japan says unauthorized access to the Burger King Japan app leaked about 11.18 million member records, including names, birth dates, phone numbers and emails. What leaked, what did not, and what to do today.
For: people registered with the official Burger King app in Japan, and anyone who runs a membership app. This article is based on the official notice from BK Japan Co., Ltd. and does not cover attack techniques.
Developing: this article will be updated as the organisation publishes more
As of October 17, 2026Not yet known
- How the access became possible and the detailed cause (under investigation with an outside specialist)
- Whether login password information leaked (no leak confirmed so far, the company says)
- How many people the 11.18 million records represent
- The sender and content of the notice emails to affected customers
- The specifics of the permanent fixes and recurrence-prevention measures
The notice does not say when a follow-up will be published. The company says it is continuing its investigation with an outside specialist organization and its permanent fixes. As of October 17, there was no follow-up on this incident in the news list on Burger King Japan's official site.
What app members should do today
Do not follow links or instructions in emails, texts or calls claiming to be Burger King
The leaked items include name (kanji and katakana), date of birth, phone number and email address. With all of that, a scammer can send a message with your correct name and birth date.
The company asks customers to watch for suspicious emails, texts and calls impersonating it or its services, and not to open URLs or attachments or enter member information or passwords. Whether the message offers, for example, "apology coupons", a "mobile order refund" or "re-registering your member details" (this site's examples), do not open the link; open the app yourself to check (see What is phishing?).
Check notice emails from the company in the app, not through their links
The company says it is emailing affected customers in turn. The notice does not give the sender address of those emails.
Sender names can be faked, so telling the genuine notice from a fake one by appearance is hard. Even if a notice email arrives, settle on one rule: do not log in or enter anything through a link in the email.
If you use your birth date as a PIN or password, change it
Unlike an email address or phone number, a birth date cannot be changed, and this time it leaked together with names.
If your bank or card PIN, phone screen lock or any password is based on your birth date (such as "0815" or "19900815"), change it now. This is this site's general advice, not the company's.
If you reuse the same password on other services, separate them
The company says no leak of login password information "has been confirmed so far". The notice does not ask members to change their passwords, but the wording reflects an investigation still in progress.
If you use the same password for the Burger King app and other services, separate them now. A password manager is the practical way to do it. To check whether a reused password appears in past leaks, see how to check if your password was leaked.
Stay alert to calls and texts from unknown numbers for a while
Phone numbers are hard to change. The leaked numbers may receive scam calls and texts for some time, including ones that do not mention Burger King at all.
Turning on your phone's spam call and text filters reduces how many reach you (see smartphone security basics).
Use only the contact points given in the notice
The company lists its customer service as the contact for customers (phone 0120-945-630, email customerservice@burgerking.co.jp, weekdays 10:00–17:00 Japan time, closed weekends and public holidays). Use the contacts in the notice on the official site, not those written in a message you received.
What happened (according to BK Japan)
BK Japan Co., Ltd. published its apology and notice on October 15, 2026. Everything below is based on that notice.
October 2 (Fri) – 7 (Wed), 2026
A third party accessed the system that manages official app member information without authorization (established by the later investigation).October 13 (Tue)
The investigation established that member information had leaked.October 15 (Thu)
Apology and notice published. The company said it had reported the incident to Japan's Personal Information Protection Commission.As of October 17
No follow-up published.
The company says it identified possible unauthorized access and investigated, and that after establishing the access had occurred it immediately blocked access from the source. The notice gives no date for either step, so how they relate to the dates above is not known.
- Service
- The official Burger King app in Japan (the system that manages member information)
- Scope
- About 11.18 million official app member records
- Leaked items
- Member ID, email address, registration type, prefecture, gender, date of birth, name (kanji and katakana), phone number, whether the member has a mobile order history, whether the email address has been verified
- Not included
- Credit card numbers (not held by the company, so not leaked)
- Not confirmed
- Leak of login password information (no leak confirmed so far)
- Cause (company's account)
- Confirmed as unauthorized access by a third party. How it became possible and the detailed cause are under investigation with an outside specialist organization
- Damage
- No secondary damage such as fraudulent use confirmed so far
- Done
- Blocked communication from the source of the access, put interim measures in place, set up a response headquarters, reported to the Personal Information Protection Commission
- Ongoing
- Permanent fixes, investigations with an outside specialist organization, emailing affected customers
- Contact
- Customer service (phone 0120-945-630, email customerservice@burgerking.co.jp, weekdays 10:00–17:00 Japan time, closed weekends and public holidays)
What is known and what is not
Status as of October 17, 2026. When a follow-up is published, the status column will be updated.
| Item | What the notice says | Status |
|---|---|---|
| Leak of member information | Confirmed that official app member information leaked | Leak confirmed (per the company) |
| Number of records | About 11.18 million official app member records (a record count, not a head count) | Stated by the company |
| Period of the access | October 2 to October 7 | Stated by the company |
| Name, birth date, gender, prefecture | Listed among the leaked items | Leak confirmed (per the company) |
| Email address, phone number, member ID | Listed among the leaked items | Leak confirmed (per the company) |
| Mobile orders | Whether a history exists is listed. Order contents are not listed | Leak confirmed (per the company) (existence only) |
| Credit card numbers | Not held by the company; not leaked | Not included (per the company) |
| Login password information | No leak confirmed so far | Not confirmed (per the company) |
| Address (beyond prefecture) | Not listed among the leaked items | Not stated |
| Cause and how it happened | Unauthorized access by a third party; details under investigation | Under investigation |
| Secondary damage | None confirmed so far | Not confirmed (per the company) |
| Contacting affected customers | By email, in turn. Sender not given | Not stated |
| Recurrence prevention | Strengthening security measures and monitoring. No specifics | Not stated |
How to read this: "not confirmed" does not mean "not leaked"
For credit card numbers, the company states flatly that it does not hold them and they did not leak. For login password information, it says only that no leak "has been confirmed so far", which reflects an investigation still in progress.
Likewise, "no secondary damage confirmed" means none has been found yet, not that the data will never be used. Birth dates and phone numbers stay the same for years, so keep watching for messages that use this incident as a pretext.
What the leaked combination makes possible
Each item is ordinary on its own, but together they help make scam messages look genuine. The following is what can generally happen, not a statement that it has happened in this case.
Name (kanji and katakana) + birth date + phone number
↓→
Fake calls that know your name and birth date, posing as an identity check
→ Do not treat what they know as proof / do not use your birth date as a PIN
Name + email address + whether the email is verified
↓→
Fake emails addressed to you by name, sent to an address known to be verified
→ Do not open links / check in the official app
Phone number + whether there is a mobile order history
↓→
Fake texts about an "order refund" or "payment check"
→ Do not enter card numbers or passwords / use a spam text filter
Not leaked or not confirmed, according to the notice
- Credit card numbers (the company does not hold them)
- Login password information (no leak confirmed so far)
Leaked (according to the company)
- Name (kanji and katakana), birth date, gender (a birth date cannot be changed)
- Phone number (hard to change)
- Email address and whether it is verified
- Member ID, registration type, prefecture
- Whether there is a mobile order history
A past case: a separate leak from the same app, announced in 2024
The company also announced a leak from the official Burger King app on October 22, 2024. In that notice, the member records confirmed as leaked totalled 38, and the data that may have leaked was email addresses, app passwords, and the brand and expiry date of registered credit cards. Information needed to use a card, such as card numbers and PINs, did not leak, the company said.
The timing, scale and items differ from this incident, and the October 2026 notice says nothing about any connection between the two. This case may not follow the same course. Whether or not you were affected in 2024, this is a good moment to check that you are not reusing your app password on other services.
For people who run a membership app
The company has not disclosed the detailed cause, so this section does not say how to prevent it, and it is not an assessment of the company's response. How to watch the number of member records read is covered in the Yakiniku King app case. Here we focus on one point the notice itself supports: data you do not hold cannot leak.
Not holding card numbers yourself works as protection
According to the company, it does not hold credit card numbers, so they did not leak. It is an example of a general principle: when a member system is breached, what is not in it cannot leak.
Your own service can be built the same way, leaving card numbers with the payment provider and keeping only the identifier (token) it returns. Note, though, that even without storing card numbers, card data can be stolen at the moment of entry if the payment page is tampered with (see the PhotoGoods case). Not holding the data and protecting the entry page are separate measures.
Review each member field by what it is used for
In general, sign-up fields tend to pile up for campaigns and analytics. List each field next to the feature that uses it, and stop asking for, or stop storing, fields with no use.
For example, if you hold birth dates only for birthday coupons, consider whether the birth month is enough. If the purpose is an age check, you can keep only the result of the check. Katakana names, gender and similar fields can be reviewed the same way.
Decide and publish the sender you will use for breach notices in advance
This notice does not give the sender address of the emails to affected customers. In general, fake apology emails spread quickly after an incident, and about the only clue members have for spotting the genuine notice is sender information published beforehand.
Before anything happens, decide the domain and sender address you will use for important member notices, publish them on your official site, and set up sender authentication (SPF, DKIM and DMARC). See stopping spoofed email with SPF, DKIM and DMARC.
Sources (public record)
The facts in this article are based on the following public information. We do not speculate on undisclosed intrusion routes or methods.
- BK Japan Co., Ltd., "Apology and notice regarding the leak of official app member information due to unauthorized access" (October 15, 2026, in Japanese) — burgerking.co.jp (PDF)
- Burger King Japan "News" list (checked October 17, 2026; no follow-up on this incident) — burgerking.co.jp
- BK Japan Co., Ltd., "Notice and apology regarding an information leak in the official Burger King app" (October 22, 2024, in Japanese; source for the past case) — Web Archive (PDF)
Update history
2026-10-17: First version, based on BK Japan's notice of October 15 and the news list on Burger King Japan's official site (checked October 17). The company says its investigation with an outside specialist organization is continuing; this article will be updated when a follow-up is published.
Read next
- Protecting yourself from follow-on scams: What is phishing? / Smartphone security basics
- Passwords: Choosing a password manager / How to check if your password was leaked
- Similar cases (membership apps): Yakiniku King app unauthorized access / MrMax app and online store breach
- Other incidents in 2026: List of data breaches and cyberattacks (Japan and worldwide)
FAQ
QWhat was leaked in the Burger King Japan app breach?
According to BK Japan Co., Ltd.'s notice of October 15, 2026, about 11.18 million official app member records leaked. The items are member ID, email address, registration type, prefecture, gender, date of birth, name (kanji and katakana), phone number, whether the member has a mobile order history, and whether the email address has been verified. For mobile orders, the item listed is only whether a history exists, not what was ordered.
QAm I affected?
The notice says the information of 'official app members' leaked, about 11.18 million records in total. It gives no condition, such as a sign-up period, that would limit this to some members. The company says it is emailing affected customers in turn; even before an email arrives, it is safest to act as affected if you are an app member. Note that 11.18 million is a count of member records, not necessarily of people.
QAre my password and credit card safe?
The company says it does not hold credit card numbers, so they did not leak. For login password information, it says no leak 'has been confirmed so far', wording that reflects an investigation still in progress. The notice does not ask members to change their passwords. If you use the same password on other services, this is a good moment to separate them.
QWhat caused the breach?
The company says it has confirmed that the cause was unauthorized access by a third party. How that access became possible and the detailed cause are being investigated with an outside specialist organization and had not been disclosed as of October 17.
QWhat if I get an email or text claiming to be Burger King?
The company asks customers to watch for suspicious emails, text messages and calls impersonating it or its services, and not to open URLs or attachments or enter member information or passwords. A message that has your correct name and birth date is not proof that it is genuine. Check in the official app or site you open yourself.
QMy date of birth leaked. Is there anything I should do about that?
A birth date cannot be changed, so it stays useful to a scammer for a long time. This site recommends changing any bank or card PIN, phone screen lock or password that is based on your birth date. And when a caller asks you to 'confirm your identity' by giving your birth date, remember that a caller who already knows your name and birth date is not necessarily genuine.