B2B USA Businesses Data Compilation (2017)
Compiled U.S. corporate contact spam list'
What this rating measures
The Index rates how dangerous a breach is right now rather than how large it was. It values each exposed field on its own, ages each one according to what that field is, and models what the assembled set lets an attacker do.
It is read against what is observed circulating, not what was announced. Five bands run from Low through Guarded, Elevated and High to Severe.
Every rating carries a status. Observed means it rests on fields seen circulating. Observed minimum means at least that much was seen, so read it as a floor. Provisional means the field list comes from breach catalogues and is not yet verified. How sure we are of the evidence is shown separately, and it never lowers the rating. How the Index works →
Includes data that locates or profiles a person, beyond contact details.
- Volume
- Count not yet verified
- Field types
- 6 listed
- Breach date
- Jul 2017
Breach- Listed in breach catalogues
What data was exposed
How this data can be used against you
Assessed once the record is scored.
Two key actions to take
Assume your home address is findable
Be wary of unexpected visitors, deliveries or messages that mention where you live. Ask people-search sites to remove your address, and check again every few months, because listings come back.
Lock your mobile number
Ask your carrier for a port-out PIN so no one can move your number to a new phone.
Check whether you were affected
Most people in a breach like this do not need an engagement. They need to know whether their address is in it, and when it turns up somewhere new. HackNotice does both, free: an Instant Check now, alerts after.
Talk to us about your exposure
If you are exposed in a way that cannot be rotated away, or you are responsible for someone who is, a call establishes what is actually reachable about you and what is worth doing first. No charge for the conversation.
Request a confidential call →The full breach analysis
What happened, what the company reported against what is circulating, the field-by-field record, the actor and the advisory.
- What happened
- Recent developments
- Reported and circulating
- Data points exposed
- Downstream risk
- Principal risk advisory
- Threat actor
How this breach happened
A large spam and marketing dataset known as "B2B USA Businesses" was discovered online in 2017, exposing over 105 million records tied to professionals across corporate America. The list was not associated with a consumer-facing company or service. It functioned as a compiled targeting corpus, organizing business contact information by employer for outreach and marketing purposes. No attacker or specific breach method has been identified. The exposed data included names, email addresses, job titles, employers, work phone numbers, and physical addresses. This combination is particularly sensitive because it links identity to workplace role and contact details in a single record. That bundled profile is directly useful for crafting convincing phishing emails, impersonating colleagues or vendors, and building detailed maps of corporate org structures. No widely reported legal action or regulatory response is associated with this dataset. Because the records were compiled from third-party sources rather than stolen from a single organization, affected individuals may not receive any direct notification. People whose information appeared in this list face an elevated risk of targeted phishing, business email compromise attempts, and unsolicited contact from bad actors who can convincingly reference their employer, title, and workplace details.
What has happened since the breach
B2B USA Businesses did not have a normal corporate lifecycle because it was not a visible standalone business with a public operating identity. Since surfacing in 2017, it has been treated publicly as a legacy spam-list style breach object rather than as an active company that later changed hands, rebranded, or shut down.
What was reported vs. what is circulating
Reported
- Status
- Not yet researched
Listed in breach catalogues
- Breach date
- Jul 2017
- Volume
- Count not yet verified
- Fields listed
- 6email address, employer, full name, job information (job title), phone number, home address
The score is built only on what is listed in circulation.
Every exposed field, and how long it stays useful
| Field | Shelf life | In notice | Listed |
|---|---|---|---|
| Email Address | Lasts for years | No | Yes |
| Employer | Fades over a few years | No | Yes |
| Full Name | Lasts for years | No | Yes |
| Job Information (job title) | Fades over a few years | No | Yes |
| Phone Number | Fades over a few years | No | Yes |
| Home address | Lasts for years | No | Yes |
Shelf life is how long a field stays useful to someone holding it. A password expires fast. A government ID number or a date of birth lasts for years. An address stays useful long after it stops being current.
How attackers can use this data
High risk of spearphishing, executive targeting, and business relationship mapping. The dataset is directly useful for outreach-based fraud and impersonation.
Risks for executives and other high-profile people
A data-broker/identity breach: aggregated identity attributes re-seed broker networks and enrich targeting of the individual. For a high-profile principal this is targeting-grade, not merely identity-theft-grade: the combination lets an adversary locate, impersonate, or pressure the principal with little additional work.
Who is behind this breach
No threat actor has been publicly attributed.
About this record
This is a compilation: a circulating dataset assembled from many sources, not a breach of the organization named. It is scored because the data circulates, whatever its origin. No score is shown until the circulating field list has been audited. Scores come from the Breach Risk Index, which rates what the exposed fields still let an attacker do, not how large the breach was. Breach records change as evidence does. If you hold a notice, a filing or a dataset observation this page does not reflect, report a correction.