For: customers of Tsukaeru.net shared servers, Cloud VPS and related services, and anyone who runs a website or email on them. This article is based on the official notices of Tsukaeru.net Co., Ltd. and does not cover attack techniques.
Developing: this article will be updated as the organisation publishes more
- Who is affected
customers of Tsukaeru.net shared servers, Cloud VPS and related services, and anyone who runs a website or email on them.
- Confirmed so farSee the table ↓
- Cause
- Unauthorized connection to an internal system, reading of credentials, access to administrative functions
- Shared-server data and email
Listed as possibly affected
- Name, company name, address, phone number, email address and more
- Stored portal passwords
- Not yet confirmed
- Which customers and which data were viewed or obtained, and how many
- Whether anything was taken outside or misused
- Details of the period and route of the intrusion
2 more
- Implementation of recurrence-prevention measures
- Resumption of new VPS sign-ups
- What to do nowSee the steps ↓
- Reset the portal password and two-factor authentication, and change reused passwords
- Replace credentials stored inside your VPS or shared server
- On shared servers, check for missing data and email
2 more
- If you see odd logins or changes, save records and consult the company
- Beware of contact in the company's name, and ask through official channels
- Where to verify (source)All sources ↓
- Tsukaeru.net Co., Ltd., "[Important, third report] Investigation and response status regarding unauthorized access to internal systems" (Japanese original, November 20, 2026)
- Last checked
- As of November 21, 2026
Follow-up plans and what we checked
The company says it will report progress, and any newly found impact on customers and actions needed, on its official site and by email. As of the third report, the integration with its waffle service was still being restored and new VPS sign-ups in its online store remained suspended.
What Tsukaeru.net customers should do today
Reset the portal password and two-factor authentication, and change reused passwords
The company invalidated the Tsukaeru Portal login passwords and asks customers to reset their password and two-factor authentication. If you have not, use "Forgot password" on the login screen.
The November 7 flash report says stored passwords were encrypted but may have been decrypted by a third party. If you use the same password as the portal for email or other services, change each to a different one, email accounts first (how to check: how to check whether your password leaked; for two-factor authentication: choosing multi-factor authentication).
Replace credentials stored inside your VPS or shared server
In its second report the company asks everyone, whether or not they use the portal, to change the passwords of the services they use as a precaution. Servers often hold other credentials as well.
As general advice from this site, not the company's, replace the following:
- Server login passwords, SSH keys and FTP passwords
- Admin passwords for WordPress and similar, and database passwords
- API keys and tokens written in configuration files (reissue them on the external service)
For where to keep them, see how to keep .env files out of public reach on shared hosting.
On shared servers, check for missing data and email
According to the company, shared servers where it confirmed unauthorized access were restored from the November 2 backup. Website data updated and email sent or received between that backup and the early morning of November 7 were therefore lost.
- Check that site updates, posts, setting changes and uploads made after November 2 are still there, and re-apply any that are missing from your own copies
- Check for email you should have received between November 2 and the early morning of November 7, and ask important senders to resend
- For sites with orders, bookings or form data, compare that period with other records such as payment and email notifications
If you see odd logins or changes, save records and consult the company
The company asks shared-server customers who notice logins, file or setting changes, or unusual behaviour they do not recognise to save the related records and consult it before deleting suspicious files or rebuilding the server. Its second report gives the same guidance for VPS customers. For how to inspect, see how to check if your website or server was hacked.
Beware of contact in the company's name, and ask through official channels
Because registration data (name, company name, address, phone number, email address and more) may have been viewed, fake invoices, renewal notices or password-reset messages in the company's name are conceivable. Do not open links; check on the official site you open yourself (how to tell: What is phishing?).
The channels named in the company's notice are its support system and email (support@tsukaeru.net). When you write, include the service name, your contract number if known, and the date and details of what you saw, and never include passwords, private keys or verification codes. The company says inquiries are concentrated and replies are slow. If you contract through a partner, ask your usual contact.
What happened (from Tsukaeru.net's notices)
The following is based on the company's flash report of November 7, its notice of November 9, its second report of November 11 and its third report of November 20.
Nov 2
Date of the backup used to restore the shared servers (per the company).Nov 6
The company confirmed an anomaly in a server it manages and began investigating.Nov 7
Flash report published: unauthorized access and leak of customer information. On shared servers, updates and email after the Nov 2 backup up to the early morning of Nov 7 were lost.Nov 9
Company confirmed unauthorized access to an internal system managing customer information and said the data may have flowed outside.Nov 11
Second report: says VPS was restored around 03:00 on Nov 7; service status, contract-management panel recovery, and requests to customers.Nov 20
Third report: what the investigation confirmed, actions so far, and recurrence-prevention measures under consideration.
- Environments with confirmed access
- In customer-facing service environments, only some Tsukaeru Cloud VPS host machines and some shared servers used through the portal (third report)
- Registration data
- Name, company name, address, phone number, email address and more may have been viewed or obtained (second report). Which customers and information is under investigation, and includes customers who do not use the portal (third report)
- Credit card information
- The portal does not store card information, so no card data leaked from the portal (flash report, Nov 7)
- VPS
- The Nov 7 flash report said it was checking 127 VPSs related to host machines where unauthorized access was confirmed (the company said this is the number being investigated, not the number confirmed intruded or leaked). It says it has contacted affected customers individually (third report)
- Shared servers
- Restored from the Nov 2 backup. Data updated and email sent or received after it, up to the early morning of Nov 7, were lost. Scope of viewing or obtaining is under investigation
- Company's response
- Stopped the affected internal system, revoked related access keys, updated the portal software and restored it from backup, invalidated portal passwords, external-organisation investigation, report to the relevant authorities
What is known and what is not
Status as of November 21, 2026. We will rewrite the status column as updates appear.
| Item | What the notices say | Status |
|---|---|---|
| Cause | Unauthorized access exploiting a vulnerability in software used by the portal | Confirmed (company; no software name or route given) |
| Unauthorized connection to an internal system, reading of credentials, access to administrative functions | Confirmed | Confirmed (company) |
| Name, company name, address, phone number, email address and more | May have been viewed or obtained by a third party | Possible (company) |
| Scope and number of customers and data viewed or obtained | Under investigation | Under investigation |
| Taken outside, or misused | Under investigation | Under investigation |
| Credit card information | Not stored in the portal; no leak from the portal (Nov 7) | Not included (company, for the portal) |
| Stored portal passwords | Encrypted but may have been decrypted (Nov 7) | Possible (company) |
| Shared-server data and email | Those after the backup, up to early Nov 7, were lost | Confirmed (company) |
| Viewing or obtaining of data inside VPSs and shared servers | Scope under investigation | Under investigation |
| Other services (file box, data protect, mail buster, waffle, private cloud, SSL certificates, domains) | As of Nov 11, no unauthorized access to the services themselves confirmed | Not confirmed (company, as of Nov 11) |
| Period of intrusion | Not mentioned (an anomaly was confirmed Nov 6) | Not stated |
| Recurrence prevention | Review of how credentials are stored and used, access permissions, separation of internal systems and service environments, and the scope of encryption of stored customer data | Under consideration (company) |
How to read this: 'not confirmed' as of November 11 does not include later investigation
"No unauthorized access confirmed" for other services is from the second report of November 11. The third report of November 20 says that, in customer-facing environments, only some cloud VPS host machines and some shared servers were confirmed. "Possible" does not mean "did not leak"; it means the investigation is still under way.
What registration data plus server access can enable
In general, name, company name, address, phone number and email address together let someone write convincing fake invoices, renewal notices and password-reset messages. Messages posing as renewals or payments aimed at server customers are conceivable. That does not mean this has happened here.
Credentials kept inside a server, such as database passwords or API keys, can become a way into other services if the server's contents were viewed. Whether they were is under investigation, so it is safer to replace them on the assumption that they were (a general approach, not the company's guidance).
For people who run sites on rented servers: what the published facts suggest
The company explains that restoring from backup lost data and email created after the backup. On shared hosting, the provider's backup is not necessarily current. Keeping your own regular copies of site content, databases and email in a separate place lets you restore what a rollback like this removes (backup and recovery essentials).
For recurrence prevention the company lists a review of how credentials are stored and used, finer access permissions, stronger separation of internal systems and service environments, and the scope of encryption of stored customer data. For what customers should do when a provider is breached, see when your web hosting provider is breached: what customers should do. The software name and intrusion route have not been disclosed, so this section does not assess the company's response.
Sources (public record)
The facts in this article come from the public information below. We have not speculated about any undisclosed route or technique.
- Tsukaeru.net Co., Ltd., "[Important, third report] Investigation and response status regarding unauthorized access to internal systems" (Japanese original, November 20, 2026) — tsukaeru.net
- Tsukaeru.net Co., Ltd., "[Important, second report] Investigation and response status regarding unauthorized access to internal systems" (Japanese original, November 11, 2026) — tsukaeru.net
- Tsukaeru.net Co., Ltd., "[Important] Possible leak of customer information through unauthorized access to internal systems" (Japanese original, November 9, 2026) — tsukaeru.net
- Tsukaeru.net Co., Ltd., "[Important, flash report] Apology and report on unauthorized access and leak of customer information" (Japanese original, November 7, 2026) — tsukaeru.net
Update history
2026-11-21: First version, based on the company's notices from November 7 to 20 (flash report to third report). The company says it will report progress in sequence, and we will update this article when it does.
Read next
- When your host itself is breached: when your web hosting provider is breached: what customers should do
- Checking your own site: how to check if your website or server was hacked
- A similar case: ConoHa WING unauthorized access
- Preparing: Backup and recovery essentials / What is phishing?
- Other 2026 incidents: Data breaches and cyberattacks (Japan and abroad)