For: people who have requested a service provider through the quote service Meetsmore (ミツモア), and service providers registered on it. This article is based on the company's official notice and does not cover attack techniques.
Developing: this article will be updated as the organisation publishes more
- Who is affected
people who have requested a service provider through the quote service Meetsmore (ミツモア), and service providers registered on it.
- Confirmed so farSee the table ↓
- Information leak
- Unauthorized logins
- Vulnerability fix
Listed as possibly affected
- Count
- Information that may have been viewed through those logins
- Not yet confirmed
- Number of people affected (the notice gives only record counts)
- Technical details of the cause (withheld by the company to prevent abuse)
- When individual notices will be complete
- What to do nowSee the steps ↓
- Find out whether you are affected
- Do not respond to calls, visits, texts or emails posing as Meetsmore or your provider
- Never give passwords or card numbers to anyone
3 more
- Separate your password if you use it elsewhere
- Service providers: reissue meeting URLs registered inside Meetsmore
- If you were told your account was logged into, reset your password
- Where to verify (source)All sources ↓
- Meetsmore Inc., apology and notice regarding a personal information leak due to unauthorized access (November 16, 2026, Japanese)
- Last checked
- As of November 17, 2026
Follow-up plans and what we checked
The company says it will post any new facts on the same page. We rechecked that page on November 17, 2026 and found no update beyond the November 16 notice.
What customers and service providers should do today
Find out whether you are affected
The company says it is contacting affected customers and service providers in stages at their registered email addresses. The sender is given as no-reply@meetsmore.com.
A sender address can be faked. Do not log in or enter anything from links in the email; open the official site yourself. The company says its emails about this incident contain no link asking you to enter a password. Questions can go through the inquiry form in the company's notice.
Do not respond to calls, visits, texts or emails posing as Meetsmore or your provider
The leaked addresses and phone numbers are those registered in providers' schedules. A message that seems to know about your request is not proof that it is genuine. The company asks people to beware of suspicious calls, visits, texts and emails claiming to be Meetsmore or a service provider.
If a message about a "new quote", "extra charge" or "refund" arrives, do not open its link. Open the Meetsmore app or site yourself and check there (how to tell: What is phishing).
Never give passwords or card numbers to anyone
The company says it never asks for passwords or credit card numbers by phone, email or text. If someone asks, do not answer, even if they claim to be the company.
Separate your password if you use it elsewhere
The company says the logins used IDs and passwords that appear to have been obtained elsewhere, and that it has found no sign of IDs or passwords leaking from its own system. It recommends that anyone using the same password on other services change each to a different one.
A password manager is the practical way to sort this out, and how to check whether a password has leaked shows whether a reused password appears in past leaks. Turning on multi-factor authentication means a password alone is not enough to sign in.
Service providers: reissue meeting URLs registered inside Meetsmore
The company recommends that providers reissue online meeting URLs they registered inside Meetsmore. It says meeting URLs registered in a linked external calendar are not part of the leak.
If you had linked an external calendar, the subjects of linked events are affected (nothing but the subject). If you tend to put client or project names in subjects, review what was written.
If you were told your account was logged into, reset your password
On November 12 the company invalidated the passwords of the affected accounts and logged them out of all devices. It has contacted those customers individually and asked them to set a new password.
It says no changes to registration details, no messages sent and no payment operations have been confirmed. After resetting, check your profile and message history for anything you do not recognise.
What happened (from Meetsmore's notice)
Meetsmore Inc. published an apology and notice about a personal information leak caused by unauthorized access on November 16, 2026. Everything below is based on that notice. The company describes two separate events: an information leak, and unauthorized logins.
November 11, 2026, 15:39–16:27
A third party logged into 201 accounts using IDs and passwords that appear to have been obtained outside the company.November 11, 16:27 to November 12, 0:22
A third party used an account it had logged into to obtain information from part of the system. Up to 366,850 records may have leaked.November 12, 8:25
The company investigated an alert from its monitoring and found the incident. It blocked traffic from the source and fixed the vulnerability the same day. It invalidated the affected accounts' passwords and logged them out of all devices.November 13
Reported to the Personal Information Protection Commission and the Ministry of Internal Affairs and Communications, and consulted the police the same day.November 16
Published the apology and notice; said it would contact affected customers and providers by email in stages.
- Information leaked
- Customers' addresses and phone numbers registered in providers' schedules; identification numbers the company assigns to members and requests; online meeting URLs registered inside Meetsmore. If a provider had linked an external calendar, the subjects of linked events (nothing but the subject)
- Not included
- Names, email addresses, passwords, credit card information
- Count
- Up to 366,850 records may have leaked (about 370,000 in the notice's lead)
- Cause (company's explanation)
- A function that displays providers' availability had a vulnerability, which a third party exploited to obtain information registered in providers' schedules. Technical details are withheld to prevent abuse
- Unaffected service
- The company's service Proone runs on a separate system and is not affected
- Reports
- November 13: Personal Information Protection Commission and the Ministry of Internal Affairs and Communications; police consulted the same day
- Count
- 201 accounts (November 11, 15:39–16:27)
- Cause (company's view)
- IDs and passwords that appear to have been obtained improperly outside the company were used. No sign of IDs or passwords leaking from its own system
- Information that may have been viewed (customers)
- Registered name, email address, phone number, past request details (including address), messages with providers
- Information that may have been viewed (providers)
- Registered profile, messages, schedule, and the details of customers they deal with (name, address, request details and so on)
- Not confirmed
- Changes to registration details, sending of messages, payment operations
What is known and what is not
Based on the company's notice of November 16 as checked on November 17, 2026. We will update the status column as follow-ups appear.
| Item | What the company says | Status |
|---|---|---|
| Information leak | Addresses, phone numbers, identification numbers, meeting URLs and more registered in providers' schedules | Leak confirmed (company) |
| Count | Up to 366,850 records (records that may have leaked) | Possible (company); number of people not stated |
| Names, emails, passwords, card data (in the leaked information) | Not included | Not included (company) |
| Unauthorized logins | 201 accounts, using IDs and passwords that appear to have been obtained elsewhere | Confirmed (company) |
| Information that may have been viewed through those logins | Customers' name, email, phone, request details (including address); providers' profile, messages, schedule and more | Possible (company) |
| Changes to registration, messages sent, payments | Not confirmed | Not confirmed (company) |
| Cause of the leak | Vulnerability in a function that shows availability; technical details withheld | Partly disclosed (company) |
| Vulnerability fix | Fixed on November 12; the same method no longer works | Confirmed (company's explanation) |
| Misuse and secondary harm | None confirmed at this time | Not confirmed (company) |
| Impact on Proone | Runs on a separate system; not affected | Not included (company) |
| Number of people | The notice gives record counts only | Not stated |
| Individual notices | Being sent by email in stages | In progress |
A record count is not a head count
Up to 366,850 is a record count. The company does not give a number of people, and records and people do not necessarily match.
The 201 is a count of accounts, not people.
What addresses, phone numbers and meeting URLs can lead to
This describes what can generally happen when the same combination of data leaks. It does not mean it happened in this case.
Address + phone number + identification number
↓→
Calls, visits or texts posing as your provider or Meetsmore
→ Do not respond; check in the official app
Online meeting URL
↓→
Anyone who knows the URL could join the meeting (general)
→ Providers reissue the URL
ID + password (obtained elsewhere)
↓→
Logins to services where the password is reused
→ Stop reusing; use multi-factor authentication
Leaked, or possibly viewed
- Addresses and phone numbers registered in providers' schedules
- Identification numbers for members and requests
- Online meeting URLs registered inside Meetsmore
- Request details and messages inside the accounts that were logged into
Not included or not confirmed, according to the notice
- Names, emails, passwords and card data are not in the leaked information
- No changes to registration, sent messages or payments have been confirmed
- Proone is not affected
For people who run booking and quote services
The technical details have not been published. The points below follow only from the sequence of events the company describes.
Detect logins that use reused IDs and passwords
The company says the unauthorized logins used IDs and passwords that appear to have been obtained elsewhere, and that they hit many accounts within a short time. Consider alerts for many failed and successful logins from one source in a short time, and offer multi-factor authentication at login (rate limiting and abuse control).
Separate what a schedule or availability view can return, by the viewer's permission
The company says information registered in providers' schedules was obtained through a function that shows availability. As prevention it says it reviewed access permissions across all functions that handle customer information.
For your own service, list who each schedule-display function returns data to and which fields it returns, and check that it does not return addresses or phone numbers that are not needed.
Decide the steps from detection to cut-off in advance
The company says it found the incident at 8:25 on November 12 by investigating an alert from its monitoring, then blocked the traffic and fixed the vulnerability the same day. Decide who receives overnight alerts and who can decide to stop the service.
Sources (public record)
The facts in this article are based on the public information below. We have not speculated about technical details that have not been published.
- Meetsmore Inc., apology and notice regarding a personal information leak due to unauthorized access (November 16, 2026, Japanese) — company.meetsmore.com
Update history
2026-11-17: First version, based on the company's notice of November 16. We rechecked the same page and found no follow-up. We will update this article when new facts are published.
Read next
- An example of 2026 cases in Japan that began with legitimate credentials: how 2026 breaches in Japan began, across cases
- A same-period case involving a business-facing service's member data: unauthorized access to Commune
- Guarding against follow-on scams: What is phishing / Smartphone security basics
- Passwords and login: Choosing a password manager / How to check whether a password has leaked / Multi-factor authentication guide
- Other 2026 incidents: Data breaches and cyberattacks in 2026