OnlineBloodBank Alleged Data Exposure
The 2018 OnlineBloodBank data breach occurred in January 2018 when the MongoDB database of OnlineBloodBank (onlinebloodbank.com), an Indian national blood donor registry and voluntary hospital coordination network, was compromised and exfiltrated.
Exposed Data Types
1 sensitive8- Health and medical records
- Email addresses
- Names
- Phone numbers
- Physical addresses
- Dates of birth
- Genders
- Geographic locations
About This Record
What information was affected in the OnlineBloodBank incident?
The leaked NoSQL export (onlinebloodbank.com_22012018.json) encompasses 1,128,031 voluntary donor records, exposing:
- Protected Health & Medical Data: Donor blood types and Rh factors (blood_group_name), donor classification (donor_type_name), and affiliated hospital / blood bank names (bb_name).
- Identity & Demographic Details: Full donor names, birth dates, and genders.
- Contact Coordinates & Physical Geolocation: Mobile phone numbers, permanent residential addresses, district names, and state jurisdictions across India.
- Email Identifiers: Canonical valid email addresses for the 646 donors who supplied email contacts.
Note: This registry database contains voluntary donor medical intake forms rather than authentication passwords.
How many accounts were affected?
Out of 1,128,031 total donor records, canonical RFC extraction confirmed 646 unique valid email addresses.
Technical analysis and security risks
The unauthorized dissemination of medical blood group categorizations combined with personal contact telephone numbers facilitates targeted healthcare-related social engineering, false emergency scams, and unsolicited telemarketing.
Recommended actions for affected individuals
Donors registered with OnlineBloodBank should:
- Remain watchful against unsolicited communications requesting financial contributions or personal verification under the pretext of blood donation emergencies.
- Verify any hospital or blood bank requests through established official medical channels.
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
