Home › Intelligence › Brief
BREACH BRIEF🟠 High Breach

Ualabee Mobility Platform Breaches 472,296 User Records via Unauthenticated Interface

In May 2025 Ualabee’s public interface allowed an unauthenticated scraper to collect 472,296 user records, including emails, names, dates of birth, phone numbers and profile photos. The breach highlights the need for robust access‑control monitoring to satisfy audit and regulatory expectations.

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

Ualabee Mobility Platform Exposes 472,296 User Records

What Happened – In May 2025 the South‑American mobility‑services platform Ualabee allowed an unauthenticated scraper to pull data from a public‑facing interface. The scrape harvested 472,296 unique records containing email addresses, names, dates of birth, phone numbers and profile photos.

Why It Matters for Trust & Control Assurance

  • This incident illustrates a gap in access control and API‑level authorization that continuous‑control programs are built to detect and remediate.
  • Without verifiable evidence that only authorized identities can query personal‑data endpoints, organizations cannot demonstrate a defensible audit trail to regulators or partners.
  • Ongoing monitoring of access logs and automated policy enforcement are essential to prove due‑diligence and maintain trust.

Who Is Affected – Ride‑hailing and mobility‑as‑a‑service providers; their customers in the consumer‑facing mobility sector.

Recommended Actions

  • Conduct an immediate review of all public APIs and UI endpoints for authentication and least‑privilege enforcement.
  • Deploy continuous access‑control monitoring to capture and alert on anomalous data‑exfiltration patterns.
  • Update incident‑response playbooks to include evidence‑preservation steps for API‑level breaches.

Source: Have I Been Pwned – Ualabee breach

Technical Notes – The data was scraped via an unauthenticated HTTP request to a user‑profile endpoint; no CVE is associated. Exposed fields: email, full name, date of birth, phone number, profile photo. Source: same as above

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

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

From the Verisq platform · Trust Operations

Access is where most audits get tested.

Verisq AI Trust Operations maps incidents like this to your access controls and collects the evidence continuously, keeping your trust posture defensible.

See where you'd stand with Verisq AI Trust Operations →