Compilation · Aggregated cryptocurrency-user breach dataset · Multi-source re-indexed exposure dataset targeting crypto account holders · Global

Have I Been Drained (HIBD) Data Breach (2025)

Aggregated cryptocurrency-user breach compilation assembled from multiple prior incidents and marketed as a targeting dataset for crypto holders

Pilot record · BRI 2.0 results pending
Breach Risk Index
LowGuardedElevatedHighSevere
Not yet scored
Circulation not yet audited
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 →

Data sensitivity
Sensitive

Includes data that locates or profiles a person, beyond contact details.

Volume
Count not yet verified
Field types
4 listed
Breach date
Mar 2025
Attributed
Unknown (aggregator)
Vector
Scraping / Collection
How it unfoldedListed the same month as the breach
  1. Breach
  2. Listed in breach catalogues
What came out

What data was exposed

Account BalanceFinancial
Email AddressContact
Full NameIdentity
Phone NumberContact
Red cannot be reissued or taken back · Blue is the residence · Black is movement, where you go rather than where you live · Grey is high-signal data that is not standard breach material · Field list from breach catalogues, not yet verified
What it enables

How this data can be used against you

Assessed once the record is scored.

What you should do

Three key actions to take

Add a verbal password at your bank and brokerage

Ask each one to require it before any change made by phone.

Lock your mobile number

Ask your carrier for a port-out PIN so no one can move your number to a new phone.

Treat messages about Have I Been Drained (HIBD) with care

Do not act on a call, email or text about this breach. Contact Have I Been Drained (HIBD) using a number you already have.

Check it yourself

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.

HackNoticeRuns on HackNotice · ObscureIQ never sees the address you check
Run the Instant Check →
If this matters to you

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 →
Full record · 8 sections

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
  • Reported and circulating
  • Data points exposed
  • Downstream risk
  • Principal risk advisory
  • Threat actor
  • Background
  • Data context
No sign-in · nothing is recorded
What happened

How this breach happened

"Have I Been Drained" is a compilation of about 13.5 million cryptocurrency-user records aggregated from multiple prior incidents and circulated as a targeting dataset. It pairs names, email addresses, and phone numbers with account-balance information, making it especially useful for targeting crypto holders.

Reported and circulating

What was reported vs. what is circulating

The company's notice

Reported

Status
Not yet researched
Not yet verified by ObscureIQ

Listed in breach catalogues

Breach date
Mar 2025
Volume
Count not yet verified
Fields listed
4account balance, email address, full name, phone number

The score is built only on what is listed in circulation.

Data points exposed

Every exposed field, and how long it stays useful

FieldShelf lifeIn noticeListed
Account BalanceExpires fastNoYes
Email AddressLasts for yearsNoYes
Full NameLasts for yearsNoYes
Phone NumberFades over a few yearsNoYes

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.

Downstream risk

How attackers can use this data

Because it is aggregated and balance-aware, presence signals a crypto holder has been profiled for targeting; mitigation is heightened phishing/SIM-swap vigilance rather than action against one company.

Principal risk advisory

Risks for executives and other high-profile people

A financial-institution breach: account, wealth or payment data supports direct fraud and highly credible financial-impersonation scams. For a high-profile principal the main risk is credible impersonation and enrichment of existing exposure.

Threat actor

Who is behind this breach

Attributed to Unknown (aggregator).

Background

About the company

"Have I Been Drained" is not a company but an aggregated dataset of cryptocurrency users, compiled from multiple prior breaches and marketed as a targeting list for crypto holders.

Data context

Why the company holds this data

This dataset is best understood as a cross-platform compilation of user records drawn from multiple cryptocurrency-related services, including exchange, portfolio, token, and crypto-adjacent platforms. The reported fields include email addresses, phone numbers, full names, wallet addresses, IP or location data, account balances, and in some descriptions KYC-related status or transaction-linked details, making it a stitched identity-and-asset mapping dataset rather than the native customer database of a single company

Unknown (aggregator)Scraping / CollectionCybercrime & CompilationsData CompilationNo single organization2025

About this record

No reported total is on record for this breach. No count has been verified for this breach yet. Figures in older breach catalogues are not shown until they are checked against the data. 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.

ObscureIQ · Circulating breach record How the Index works · Contact MMXXVI