Skip to content
Ledger Data Breach Exposes 272,000 Customer Records

Ledger Data Breach Exposes 272,000 Customer Records

First seen 25 Oct 2026, 13:12 UTC •
API

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •October 25, 2026 at 15:14 UTC
  • •272,000 customer records exposed in a recent data dump.
  • •Breach traced to unauthorized access via an API key.
  • •Ongoing phishing campaigns targeting affected customers.

Ledger confirmed a data breach involving its e-commerce database, initially reported in July 2020. A recent dump on Raidforum revealed approximately 272,000 records containing detailed personal information, including names, postal addresses, and phone numbers. The breach was traced back to unauthorized access via an API key, which has since been deactivated. Initially, Ledger reported that around 1 million email addresses were compromised, with 9,532 customers' detailed information identified. The company expressed regret over the incident and acknowledged ongoing phishing campaigns targeting affected customers. Ledger is committed to transparency and has informed all customers about the breach.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated just now How this analysis works

Timeline

2020-06-25
Unauthorized access confirmed
An unauthorized third party accessed Ledger's e-commerce and marketing database through an API key.
Ledger
2020-07-14
Breach reported by researcher
A researcher in Ledger's bounty program alerted the company about a potential data breach.
Ledger
2026-10-24
Data dump released on Raidforum
A dump of Ledger's customer database was released, revealing a larger subset of detailed personal information.
Ledger

More articles in this cluster (2)

Following this threat?

Track Ledger in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Extracted Entities (5)

1 / 4

Common questions

What information was leaked?
The breach exposed approximately 272,000 records with names, postal addresses, and phone numbers, in addition to 1 million email addresses.
How did the breach occur?
The breach was caused by unauthorized access through an API key, which has since been deactivated.
What actions is Ledger taking?
Ledger is informing affected customers and has expressed regret over the incident, emphasizing their commitment to transparency.