All Breaches
March 28, 2019 Verified Sensitive Record Electronics Manufacturing

Hakko Corporation Data Breach

The 2019 Hakko e-shop breach came to light when a customer told the company on March 20, 2019 that data obtained through unauthorized access had been uploaded to an overseas server.

9.7 Thousand
Email Identifiers
9
Data Types
Low
Severity
Oct 10, 2026
Last updated

Protect Yourself

Check whether you were affected by this breach

Check my email

Exposed Data Types

9
  • Names
  • Physical addresses
  • Phone numbers
  • Dates of birth
  • Company names
  • Email addresses
  • User IDs or usernames
  • Passwords
  • HIBP-reported gender

About This Breach

In its March 28 notice, Hakko said a system vulnerability was involved, temporarily closed the e-shop, sought removal of the uploaded data, and reported 9,793 customer records. The exact attack date was not published.

The operator notice lists names, addresses, phones, dates of birth, company names, emails, user IDs, and passwords. Hakko said the e-shop did not process card data and that no leak from its other sites had been confirmed. A public breach source later catalogued 9,665 unique emails with dates of birth, emails, gender, names, passwords, phones, addresses, and usernames and described the passwords as plaintext.

The 9,793 figure is the operator-reported customer-record total, while 9,665 is a public breach source's unique-email measure. The 128-record difference and source-specific fields such as gender and company name remain unreconciled. No person-level dataset or searchable Hakko data exists locally.

The record does not identify anyone as a Hakko customer or account holder and cannot establish orders, support, warranty activity, occupation, business type, name, address, phone, birth date, and password co-occurrence, compromise, or misuse. An authenticated old Hakko password should be replaced where it was reused, and unexpected e-shop contact should be verified independently.

Verification and editorial method

LeakData compares the incident name, date, affected-record count, and exposed data types with accessible sources. Unverified fields are not presented as facts, and records are updated when new evidence becomes available.

Report missing or incorrect information