Incidents & Vulnerabilities

7pay fraud (2019): the disclosed cause assessment and account protections

7pay’s 2019 incident: the operator’s cause assessment, dated loss figures, and lessons for authentication, recovery and payment alerts.

Published 2026-07-07 Updated 2026-10-18 7 min read
On this page

This article distinguishes the operator's public explanation from this site's general defensive recommendations. It does not reconstruct an attack or infer a cause from a suggested control.

~¥38.6M
Unauthorized top-ups and use; July 31, 17:00
808
People recognized as affected; July 31, 17:00
~3 months
From launch to service closure
2FA
Additional authentication was insufficiently considered, the company said
Disclosed facts and limits
Target
User accounts in the "7pay" payment app (operator: 7pay, Inc. / Seven & i Holdings)
Detected
2–3 July 2019 (unauthorized access noticed right after launch)
Company assessment
In its August 1, 2019 statement, the operating group assessed an attack using lists of illicitly obtained IDs and passwords as the likely cause. This is the company's assessment at that time, not a claim that every attack path had been established.
Dated scope
808 people and ¥38,615,473, as of July 31, 2019 at 17:00, covering both unauthorized top-ups and unauthorized use. These are the dated figures in the August 1 disclosure, not a stated final total.
Not established in that disclosure
The same statement said it had not found cases where external-ID integration, password reminders or chat-assisted password resets directly caused the unauthorized access.

What the official statement establishes and leaves uncertain

In its August 1, 2019 statement, the operating group assessed an attack using lists of illicitly obtained IDs and passwords as the likely cause. This is the company's assessment at that time, not a claim that every attack path had been established. The company identified the system's authentication level, development arrangements and system-risk management as factors behind the failure to prevent the attack. It said countermeasures for logins from multiple devices and consideration of additional authentication such as 2FA had been insufficient.

The same statement said it had not found cases where external-ID integration, password reminders or chat-assisted password resets directly caused the unauthorized access.

A useful control is not proof of an incident's cause

Strong login and safe recovery are sensible defenses for current services. Recommending them does not prove that a particular missing feature or reset path was used in 7pay. Check recovery and contact changes even after strengthening login.

Three areas to check in a current service

Login

Login: avoid password reuse and combine additional authentication with detection and limits for abnormal attempts.

Recovery and reset

Recovery: verify recovery methods, backup options and how changes to registered contacts are authorized.

Payments and important actions

Important actions: review re-authentication, transaction alerts and the official way to stop unrecognized use.

General defensive checks, not the sequence of a confirmed 7pay attack.

Published timeline

  1. 2019-07-01

    7pay launches (inside the 7-Eleven app, integrated with 7iD).
  2. 2019-07-02

    The company receives a customer inquiry about an unrecognized transaction.
  3. 2019-07-03

    Important notices are published; overseas-IP access is blocked and credit/debit-card top-ups are suspended.
  4. 2019-07-04

    Cash top-ups at registers and ATMs, and new registrations, are suspended.
  5. 2019-07-05

    A security-response project is established.
  6. 2019-08-01

    Abolition of the service is announced (a safe restart would take considerable time).
  7. 2019-09-30

    7pay shuts down.

The company's disclosed issues and general preventive measures

Company assessment

The company identified the system's authentication level, development arrangements and system-risk management as factors behind the failure to prevent the attack. It said countermeasures for logins from multiple devices and consideration of additional authentication such as 2FA had been insufficient.

Checks for current development, as general advice

  • Login: avoid password reuse and combine additional authentication with detection and limits for abnormal attempts.
  • Recovery: verify recovery methods, backup options and how changes to registered contacts are authorized.
  • Important actions: review re-authentication, transaction alerts and the official way to stop unrecognized use.

A useful control is not proof of an incident's cause

Strong login and safe recovery are sensible defenses for current services. Recommending them does not prove that a particular missing feature or reset path was used in 7pay. Check recovery and contact changes even after strengthening login.

How you defend against this

Even if you don't build payments, if there's a single place where one login moves a lot of value, this is yours. In priority order:

1

Offer two-factor authentication (2FA) on sensitive actions

Put 2FA on login and on money/data-moving actions, and prefer phishing-resistant methods like passkeys where you can. Even a one-time password (OTP) is far stronger than a single password.

2

Restrict password reset to 'registered channels only'

Do not send a new password itself. Use a short-lived, single-use reset link or equivalent through a verified contact. Authenticate changes to that contact, do not accept fragments of personal data alone as proof, and notify the account owner about reset and contact changes.

3

Assume credential-stuffing; detect and limit it

Attacks that replay leaked credentials are a given. Add rate limits, anomalous-login detection, and lockout after N tries, and reject known-breached passwords. Nudge users away from reuse.

4

Review the auth flow before launch

Have login, reset and re-auth reviewed by a second set of eyes at design time and before launch. "It works" is not "it's safe." Don't skip auth review for speed.

Our assessment: review more than the login screen

The disclosed assessment supports reviewing authentication and multi-device controls before launch. As general engineering practice, also check authorization for recovery, contact changes and important actions. Adding a 2FA setting by itself does not establish that the whole account is protected.

Correction and sources

Corrected October 18, 2026: the previous version asserted that password reset was a direct cause and illustrated that attack sequence. We replaced those claims with the dated official assessment and a general defensive diagram. The URL and original publication date are retained.

  • Operating group's notice on discontinuation, investigation and response (2019-08-01) — 7andi.com
  • Operator's notice after discontinuation and on unused-balance refunds (2019-10-01) — sej.co.jp

FAQ

QWhat did the company say about the cause?
A

In its August 1, 2019 statement, the operating group assessed an attack using lists of illicitly obtained IDs and passwords as the likely cause. This is the company's assessment at that time, not a claim that every attack path had been established. The same statement said it had not found cases where external-ID integration, password reminders or chat-assisted password resets directly caused the unauthorized access.

QAre the victim count and amount final totals?
A

808 people and ¥38,615,473, as of July 31, 2019 at 17:00, covering both unauthorized top-ups and unauthorized use. These are the dated figures in the August 1 disclosure, not a stated final total.

QWhat should an individual user check?
A

Use a different password for each service, enable supported MFA, keep a usable backup and recovery method, and review payment notifications. Report unrecognized activity through the service's official support channel.