Lookbook Data Breach (2012): What Was Exposed & What To Do
SourceBreach data provided in part by Have I Been Pwned, used under CC BY 4.0.
The Lookbook Data Breach (2012) (reported August 24, 2012) exposed Dates of birth, Email addresses, IP addresses and Names belonging to roughly 1.1M 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.
Inside the incident
The breach occurred in 2012. Public records indicate that the organisation became aware of unauthorised access around August of that year. No further technical details, such as the precise method of entry or the duration of access, were disclosed at the time. In June 2016 the same collection of 1.1 million records was offered for sale on an underground forum, containing the data types listed above in plain text where passwords were concerned.
How a breach like this happens
Incidents involving the theft of user account data from online platforms commonly begin with the compromise of a web application or its supporting infrastructure. Attackers may obtain valid credentials through prior leaks, exploit unpatched software, or gain access via third-party services connected to the target. Once inside, they can extract database tables that store authentication material and personal identifiers. When passwords are stored without additional protective measures such as hashing, the extracted files can be used or sold immediately.
Who is Lookbook?
Lookbook operated as a social platform focused on fashion, allowing users to share and discover clothing and style content. Services of this kind routinely collect account credentials, contact information and behavioural data to support user profiles and personalised features. A breach at such a site is consequential because the combination of persistent login details and personal identifiers can remain useful to malicious actors long after the original incident.
What data was at risk
The records offered for sale in 2016 included usernames, email addresses, IP addresses, names, dates of birth, plain-text passwords and website activity logs. The exact scope of any additional fields that may have been present in the original database remains unconfirmed. Organisations in this sector typically store further profile information and interaction histories, yet no authoritative inventory beyond the listed items has been released.
The real-world impact
Individuals whose records were exposed face the possibility that their email addresses and passwords could be tested against other online accounts. Plain-text passwords increase this risk because they require no further processing before use. Dates of birth and names can support identity-verification attempts elsewhere. For the organisation, the later appearance of the data underscored that retained records can surface years after the initial event, affecting user trust and prompting reviews of password-storage practices.
Were you affected?
Anyone who created an account on Lookbook before August 2012 should assume their information may be among the exposed records. Practical first steps include changing passwords on Lookbook and any other sites where the same credentials were reused, and enabling multi-factor authentication where available. Readers can also run a free exposure scan of their email address against known breach datasets to check for appearances in this or other incidents.
AICompiled with AI assistance from public sources and published under our editorial standards.
How this breach connects
More recent breaches
Heroes of Newerth Data Breach (2012)BookCrossing Data Breach (2012)Netlog Data Breach (2012)The Botting Network Data Breach (2012)Latest breaches
Read GalaxyWarden’s full analysis of the Lookbook Data Breach (2012) →
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.