Yellow Hat Reports Breach in Web Work Reservation System, Possible Leak of 1.8 Million Member Records

Japanese automotive retailer Yellow Hat disclosed that its Web Work Reservation System was compromised, potentially exposing personal data of up to 1,801,499 members. The intrusion was detected on August 18, 2026, after which investigators confirmed that customer information stored on the company's member server may have been exfiltrated. Affected records include names, telephone numbers, email addresses, and member numbers. Yellow Hat has notified law enforcement and Japan's Personal Information Protection Commission while contacting impacted individuals through multiple channels. The company is advising members to remain vigilant against unsolicited communications that could indicate misuse of the stolen data.

Security NEXTTranslated from Japanese

Read at source

Yellow Hat, a major Japanese retailer of car parts and accessories, has confirmed a security breach affecting its online Web Work Reservation System.

The system, used by customers to book maintenance services such as oil changes, battery replacements, and vehicle inspections, was found compromised on August 18, 2026. Subsequent investigation revealed that personal information stored on the company's member server may have been accessed and leaked externally.

Up to 1,801,499 members could be impacted. The exposed data includes names, telephone numbers, email addresses, and member numbers.

Yellow Hat has reported the incident to police and the Personal Information Protection Commission. Affected members are being notified via email, SMS, telephone, or postal mail, with warnings to watch for any suspicious unsolicited contacts.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Data Breaches & Leaks

Yandex Restores Access to 96% of Yandex Disk Data After Data Center Attacks
k0t Operators Breach Corporate Firewalls and VPNs Exposing Over 70,000 Credentials
OpenCode Reports Possible Exposure of Third-Party API Keys After Legacy System Breach