All Breaches
February 22, 2023 Verified Sensitive Record Non-bank Lending / Financial Services

HDB Financial Services Data Breach

The 2023 HDB Financial Services service-provider incident was acknowledged by the company as unauthorized access at a provider that processed customer information.

1.7 Million
Email Identifiers
7
Data Types
Critical
Severity
Oct 9, 2026
Last updated

Protect Yourself

Check whether you were affected by this breach

Check my email

Exposed Data Types

7
  • Dates of birth
  • Email addresses
  • Genders
  • Postcodes or geographic information
  • Loan information
  • Names
  • Phone numbers

About This Breach

Reuters and the Economic Times reported on March 7, 2023 that HDB had secured the provider's system and was working with regulators and government authorities. HDB did not then disclose data types or an affected-customer total, and HDFC Bank said its own systems were not affected.

A public breach source separately catalogues a dataset under a February 22 date with more than 70 million customer records and 1,658,750 unique emails. Its classes include names, dates of birth, phones, gender, postcodes or geographic information, and loan information. More than 70 million describes raw or customer-record scale, while 1,658,750 is a unique-email measure. Neither is a confirmed unique-person count or the affected-customer total disclosed by the company.

No dataset or person-level data has been imported locally. The record does not establish that anyone was an HDB customer, applied for a loan, had debt or a financing need, or had phone, birth date, gender, location, and loan fields in the same record. Financial-service associations and these fields must remain private.

Unexpected loan, collection, document-update, or payment requests should be verified through independent official channels. Correct personal or loan details do not authenticate a sender; identity documents, banking details, one-time codes, and advance payments should not be provided in response to inbound contact. Because passwords and payment cards are not among this dataset's normalized classes, the record alone does not require a password change.

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