Skip to content
JAENES
BLeak confirmedNovember 4, 2026 announced

ヤクルト本社Data breach / unauthorized access incident

笹尾 祐太朗の写真Reviewed by Yutaro SasaoWritten by Leak Watch editorial team published ・ updated
Occurred on
October 26, 2026
Announced on
November 4, 2026
Severity
BIncidents centered on names and contact details.
Scale
39,505 records
Main impact
Personal data of 3万9505件 were leaked due to unauthorized access to the website; this may include names, addresses, and telephone numbers of inquiry consumers, members, press contacts, and cosmetic applicants.
Information involved
Full nameHome addressPhone numberEmail address
Cause / key point
Data leakage due to unauthorized access to the website.
Industry
Food & dining
Listing / capital
Listed companyTSE Prime 2267
Last updated
November 5, 2026

Stock price reaction to the disclosureヤクルト本社 / 東証プライム 2267

2026.10.15 〜 2026.11.05Loading…

Stock information is reference data based on Yahoo Finance and may be delayed. This site does not solicit or advise investment and does not guarantee the accuracy or completeness of this information. We accept no liability for any investment decision based on it.

Where to go for this information

The steps themselves are on the protection guide. These links match the kinds of data in this incident, plus support contacts.

Ask AI about this incident

Opens an AI chat with this page's URL already in the prompt. Treat the answer as a starting point — always verify with the official sources listed above.

Ask ChatGPT ↗Search Perplexity ↗

Full nameHome addressPhone numberEmail addressHow severity is assessed →

Is this incident worth paying attention to?

Written & reviewed

笹尾 祐太朗の写真

Reviewed byYutaro SasaoFounder & CEO, MediaLeap Inc.

CEO of MediaLeap Inc. Working on both sides of web advertising and web media since 2013; founded the company in May 2025.

Review scope: cross-checking against primary sources (official and government announcements), verifying claims stay within the facts, and checking source attribution。Last reviewed:

Written by:Leak Watch editorial team (AI-assisted drafts verified against sources by the editorial team) · Reviewer profile · Request a correction

Related incidents

Browse the database →

Incidents sharing the same company, service, attack method or industry (grouped automatically from the disclosures).

← Back to Breach Watch