Studio Inc., the provider of the Studio website service that Uzabase uses, had its cloud environment accessed without authorization between September 30 and October 1, 2026, and the stored data could be obtained from outside until October 14. For people who used the contact forms on websites Uzabase built and ran on Studio, names, birth dates, gender, addresses, phone numbers, emails and other form input such as employer, career and income may have leaked. It is not confirmed that anyone actually took the data, and no secondary harm has been found. Accounts and passwords for Speeda, NewsPicks and other Uzabase services are not affected, and people are asked to watch for suspicious emails, texts and calls.
Uzabaseinquiry forms of Studio-built websites
1MinorPossibleAnnounced Checked against sources (2026-10-28)
Unauthorized access to Studio may have leaked inquiry form data such as names, birth dates, addresses and career details. Speeda and NewsPicks accounts are not affected.
- Cause
- Via a vendor or service, Unauthorized access
- Occurred
- 2026-09-30 – 2026-10-01
- Sector
- IT, cloud & telecom
- Operational impact
- None
Data involved
| Data | Status | Count | Group | Evidence |
|---|---|---|---|---|
| Name | Possible leak | Not disclosed | Studioで作成・運営していたWebサイトのお問い合わせフォームの利用者 | Source(opens in a new tab) |
| Email address | Possible leak | Not disclosed | Studioで作成・運営していたWebサイトのお問い合わせフォームの利用者 | Source(opens in a new tab) |
| Phone number | Possible leak | Not disclosed | Studioで作成・運営していたWebサイトのお問い合わせフォームの利用者 | Source(opens in a new tab) |
| Postal address | Possible leak | Not disclosed | Studioで作成・運営していたWebサイトのお問い合わせフォームの利用者 | Source(opens in a new tab) |
| Date of birth | Possible leak | Not disclosed | Studioで作成・運営していたWebサイトのお問い合わせフォームの利用者 | Source(opens in a new tab) |
| Other | Possible leak | Not disclosed | Studioで作成・運営していたWebサイトのお問い合わせフォームの利用者 | Source(opens in a new tab) |
Counts are the figures the organization announced. Because the same person may be counted more than once, we do not add the rows together.
What users should do
- Watch for emails and texts pretending to be the company
- Ask the company’s help line whether you are affected
General steps based on the type of data involved. Check the organization’s notice or help line to see whether you are affected.
Other incidents naming the same service
- Incidents naming Studio (152 incidents)