Security Guides

Shippio Platform Unauthorized Access (About 1,300 Document Files Downloaded, About 1,100 Teams Hit): What Client Companies Should Do

Shippio reports unauthorized access: about 1,300 document files downloaded, fake accounts in about 1,100 teams. What client companies should do.

Published 2026-11-17 Updated 2026-11-17 Last verified 2026-11-17 10 min read
On this page

For: staff at shippers and trade companies that use the Shippio Platform, and their business partners. This article is based on Shippio, Inc.'s official notices (first to third reports) and does not cover attack techniques.

Developing: this article will be updated as the organisation publishes more

Who is affected

staff at shippers and trade companies that use the Shippio Platform, and their business partners.

Confirmed so farSee the table ↓
  • Company name, team name, address, phone number
  • Shipment information, document file names and types
  • Document file contents
4 more
  • Users' names and email addresses
  • Billing amounts
  • Unauthorized accounts and API credentials
  • Service status

Listed as possibly affected

  • Internal shared files
Not yet confirmed
  • Detailed cause and measures against recurrence
  • Details of the downloaded document files
  • Range of customer information in the internal shared files
2 more
  • Range of people whose personal information was taken
  • Findings of the outside security specialist
What to do nowSee the steps ↓
  1. Reset your Shippio password, and separate reused passwords
  2. Do not open documents or contacts you do not recognise
  3. Verify shipment, invoice and bank-detail messages by a separate channel
3 more
  1. Check data from before the stop against your originals
  2. Re-set up share links and API integrations, and look for accounts you do not recognise
  3. Wait for an individual notice; use the official contact
Last checked
As of November 17, 2026
Follow-up plans and what we checked

The company says it will promptly announce on the same page when its investigation and reports are complete or new facts emerge. It published a third report on November 16; when we checked its news list on November 17, there was nothing newer.

What client companies should do today

1

Reset your Shippio password, and separate reused passwords

The company says it reset all users' login sessions and passwords when it restarted the service. Set a new password using "Forgot your password?" on the login screen.

It strongly recommends changing the password on other services too if you used the same one there. It says Shippio passwords are managed by an external authentication service and were not taken, but a reset is a good time to separate them (see Choosing a password manager).

2

Do not open documents or contacts you do not recognise

The company says malicious files were uploaded to shipments, and that it has found no sign they were downloaded on the customer side. If a document you do not recognise is attached to a shipment after the restart, do not open it and tell the company's contact.

Do the same for suspicious emails or calls posing as company staff (for example asking for passwords or verification codes). The company says it does not ask for passwords, verification codes or API keys, and asks you not to open the link in an unexpected password-reset email either.

3

Verify shipment, invoice and bank-detail messages by a separate channel

The shipment information taken includes what is shipped, schedules and parties, and some customers' document contents were taken. That is material for convincing fake messages with correct partner names, goods and dates.

For anything about "customs documents", "sending an invoice", "freight payment" or "changing bank details", do not act on the email or its link. Confirm by a phone number you already know or a contact you verified at contract time. Inside your company, also set a rule that no one changes a payment destination alone (see What is phishing?).

4

Check data from before the stop against your originals

The company asks you to compare data downloaded before the service stopped, CSV files and data imported through the API with your originals before using it for work. It says it has not confirmed that business data such as shipments was rewritten, but it did find unauthorized accounts created and some configuration data written.

5

Re-set up share links and API integrations, and look for accounts you do not recognise

The company invalidated all previously issued shipment share links; reissue them if needed. If you use external API integrations you need to obtain access tokens again, and you may be asked to reissue API keys.

The company says it deleted the unauthorized accounts and API credentials. As a precaution, it is worth looking once through your team's member list and API key list for anything you do not recognise (this is our suggestion, not the company's instruction).

6

Wait for an individual notice; use the official contact

The company says it has contacted customers whose document contents were taken individually since November 5, and is contacting people whose personal information was taken in sequence. Use the contact for users in its notice (support@shippio.zohodesk.jp); it warns that replies may take time.

What happened (from Shippio's notices)

Shippio, Inc. published its first report on November 4, its second on November 5 and its third on November 16, 2026. Everything below is based on them. The first two reports were later edited with additions and corrections; this article uses the latest content.

  1. October 30

    The company confirmed improper access to its internal work tool had occurred from this date.
  2. About 19:30 on November 1 to about 17:00 on November 2

    The Shippio Platform was accessed without authorization several times by an outside third party.
  3. November 2

    The service was temporarily suspended from 10:40. About 11:40 the internal work tool used as the entry route was stopped. At 17:38 the company finished blocking the unauthorized access to the platform.
  4. November 4

    First report published at 9:00.
  5. November 5

    Service began restarting in sequence from about 9:20. All users' passwords were reset and all earlier share links invalidated. Second report published.
  6. November 16

    Third report published (state as of 16:00 on November 13). It corrected that customers' billing amounts were not taken and said a preliminary report had been filed with the Personal Information Protection Commission.
About 1,300
Document files actually downloaded
About 1,100 teams
Customer accounts in which unauthorized users and API credentials were created
Almost all
Customers with registered shipments whose shipment information was viewed
Not confirmed
Misuse of leaked information or secondary harm (per the company, as of Nov 16)
What the notices say (first to third reports)
Cause (company's explanation)
A tool used for internal work was misused, and the credentials stored in it were used to access the company's systems. The detailed cause is under investigation
Information viewed
Company name, team name, address, phone number: all customers. Shipment information (what is shipped, schedules, parties) and document file names and types: almost all customers with registered shipments
Information taken
Document file contents: about 1,300 files actually downloaded. Some internal shared files were also taken and may contain customer information; under investigation
User information
Users' names and email addresses are in scope. The company does not hold users' phone number data, so it did not leak (corrected on November 5). Passwords are managed by an external authentication service and were not taken
Billing-related information
Included in the second report, but later log analysis showed customers' billing amounts were not taken. Billing line items for some shipments (item names, quantities, the company's cost and similar) were taken (third report)
Data damage
Unauthorized user accounts and API credentials created (about 1,100 teams), some configuration data written, and malicious files uploaded to shipments. No rewriting of business data confirmed. The company says it has deleted or restored these
Response
Blocked the routes, changed related credentials, stopped the work tool, reset all users' passwords, invalidated share links. Filed a preliminary report with the Personal Information Protection Commission. Consulting an outside security specialist on cause and scope

What is known and what is not

State as of November 17, 2026 (reflecting the third report of November 16). We will rewrite this table when follow-ups appear.

ItemWhat the notices sayStatus
Company name, team name, address, phone numberViewed for all customersLeak confirmed (company)
Shipment information, document file names and typesViewed for almost all customers with registered shipmentsLeak confirmed (company)
Document file contentsAbout 1,300 files actually downloaded; details under investigationLeak confirmed (company)
Users' names and email addressesIn scopeLeak confirmed (company)
Internal shared filesSome taken; may contain customer information; under investigationPossible (company)
Billing amountsCustomers' billing amounts were not taken; billing line items for some shipments (item names, quantities, the company's cost and similar) wereConfirmed (company, third report)
Users' passwordsManaged by an external authentication service; not takenNot included (company)
Users' phone number dataNot held, not leaked (corrected on November 5)Not included (company)
Unauthorized accounts and API credentialsCreated in about 1,100 teams; deletedConfirmed (company)
Rewriting of business dataNot confirmed at presentNot confirmed (company)
Misuse and secondary harmNot confirmed at presentNot confirmed (company)
CauseMisuse of an internal work tool and the credentials stored in it; detailed cause under investigationPartly disclosed
Service statusRestarting in sequence since about 9:20 on November 5; automatic tracking updates for the stopped period are not backfilledConfirmed (company)
Range of people whose personal information was takenRange and items under investigation; individual notices in sequenceUnder investigation

What shipment information and documents can be used for

In general, a combination of shipment contents and documents is useful for messages that pretend to know the deal. This does not mean any of it has happened in this incident.

  • Shipment contents, schedules, parties + partner names: realistic notices about "a shipping delay" or "customs documents to confirm"
  • Document contents (invoices, shipping documents) + names and email addresses: a fake invoice copied from a real one with only the bank details changed, or a change request
  • A malicious file attached to a shipment: a file that looks like a document on the company's own screen (the company says there is no sign customers downloaded such files)

So judge a document or message not by whether its content looks correct, but by who sent it and by which route.

Sources (public record)

This article is based on the public information below. We do not speculate about causes or methods that have not been disclosed. We also checked the company's news list on November 17.

  • Shippio, Inc., "Apology and report on the leak of personal information and temporary service suspension following unauthorized access to our platform" (first report, November 4, 2026, Japanese) — shippio.io
  • Shippio, Inc., "Resumption of platform service and report on unauthorized access (second report)" (November 5, 2026, Japanese) — shippio.io
  • Shippio, Inc., "Notice Regarding Unauthorized Access to Shippio Platform (Third Report)" (November 16, 2026) — shippio.io

Update history

2026-11-17: First version, based on Shippio's first (November 4), second (November 5) and third (November 16) reports, using the latest content (billing amounts not taken, phone number data not leaked, and so on). We checked the company's news list the same day; nothing newer than the third report had been posted. We will update this article when a follow-up appears.

Latest breaking reports

All breaking reports →

FAQ

QWhat was leaked in the Shippio incident?
A

According to Shippio, Inc.'s notices (first report November 4, second report November 5, third report November 16), the affected data includes shipment information (what is shipped, schedules, parties), the file names and types of documents registered to shipments, company names, team names, phone numbers and addresses, and users' names and email addresses. About 1,300 document files were actually downloaded, and some internal shared files were also taken.

QIs my company affected?
A

The company says information such as company names, team names, addresses and phone numbers of all customers was viewed, and that shipment information and document file names and types were viewed for almost all customers that have registered shipments. It says it has contacted customers whose document contents were taken individually since November 5, and is contacting people whose personal information was taken in sequence. If you have not heard from it, you can ask the company's contact.

QWere passwords leaked?
A

The company says users' Shippio Platform passwords are managed by an external authentication service that handles logins, not stored in its own systems, and so were not taken. Because it reset every user's login sessions and password when the service restarted, you need to set a new password. If you reuse the password on other services, the company strongly recommends changing it there too.

QWhat caused the breach?
A

The company says a tool it used for internal work was misused, and the credentials stored in it were used to access its systems. The detailed cause and measures against recurrence are still being investigated. It says there were improper accesses to the internal work tool from October 30, and several accesses to the platform between about 19:30 on November 1 and about 17:00 on November 2 (JST).

QWhat should I do about fake invoices or shipment messages?
A

The company asks you not to open links or files, and to tell its contact, if you find a document you do not recognise attached to a shipment or receive a suspicious email or call from someone claiming to be its staff (for example asking for passwords or verification codes). Verify shipment or invoice messages by a separate channel such as a phone number you already know rather than by replying; be especially careful with requests to change bank details or destinations.

QI use shared links and the API. What should I do?
A

The company invalidated all previously issued shipment share links when it restarted, so reissue them if needed. Customers using external API integrations need to obtain access tokens again, and customers who issued Shippio API keys may be asked to reissue them.