What happened?
In July 2026, electronic test and measurement equipment company Fluke was targeted in a ShinyHunters "pay or leak" extortion campaign . The group subsequently published more than 100GB of data allegedly taken from the company. The corpus contained largely corporate contact information, including over 800k unique email addresses, names, phone numbers and physical addresses. A large collection of support cases was also present.
When did it happen?
The breach date in the public record is July 1, 2026. The record was added to the catalogue on July 15, 2026 and last updated there on July 15, 2026.
What information was reported as exposed?
- Email addresses
- Employers
- Job titles
- Names
- Physical addresses
- Support tickets
These are incident-level categories. The record does not prove that every category was exposed for every affected person.
Who may be affected?
This record may be relevant to people who had an account or other relationship with Fluke or used fluke.com around July 1, 2026. A catalogue entry does not establish that every customer was affected or that every listed data category applied to each person. Compare the record with an official notice addressed to you.
What should you do?
Compare the organization, dates, and information categories with any notice you received. Use contact details you independently confirm.
Review your credit reports and consider a free credit freeze if identity information could support new-account fraud.
Treat unexpected breach follow-ups with caution. Do not use links or phone numbers in a suspicious message; contact the organization directly.
Choose actions that match the information involved. If you find signs that someone is using your identity, the Federal Trade Commission provides a personal recovery plan at IdentityTheft.gov.
Sources and review information
- Have I Been Pwned breach catalogue record ↗
- Federal Trade Commission: What To Do After a Data Breach ↗
- Federal Trade Commission: Credit Freezes and Fraud Alerts ↗
Page reviewed September 14, 2026 by the Data Breach Help Editorial Team. Catalogue details reflect the provider record and may change.