Who this affects: people who have used Snow Peak's reuse buyback service, event reservation system, community app, or official online store and member app. Especially people who registered a bank account for payouts in the reuse buyback service. This article is based on Snow Peak's official notice and does not cover attack methods.
Developing: this article will be updated as the organisation publishes more
- Who is affected
people who have used Snow Peak's reuse buyback service, event reservation system, community app, or official online store and member app. Especially people who registered a bank account for payouts in the reuse buyback service.
- Confirmed so farSee the table ↓
- Cause
Listed as possibly affected
- Number of people
- Member number, name, name in kana, date of birth, age, gender, occupation
- Email address, phone number, address, customer number
2 more
- Identity verification status, order information
- Bank account information for payouts (bank name, branch, account type, account number, account holder name)
- Not yet confirmed
- Final count and scope for the reuse buyback service (under investigation)
- What the vulnerabilities were
- Completion of individual notices
2 more
- When the suspended services (reuse buyback, event reservations, community app) will reopen
- Whether there has been secondary damage
- What to do nowSee the steps ↓
- If you used the reuse buyback service: check the transactions on your payout account
- Do not respond to contact that uses the company's or a bank's name
- If you use the official online store or member app: review your password
4 more
- If you used event reservations: watch for contact that uses your booking or companion details
- If you used the community app: be careful of contact built from your display name or profile
- If you are worried, use the official contact point
- If you entered details or sent money, get help right away
- Where to verify (source)All sources ↓
- Snow Peak, "Apology and notice regarding personal information leakage due to unauthorized access" (November 13, 2026, in Japanese)
- Last checked
- As of November 15, 2026
Follow-up plans and what we checked
The company says no secondary damage caused by this matter has been confirmed so far. For the reuse buyback service, it says it is still investigating the number of people and the full scope. The company said the official online store would reopen on November 13 (we could not confirm from the notice whether it has reopened); the other suspended services will reopen in turn after security is strengthened. We checked the company's notice on November 15, 2026 and found no update since the November 13 notice.
What affected customers should do today
If you used the reuse buyback service: check the transactions on your payout account
The information that may have leaked in the reuse buyback service includes bank account information for payouts (bank name, branch, account type, account number, account holder name). The company says bank PINs and internet banking login details are not included. Still, someone who knows your account number and name can more easily make contact that looks like a transfer (our view). Check the transaction history in your banking app or passbook.
If a deposit you do not recognize arrives and someone contacts you saying "we sent it by mistake, please return it," do not send money yourself. Contact your bank first and ask about reversing it. The notice does not ask you to change your account. If you are worried, talk to your bank.
More on these scams is in the Japanese Bankers Association warning and the National Police Agency notice (both in Japanese, general warnings and not about this incident). A similar case involving bank account details is the Lashinbang incident.
Do not respond to contact that uses the company's or a bank's name
The company asks you to be careful of suspicious contact by email, SMS, phone or mail that pretends to be the company or a financial institution. If you get a suspicious email or SMS, do not open attachments or visit the URL; discard it.
The company says it never asks for passwords, credit card numbers, bank PINs or login passwords by email, SMS, phone or mail. Do not respond to contact that asks for them. The company's individual notices are likely to arrive by email or similar, so do not open links in them; check services in an app or official site you open yourself (our view). How to tell the difference is in What is phishing?.
If you use the official online store or member app: review your password
Unauthorized logins using IDs and passwords that appear to have been obtained elsewhere were confirmed on up to 445 online store and member app accounts. The company says no passwords leaked from its own systems. It asks for your understanding of the stronger login checks, and asks you to avoid reusing passwords from other services and to avoid guessable ones such as a date of birth or sequential digits.
If you use the same password on other services, change it (our view). To check reuse, see How to check if your password has leaked; for two-step login, see Setting up multi-factor authentication. A screen showing the card type and part of the card number may have been viewed, so check your card statement as a precaution.
If you used event reservations: watch for contact that uses your booking or companion details
The information that may have leaked in the event reservation system includes the applicant's name, address, phone number, email address and date of birth, a companion's name, age and gender, and application details such as event name, date, lodging, amount, vehicle type and remarks. Leakage of credit card information and passwords has not been confirmed so far.
Generally, someone who knows your booking can more easily make contact that pretends to confirm a reservation or charge a cancellation fee (our view). Check anything about a booking through the official booking page you open yourself or by phone, not through links in an email. Because companions' details are included, it also helps to tell the family or friends who came with you not to respond to suspicious contact.
If you used the community app: be careful of contact built from your display name or profile
The information that may have leaked in the community app is the member number, display name (your name if you registered it), self-introduction text and cover image. The company says addresses, phone numbers, email addresses, passwords and credit card information are not included.
The notice does not describe any immediate action based on this data alone. If a stranger contacts you in the app and asks for personal information or money, do not respond.
If you are worried, use the official contact point
The contact point in the notice is Snow Peak User Service by phone: 0120-010-660 (9:00 to 17:00, Monday to Friday, excluding weekends and holidays; a Japanese toll-free number). If the line is busy, you can use the company's inquiry form.
Use the contact point in the official notice, not one written in an email or SMS.
If you entered details or sent money, get help right away
If you entered bank details or personal information on a suspicious link or sent money, contact your bank or card company right away. You can also call the police advice line (#9110 in Japan) or the Consumer Hotline (188). To check an account for suspicious activity, see How to check for unauthorized access.
What happened (from Snow Peak's notice)
On November 13, 2026, the company posted "Apology and notice regarding personal information leakage due to unauthorized access" in the important notices section of its site. Everything below is what the company says.
October 29 to 30
Unauthorized logins to the official online store and official member app using IDs and passwords that appear to have been obtained elsewhere (one of the confirmed periods).October 30
Unauthorized access to the event reservation system and the community app (one of the confirmed dates).November 8 to 9
Unauthorized access to the event reservation system and the community app. On November 9, unauthorized access to the reuse buyback service and unauthorized logins to the online store and member app also took place.November 9
The company detected suspicious access to the official online store and member app and began investigating.November 10 to 12
The company confirmed the community app leak on November 10, the event reservation system leak on November 11, and the possible leak from the reuse buyback service on November 12.November 13
Posted the notice. It had suspended four services and said the official online store would reopen on November 13 (whether it has reopened is unconfirmed). It is reporting to the Personal Information Protection Commission and other authorities.
These are separate figures for each service. The same person may appear in more than one, so the company has not announced a combined total, and this article does not give one.
- Services involved
- Four matters: the reuse buyback service, the event reservation system and the community app (information leaks), and the official online store and official member app (unauthorized logins)
- Cause
- The three leaks are attributed to a vulnerability in each service, not to customers' own management. The unauthorized logins used IDs and passwords that appear to have been obtained elsewhere
- Not included (varies by service)
- Bank PINs, internet banking login details, passwords, credit card numbers. See the tables below
- Response
- Suspended four services. Strengthening security and monitoring. Investigation with outside experts (reuse buyback). Reporting to the authorities is under way
- Secondary damage
- None confirmed so far
- Contact
- User Service 0120-010-660 (9:00 to 17:00, Monday to Friday, excluding weekends and holidays). Inquiry form if the line is busy
Items and status by service
This is based on the company's notice of November 13, as of November 15, 2026. The status column follows the company's wording. We will update it when there is news.
Reuse buyback service (24,948 people)
The unauthorized access was on November 9, and the company confirmed the possible leak on November 12.
| Item | What the notice says | Status |
|---|---|---|
| Number of people | 24,948 at present. The number and full scope are under investigation | Possible (company; under investigation) |
| Member number, name, name in kana, date of birth, age, gender, occupation | Among the information that may have leaked | Possible (company) |
| Email address, phone number, address, customer number | Among the information that may have leaked | Possible (company) |
| Identity verification status, order information | Among the information that may have leaked | Possible (company) |
| Bank account information for payouts (bank name, branch, account type, account number, account holder name) | Among the information that may have leaked | Possible (company) |
| Bank PIN, internet banking login details | Not held by the company and not included | Not included (company) |
| Passwords, credit card numbers | Not included | Not included (company) |
| Cause | A vulnerability in the service, not customers' own management | Confirmed (company); details not stated |
| Images of ID documents | Not listed as an item | Not stated |
Event reservation system (5,923 people)
The unauthorized access was on October 30 and November 8 to 9, and the company confirmed the leak on November 11.
| Item | What the notice says | Status |
|---|---|---|
| Number of people | Data on 5,923 people may have leaked at present | Possible (company; current figure) |
| Applicant's name, name in kana, email address, phone number, address, date of birth, gender, customer number | Among the information that may have leaked | Possible (company) |
| Companion's name, age, gender | Among the information that may have leaked | Possible (company) |
| Application details (event name, date, lodging, amount, vehicle type, remarks, etc.) | Among the information that may have leaked | Possible (company) |
| Credit card information, passwords | No leak confirmed so far | Not confirmed (company) |
| Cause | A vulnerability in the system, not customers' own management | Confirmed (company); details not stated |
Community app (21,553 people)
The unauthorized access was on October 30 and November 8 to 9, and the company confirmed the leak on November 10.
| Item | What the notice says | Status |
|---|---|---|
| Number of people | 21,553 | Possible (company) |
| Member number, display name (your name if registered), self-introduction text, cover image | Information that may have leaked | Possible (company) |
| Address, phone number, email address, passwords, credit card information | Not included | Not included (company) |
| Cause | A vulnerability in the app, not customers' own management | Confirmed (company); details not stated |
Official online store and official member app (unauthorized logins, up to 445)
The company detected suspicious access on November 9. The confirmed login periods were October 29 to 30 and November 9.
| Item | What the notice says | Status |
|---|---|---|
| Unauthorized login | Some customers' accounts were logged in to using IDs and passwords that appear to have been obtained elsewhere. Up to 445 | Confirmed (company) |
| Name, address, phone number, email address, date of birth, purchase history, points, delivery address, etc. | May have been viewed | Possible (company) |
| Payment method (card type and part of the number) | Full card numbers are not shown, so they did not leak. A screen showing the first 6 and last 2 digits may have been viewed | Full number not included (company); partial digits possible |
| Passwords | No fact of passwords leaking from the company's systems | Not included (company) |
Overall
| Item | What the notice says | Status |
|---|---|---|
| Combined number of people | Not announced (only per-service figures) | Not stated |
| Misuse (secondary damage) | None confirmed so far | Not confirmed (company) |
| Individual notices | The company will contact customers who may have been affected individually | Planned (company) |
| Reports to authorities | Reporting to the Personal Information Protection Commission and other authorities is under way | In progress (company) |
What can happen with information that may have leaked
- Genuine-looking emails, SMS, calls and mail that use the company's or a bank's name
- Requests to "return" or "confirm" a deposit (reuse buyback customers)
- Contact pretending to confirm or charge for a booking (event reservation customers)
- Unauthorized logins to other services that share a reused password (our view)
What the notice says is not included or not confirmed
- Bank PINs and internet banking login details (reuse buyback)
- Passwords (reuse buyback and community app; for the online store, no fact of leakage from the company's systems)
- Full credit card numbers
- Secondary damage (none confirmed so far)
For operators: checking several services run as separate systems
The causes have not been disclosed in detail, so this covers only what the disclosed facts support.
- Check each service together: here, leaks through vulnerabilities in three services and a separate set of unauthorized logins were confirmed within about the same period (October 29 to November 9). When you run several services on separate systems, deciding in advance that finding suspicious access in one means checking the logs of the others for the same period helps you find the scope sooner.
- Prepare for IDs and passwords obtained elsewhere: the unauthorized logins used IDs and passwords that appear to have been obtained elsewhere. Extra checks at login, detection of many login attempts in a short time, and limiting how much of the card number is shown on screens are generally effective safeguards.
Sources (public records)
The facts in this article are based on the official notice below. We have not guessed at causes that were not disclosed.
- Snow Peak, "Apology and notice regarding personal information leakage due to unauthorized access" (November 13, 2026, in Japanese) — snowpeak.co.jp
Update history
2026-11-15: First version. Based on Snow Peak's notice of November 13. We checked the company's notice the same day and found no follow-up.
Read next
- When bank account details leak: The Lashinbang incident (ID documents and bank details) / What to do when a driver's license or ID document leaks
- How to spot fake contact: What is phishing?
- Checking passwords and two-step login: How to check if your password has leaked / Setting up multi-factor authentication
- Suspicious activity on an account: How to check for unauthorized access
- Other incidents in 2026: Data breaches and cyberattacks (Japan and overseas)