All Breaches
March 22, 2017 Verified Data Services

Factual Data Breach

The Factual data record refers to the file of business and point-of-interest data associated with the data collector Factual on March 22, 2017, which was later shared as an alleged breach.

2.5 Million
Reported Records
4
Data Types
Critical
Severity
Oct 10, 2026
Last updated

Protect Yourself

Check whether you were affected by this breach

Check my email

Exposed Data Types

4
  • Email addresses
  • Employers
  • Phone numbers
  • Physical addresses

About This Breach

The file contains approximately 8 million rows, while the verified search scope is 2,461,696 unique email accounts. The verified data types are email addresses, employer or business names, phone numbers, and physical addresses. In the assessment carried out with Factual, it was stated that the data consists of publicly available information on websites and provided to customers about businesses and points of interest. Therefore, the record should not be presented as a personal account password or financial data leak; the primary risk is the reuse of business contact data for spam, sales targeting, and social engineering.

Leaking Data Types and Risks

The data types listed in this record are Email addresses, Employers, Phone numbers, and Physical addresses. When email, phone, and physical addresses are found together, a business, branch, employee, or point of interest can be targeted more easily. Business names and addresses can lay the groundwork for fake supplier, fake map entry, fake advertising service, fake invoice, or fake directory update messages. This record does not contain passwords, payment cards, bank accounts, or private customer profiles; however, the widespread circulation of business contact information increases the risk of B2B spam and targeted sales fraud. The risk is more pronounced for small business owners using personal email addresses because business communication and personal accounts may converge at the same address.

Verified Scope and Boundaries

The verified main metric is 2,461,696 unique email accounts. The total number of rows is approximately 8 million; this number is not the number of unique individuals and may include duplicate business/location records. Data types are limited to email, employer or business name, phone, and physical address. Password, username, payment card, official ID, date of birth, private customer file, or consumer account history have not been verified in this record. Although it is stated that the data consists of publicly available business and point-of-interest information, its circulation in bulk poses a risk. This distinction is important: the record should not be considered completely harmless, but it also should not be described as if individual user accounts have been compromised. The impact is more on business communication, data broker visibility, and targeted messaging.

User Groups at Risk

The main group at risk consists of business owners, local business employees, branch contact addresses, sales and customer support teams, and publicly visible contact points in map and location data. Small business owners who use their personal email address for business registration are at higher risk. Records with phone and address fields can be used for fake directory updates, fake listings, fake ad packages, fake invoices, and fake vendor calls. If the business location and phone information are accurate, attackers appear more credible. Sales and support mailboxes in corporate teams may receive heavy spam. Business communication channels are affected more than consumer accounts; however, in single-person businesses, the distinction between business and personal identity is blurred, so privacy impact may also occur.

Urgent Measures to Be Taken

If your email address appears in this record, first determine whether it is being used as a business, branch, support, or personal email address. Do not panic and assume a password breach since the password field has not been verified; however, if the same email appears with a password in other leaks, secure the account. Before making any payment for unexpected business directory updates, advertising packages, map verifications, invoices, supplier registrations, or subscription renewal messages, verify the request through an independent channel. Do not place extra trust in people who call and know your business name and address; this information may have been obtained from public or bulk data sets. Small businesses should evaluate incoming invoice and directory listing requests not based on a single person's approval, but with a second check.

Long-Term Security Strategies

Although business communication data is often publicly available, circulating it in bulk data sets reduces targeting costs. Businesses should keep publicly available email and phone addresses role-based and avoid using personal email addresses in business records as much as possible. It should be regularly checked what information is published in directories, maps, advertisements, and supplier records. Sales and support mailboxes should be protected with spam filters, invoice verification rules, and supplier approval processes. On the data provider side, bulk access to publicly available information, download limits, customer data usage conditions, and misuse monitoring controls are important. Regularly monitoring how the same business email appears in different data sets reduces the risk of targeted fraud.

Record Control and User Action

LeakData check shows whether your email address is included in this business and interest point dataset associated with Factual. A positive result does not mean your password, payment card, or personal account history has been exposed; it means that verified risk emails, business/employer names, phone numbers, and physical address information have been circulated in bulk. User actions include carefully checking incoming business verification and invoice messages, separating personal email from business records, strengthening filters against spam and sales targeting, and regularly monitoring whether the same email address appears in other leaks combined with passwords or financial data. This record should be considered particularly as a practical social engineering alert for small business and local service owners.

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