Lawson confirmed on Thursday that attackers reached its Lawson ID and app reservation systems on Sep 12-14, exposing 2,155,345 member records: names, date of birth (which may have leaked), and gender, phone numbers, and addresses where entered. Email addresses were first listed among the leaked fields, but Lawson's 24 October update states further investigation found email addresses and newsletter acquisition information were not leaked. Partial credit card numbers appeared only in a separate set of 26 Lawson App Reservations records. I run AliasFleet, an email-alias service: one forwarding address per site, so a leak names its source. Lawson is now contacting victims individually, and impersonation attempts using the leaked names, phone numbers, and addresses are the risk to watch.
What Lawson confirmed#
The disclosure came on 8 October, reported by TV Asahi, Kyoto Shimbun, Sankei and Reuters. The honest split:
| Confirmed | Still unconfirmed |
|---|---|
| The disclosure: Lawson announced the breach itself on 8 October | The attack vector into the Lawson ID and app reservation systems |
| The window: unauthorised access September 12-14, 2026; found October 7 during a routine investigation by Lawson's system division | Which parts of the card numbers in the 26-record App Reservations set were exposed ("partial" is all Lawson has said) |
| About 2,155,345 Lawson ID records, plus a separate set of 26 Lawson App Reservations records | Whether the dataset has surfaced publicly or been traded |
| Data (Lawson ID set, as corrected 24 October): names, date of birth (may have leaked), and gender, phone numbers, and addresses where entered. Email addresses and newsletter acquisition information were initially listed but found not to have leaked. Partial credit card numbers appeared only in the separate 26-record App Reservations set | Whether any other Lawson systems were touched |
| The app reservation function has been suspended | Whether more records will be added as the investigation continues |
| Lawson will contact affected people individually by email | The exact timeline of when the stolen data moved, if it has moved |
| No confirmed misuse or secondary harm as of disclosure (Reuters) |
The card detail matters, and it is narrower than first reported. Partial credit card numbers were not part of the 2.15 million Lawson ID records; they appeared only in the separate 26-record Lawson App Reservations set. "Partial" is vague on purpose: it can mean the last four digits, which are useless for purchases but perfect for sounding legitimate in a scam call ("I see your card ending in 4821..."). Lawson has not said which digits. Do not assume the harmless interpretation.
「多大なる迷惑をおかけし深くおわびする」
"We sincerely apologise for the great trouble caused," Lawson's statement, as quoted by Sankei and Kyoto Shimbun.
The notification email is now the weapon#
Lawson is contacting victims individually. The leaked set contains no email addresses, so the forgery picture changes: attackers holding names, phone numbers, and postal addresses are better placed to impersonate Lawson by SMS, phone calls, and post than by email built from this leak alone. Forged emails remain possible using addresses gathered elsewhere, but this leak does not hand attackers the victim email list.
Lawson already had an email problem before this breach. On October 1 the company disclosed that its mail server had been misused to send about 700,000 English spam emails between September 25 and 27, with subjects like "Mutual Benefit" and "RE" (ASCII via Yahoo News). That incident leaked no personal data, and it is a separate event from this breach. But it means Lawson's own warning now applies to its own brand: the company told people then that sender addresses can be faked and that unexpected mail should be deleted. That advice now applies to the breach notification too.
So here is the shape of the next two weeks. Real notifications go out. Impersonation attempts follow beside them, quoting real details, by SMS, calls, and post, and possibly by email too, asking for the rest of the card number, the full address, a password reset. Victims cannot tell the real from the forged by content, because the content is near identical. The only test that works is the channel: Lawson's app, Lawson's own site, typed by you.
A genuine Lawson notification is plausible, and forged ones are possible. The message that quotes the real apology and links to a "breach confirmation page" asking for your card details is not from Lawson. Open the Lawson app or type lawson.co.jp into your browser. No link in any email about this breach is worth clicking, including the real one.
What Lawson members should do now#
- Assume your Lawson ID record is exposed: name, date of birth (which may have leaked), gender, phone number, and address where entered. That is an identity record, not a loyalty account. Treat it accordingly. Email addresses were not in the leaked set, and partial card numbers appeared only in the separate 26-record reservations set.
- If you used Lawson app reservations, watch your card statements, and call your card issuer. "Partial" card numbers in that small set, leaked alongside names, addresses, and phone numbers, are enough for social engineering against the issuer. Ask whether a replacement card makes sense after this exposure.
- Do not click any link in any email about this breach. Open the app or type the URL yourself. This applies to the real notification too: a habit that works against the forgeries must work against the genuine ones.
- Do not reuse your Lawson password anywhere else, and if it matches another site's, change it there now. Passwords were not among the leaked fields in this breach, so this leak adds no new password to the pile, but reuse is still the risk that turns one leak into many.
- Expect SMS and calls that "confirm your identity" with your own details. Your name, address and phone number are the leaked fields. Anyone reading them back to you is proving they have the file, not that they are Lawson.
- Check Have I Been Pwned once the incident is listed, and walk the breach-response order of operations.
One address per loyalty programme#
A dedicated alias for Lawson would not have traced this leak, because no email addresses leaked at all. The alias point here is prospective, not retrospective: had addresses leaked, a Lawson-only alias would have marked every message on it as either from Lawson or from the attacker, with no third option, and a "breach notification" on that address asking for card details would have identified itself as the forgery. Kill the alias and the whole channel dies while your real inbox stays clean. That is the leak-tracing mechanism aimed at exactly this attack, and it applies to the next loyalty-programme leak, not this one. The set-up guide takes about two minutes.
Loyalty programmes are the inbox nobody thinks to protect. You sign up for the coupon, the app sits on your phone for years, and it quietly becomes a payment-adjacent identity record holding your name, your address, your phone, and possibly your date of birth. The same morning brought Daiichi Kosho's disclosure of 8.72 million karaoke member records: the loyalty signup is the breach vector of the season.
What to watch in the Lawson investigation#
Three things. First, the card detail: which digits leaked in the 26-record reservations set, and whether any issuer reports fraud tied to them. Second, whether the dataset surfaces publicly, which turns a contained intrusion into a circulating one. Third, the impersonation wave itself: if forged Lawson messages land at scale by SMS, calls, and post, they will be the first large-scale test of whether breach impersonation can be told apart from the real thing by content. It cannot be. The channel is the test. The investigation continues. So does the impersonation.
