LBB Data Breach (2019): What Was Exposed & What To Do
SourceBreach data provided in part by Have I Been Pwned, used under CC BY 4.0.
The LBB Data Breach (2019) (reported February 14, 2019) exposed Browser user agent details, Email addresses, IP addresses and Names belonging to roughly 39K people. If you have an account with them, your information may now be circulating on the open web and with data brokers. Here’s exactly what happened, how to check if you were affected, and what to do next.
What happened
The records were posted publicly in August 2022. They included browser user agent details, email addresses, IP addresses, names and physical addresses. LBB reported that it believes the exposure occurred through a third-party service rather than its own systems. The company noted that the dataset contained customer information it holds but had also been enriched with further details from other sources. No official count of total affected individuals beyond the 39,000 unique emails has been confirmed.
How a breach like this happens
Incidents involving third-party services often begin when an external vendor or integration point stores or transmits customer data without adequate segmentation or access controls. Once that environment is accessed, records can be copied and later shared on forums. Enrichment of the data with additional fields, such as device or location details, commonly occurs when multiple sources are combined before or after the initial exposure.
About LBB
LBB, also known as Little Black Book, operates as a lifestyle and shopping discovery platform focused on Indian consumers. Services of this type routinely collect contact information, delivery addresses and device identifiers to facilitate purchases, recommendations and marketing. Exposure of such records is consequential because the data directly identifies individuals and links them to specific locations and online activity patterns.
What was likely exposed
The posted material named browser user agent details, email addresses, IP addresses, names and physical addresses. LBB indicated the dataset combined information it retains on customers with attributes added by the third-party service. The precise scope of any additional fields remains unconfirmed beyond these categories.
The real-world impact
Individuals whose details appeared may receive unsolicited messages or face attempts to use the information for account access elsewhere. Physical addresses and IP data can support more targeted phishing or location-based fraud. For the organisation, the incident highlights risks that arise when customer data is held or processed by external providers whose security posture is not fully visible to the primary service.
If your data was in this breach
Review any accounts that use the exposed email address and change passwords where reuse may exist. Enable multi-factor authentication on services that hold personal or financial details. Monitor statements and delivery notifications for unexpected activity.
- Change passwords on accounts linked to the exposed email.
- Enable multi-factor authentication wherever available.
- Watch for unusual messages or delivery attempts using the listed address.
- Run a free exposure scan of the email address against known breach datasets.
AICompiled with AI assistance from public sources and published under our editorial standards.
How this breach connects
More recent breaches
BtoBet Data Breach (2019)IndiHome Data Breach (2019)Data Enrichment Exposure From PDL Customer Data Breach (2019)The Halloween Spot Data Breach (2019)Latest breaches
Read GalaxyWarden’s full analysis of the LBB Data Breach (2019) →
Verified breach. Breach data provided in part by Have I Been Pwned, used under CC BY 4.0.
Breach listings — particularly those originating from ransomware or leak sites — are third-party claims that may be unverified, incomplete, or inaccurate. A listing does not by itself confirm that a breach occurred or that any specific data was exposed. Severity is an automated assessment, not a definitive rating. Verification status is shown where available.
Attributions to threat groups and methods reflect public reporting and, in some cases, unverified claims made by the groups themselves; they may be incomplete or later revised. Recent Breaches and GalaxyWarden are independent and are not affiliated with, and do not endorse, any company or group named on this page. This information is aggregated from public sources for awareness only and is not legal, security, or investment advice.