{
  "id": "goqsystem-order-data",
  "url": "https://ohshit.app/incidents/goqsystem-order-data/",
  "title": "GoQSystem confirms theft of order data affecting 4.37 million people",
  "level": 4,
  "level_name": "septic-tank-blew",
  "date": "2026-11-12",
  "date_is_approximate": false,
  "updated": "2026-11-17",
  "tags": [
    "GoQSystem",
    "SaaS",
    "Ecommerce",
    "Data breach"
  ],
  "ecosystems": [],
  "summary": "An intruder exploited a vulnerability in GoQSystem’s contact form and took order data affecting 4,367,390 people across 1,694 merchant companies. The provider removed the form and kept IP restrictions on its admin console.",
  "splash": "Buyers and recipients whose orders were held in the affected GoQSystem merchant accounts. Older orders are also in scope.",
  "wipe": "Get your affected orders from GoQSystem, notify customers through known channels and verify partner integrations before resuming normal processing.",
  "in_the_wild": "yes",
  "source_exception": null,
  "cves": [],
  "fixed": [],
  "checklist": [
    {
      "title": "Identify affected orders and notify customers",
      "hint": "Ask support@goqsystem.com how to download your affected order list. Include buyers and delivery recipients when reconciling the list with your own order records. Preserve related access and export logs, and coordinate notices and reporting using Japan’s Personal Information Protection Commission guidance linked in the second notice."
    },
    {
      "title": "Verify storefront and warehouse integrations",
      "hint": "Check the vendor’s API status page before resuming processing. Follow the partner-specific instructions for any service that requires action. For Rakuten, verify the API approval and refresh the license key, then import missed orders and reconcile inventory errors. For STORES, obtain fresh refresh tokens for order management and inventory separately. Use Amazon Seller Central directly for FBA shipments while GoQ Logi’s FBA integration is suspended."
    },
    {
      "title": "Verify delivery and account messages independently",
      "hint": "Check unfamiliar delivery or payment requests in the original order page or through the carrier. For merchant logins, open your bookmark and confirm the host is order.goqsystem.com. If you entered a password on a lookalike, change it promptly through the genuine console and contact support@goqsystem.com."
    }
  ],
  "sources": [
    {
      "name": "GoQSystem November 12 incident notice",
      "url": "https://goq.co.jp/security-incident.html",
      "says": "Confirms intrusion, extraction, data fields and restricted service recovery.",
      "primary": true
    },
    {
      "name": "GoQSystem November 13 scope and response",
      "url": "https://goq.co.jp/security-incident-2.html",
      "says": "Gives affected companies, orders and people, identifies the vulnerable form and describes merchant response.",
      "primary": true
    },
    {
      "name": "GoQSystem API connection status",
      "url": "https://goq.co.jp/api-connection-status.html",
      "says": "Lists partner status and merchant recovery steps.",
      "primary": true
    },
    {
      "name": "GoQSystem November 15 impersonation warning",
      "url": "https://goq.co.jp/similar-sites.html",
      "says": "Lists genuine login domains and steps for reporting or responding to lookalikes.",
      "primary": true
    }
  ],
  "headline": null,
  "one_liner": null,
  "in_the_wild_note": "GoQSystem confirmed contact-form exploitation and order data theft.",
  "mitigation": null,
  "timeline": [
    {
      "date": "Nov 10–11, 2026",
      "title": "Intruder accesses the order-management system",
      "body": "GoQSystem blocks the access route and temporarily suspends the service on November 11."
    },
    {
      "date": "Nov 12, 2026",
      "title": "GoQSystem confirms order data theft",
      "body": "Emergency measures let the provider reopen the service with access limited by connection source."
    },
    {
      "date": "Nov 13, 2026",
      "title": "GoQSystem identifies the entry point and scope",
      "body": "A vulnerable contact form was exploited and has been removed. The provider counts 4,984,595 affected orders across 1,694 companies and 4,367,390 people."
    },
    {
      "date": "Nov 14, 2026",
      "title": "Provider lists integrations that require merchant action",
      "body": "Its status table marks Rakuten, BASE and STORES as requiring action and GoQ Logi as partially suspended."
    },
    {
      "date": "Nov 15, 2026",
      "title": "GoQSystem warns of impersonation",
      "body": "The provider publishes its genuine domains and says it has no confirmed cases of harm from lookalike sites at the time of the notice."
    },
    {
      "date": "Nov 17, 2026",
      "title": "BASE API integration returns",
      "body": "GoQSystem says no further steps are required for BASE merchants. Rakuten and STORES still require action, and the GoQ Logi FBA integration remains paused."
    }
  ],
  "body_markdown": "GoQSystem centralizes order processing for online merchants. GoQSystem traced the intrusion to a vulnerability in its contact form. Its reports give no further exploit details. The provider removed the form and says admin-console IP restrictions will remain in effect while it validates security.\n\nThe stolen data includes buyer and recipient names, addresses, phone numbers, email addresses and order details. The affected orders include records from before the November 10–11 intrusion. GoQSystem does not hold credit card data and excluded it from the leak. The November 13 totals count companies, orders and individuals separately. The provider planned to send affected merchants download instructions on November 14–15.\n\nThe first notice reported no further intrusion or known misuse at that time. The later impersonation warning gives no evidence of an active fake-site campaign. Buyers and recipients can verify whether their order was affected through the merchant’s established contact channel.\n\nFollow the current partner API status. For BASE merchants, GoQSystem now says there are no further actions. Rakuten merchants should update their license key, and STORES merchants should reissue refresh tokens for order management and inventory. Handle pending GoQ Logi FBA requests in Amazon Seller Central while the integration remains paused."
}