One breach, 1,694 shops: the GoQSystem leak
A contact-form flaw let attackers take order data from GoQSystem, hitting 1,694 retailers and millions of their customers. What leaked and what to do.
By Yaali. November 16, 2026, 6 min read, Threat intel, Phishing.
On 12 November 2026, GoQ System Co. said an unauthorised third party had reached its order-management system (OMS) and taken some stored order data outside the company. GoQSystem is a Japanese platform that online retailers (EC businesses) use to run their sales across several marketplaces from one admin console at order.goqsystem.com. A follow-up notice on 13 November put numbers on it: about 1,694 client companies, roughly 4,984,595 orders, and the personal information of about 4,367,390 people, the end customers of those retailers, potentially leaked.
If your shop runs on GoQSystem, the exposed records belong to your customers. You are the party those buyers handed their name and address to, and in most cases you are the one who has to tell them what happened. The window matters: GoQSystem blocked the entry route and suspended the service on 11 November, disclosed on the 12th, sized the damage on the 13th, and on 15 November warned that scammers were already registering lookalike domains and sending emails in its name. The phishing wave uses the same order details that leaked.

What happened
The attackers did not break into each shop. They broke into the platform all those shops sit on, through a vulnerability in the website inquiry (contact) form. A contact form takes text a stranger types and hands it to the application behind it: it stores the message, often queries a database, and triggers a notification. That form is reachable without any login, which is the point of a contact form and also why it is a favourite way in. When the input is not handled safely, the data a visitor submits stops being treated as plain text and starts being treated as a command the application runs.
From that foothold the attacker reached the stored order records. GoQSystem says the exposed fields are the names, addresses, phone numbers and email addresses of the people who placed or received orders, together with the order contents. The company states it does not store credit-card numbers, so card data is not part of this leak, and it has not reported passwords as taken. The unauthorised access happened on 10 and 11 November. GoQSystem cut the route at 10:36 on 11 November and took the service offline at 10:55, then began making affected stores' data available to download so each retailer could see which of its own orders were in scope.
The structure of this is the real story. One OMS holds the customer records of 1,694 separate retailers, so a single flaw in a single form on a single platform exposed millions of buyers who never heard of GoQSystem and only ever dealt with the shop they bought from. That is third-party risk, or supply-chain risk: the data you are responsible for lives on someone else's server, behind someone else's code.
What attackers are doing
The second stage started within days. On 15 November, GoQSystem published a warning about fake sites and suspicious emails that impersonate it, built on domains that look almost like the real one. The company said the only legitimate admin domain is order.goqsystem.com, and that as of its notice no damage from the fake sites had been confirmed. That last point is a snapshot, not an all-clear.
Phishing that follows a breach is more convincing than the usual kind because the sender can quote real details. Someone holding the leaked records can email a buyer by name, reference a genuine order and its contents, and point them at a page dressed up as GoQSystem or as the shop. The common tricks with the domain are small edits that pass a quick glance: swapping a character for a similar-looking one, dropping or doubling a letter, adding a word like "login" or "secure", or changing the ending of the address. Messages that push a password reset or ask you to "confirm" a payment are the ones to distrust, because a real order-management vendor rarely needs either from a shopper.
For a retailer, two groups are at risk at once. Your customers may get order-themed lures, and your own staff may get mail aimed at the GoQSystem login, since credentials typed into a fake admin page hand an attacker the console directly.

What to do
If your shop uses GoQSystem, work through these in order.
- Read the vendor's notices in full and download your store's affected-order file from the console at order.goqsystem.com, so you know exactly which of your customers are in scope rather than guessing from the headline total.
- Notify the affected customers as your obligations require. Under Japan's personal-information rules a leak of this kind generally has to be reported and the people told; check your own legal and contractual duties and your timeline.
- Warn those customers plainly that scammers may contact them quoting a real order, that your shop and GoQSystem will not ask for a password or payment confirmation by email, and that the only legitimate admin domain is order.goqsystem.com. Give them a way to reach you that does not depend on clicking a link in an email.
- Rotate any credentials and interface keys shared with the platform: admin passwords, and any application programming interface (API) keys or tokens your shop or your other tools use to connect to GoQSystem. Turn on its internet-protocol (IP) restriction feature if you can, so logins only work from your own addresses.
- Preserve and review your access logs around 10 and 11 November and after, for logins from unfamiliar locations and for any sign that a staff member entered credentials on a fake page.
To check whether you were affected, do not rely on the public figure. The 4,367,390 count is the number of people across all stores whose records are in the exposed set, and GoQSystem has said this does not mean every one of them had data confirmed as taken. Your own download from the console is the authoritative list for your shop. If you cannot see that file or are unsure, contact the vendor through its official site before acting on anything that arrives by email.
The wider lesson
Most teams can name the systems they run themselves and far fewer can name the outside platforms that hold their customers' data. That list is the thing to build now: every third-party service that stores or processes your buyers' personal information, what each one holds, and how you would be told if it were breached. Put prompt breach notification and secure handling of untrusted input, the exact class of flaw behind this incident, into the contracts you sign with those vendors. And write the customer-notification and anti-phishing message in advance, so that when a vendor does call you are editing a template rather than starting from a blank page.
The contact-form flaw here is ordinary and findable: user input that reaches the application without being treated as hostile. We look for exactly this in web application penetration testing, and we help teams map which outside platforms touch their customer data in attack surface management. If you run on a platform like this and want a second read on your exposure, open the chat and Yaali, our AI agent, will pass your question to the engineer who would do the work.
Sources: INTERNET Watch (Impress), GoQSystem notice on lookalike sites and phishing, Security Measures Lab (Rocket Boys), NOVAIST.
Read next
- A fake IT call exposed 5.68 million at Marathon Health
- Blind Eagle returns with fake court notices
- SEGA email leak: 2.2M addresses from a mail vendor
Back to the blog, or tell us about your system in the chat. Yaali, our AI agent, answers first and brings in an engineer.