Home › Intelligence › Brief
BREACH BRIEF🟠 High Breach

Bukalapak Exposes 13.4 M User Accounts in 2019 Backup Breach

Bukalapak disclosed that backups dating back to 2017 were accessed, leaking 13.37 million email addresses, IPs, names and password hashes. The incident underscores the importance of encrypted, monitored backup controls for audit readiness.

LiveThreat™ Intelligence · 📅 October 08, 2026· 📰 haveibeenpwned.com
🟠
Severity
High
BR
Type
Breach
🎯
Confidence
High
🏢
Affected
1 sector(s)
✅
Actions
3 recommended
📰
Source
haveibeenpwned.com

Bukalapak Exposes 13.4 M User Accounts in 2019 Backup Breach

What Happened — In March 2019 the Indonesian e‑commerce platform Bukalapak disclosed that backups taken as early as October 2017 had been accessed by an unauthorized party. The breach released roughly 13.37 million unique records, including email addresses, IP addresses, names, usernames and password hashes (bcrypt and salted SHA‑512).

Why It Matters for Trust & Control Assurance

  • Demonstrates the risk of insufficient backup protection—a scenario continuous control‑assurance programs are built to detect, document, and remediate.
  • Highlights the need for immutable, encrypted backup storage and auditable evidence that backup handling complies with data‑protection controls.
  • Provides a concrete example of why organizations must map backup‑related safeguards to a single control objective (e.g., “Data Protection – Secure Storage”) that satisfies multiple frameworks.

Who Is Affected — Retail/e‑commerce operators and their customers, particularly those in Southeast Asia.

Recommended Actions

  • Verify that all backup repositories are encrypted at rest and enforce strict access controls.
  • Implement continuous monitoring and logging of backup creation, modification, and access events to produce defensible audit evidence.
  • Map your backup‑security controls to the relevant VCF control objective (Secure Data Storage) and assess coverage across frameworks such as NIST CSF 2.0 or ISO 27001.

Technical Notes — The breach stemmed from exposure of backup files; no public vulnerability (CVE) was disclosed. Passwords were stored as bcrypt and salted SHA‑512 hashes, limiting immediate credential reuse but still representing sensitive credential material. Source: Have I Been Pwned – Bukalapak breach

📰 Original Source
https://haveibeenpwned.com/api/v3/breach/Bukalapak ↗

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

From the Verisq platform · Trust Operations

Answer one control objective. Answer ten frameworks.

The Verisq Common Framework is a spine of 84 control objectives that SOC 2, ISO 27001, NIST CSF, CMMC, HIPAA, PCI DSS, HITRUST, GDPR, ISO 42001 and NIST AI RMF map onto — each graded honestly. Satisfy an objective once and every framework that recognizes it lights up at its real strength.

See how the Verisq Common Framework works →