Bonobos Data Breach (2020): What Was Exposed & What To Do
SourceBreach data provided in part by Have I Been Pwned, used under CC BY 4.0.
The Bonobos Data Breach (2020) (reported August 14, 2020) exposed Email addresses, Historical passwords, IP addresses and Names belonging to roughly 2.8M 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.
Breaking down the breach
The breach was identified through data provided to Have I Been Pwned by dehashed.com. Public reporting at the time stated that the dataset contained 2.8 million unique email addresses along with the additional categories of information listed above. No further details on the method of access, the precise date of the intrusion, or the duration of unauthorized access have been disclosed in available records.
How a breach like this happens
Incidents involving large volumes of customer records from retail systems commonly occur when an attacker obtains access to a database or backup storage. This can result from remote exploitation of server software, compromised administrative credentials, or misconfigured access controls that leave data repositories reachable from the internet. Once inside, an actor can copy entire tables or file directories, which explains the presence of both current and historical password hashes as well as partial payment information that many retailers retain for order processing.
Who is Bonobos?
Bonobos operates as an apparel retailer serving customers through an online store and physical locations. Like other companies in this sector, it collects and stores personal details required for order fulfillment, account management, and payment processing. A breach at such an organization is consequential because the data it holds directly links individuals to transactional histories and contact information that can be reused across other services.
What was likely exposed
The reported dataset included the following categories of information:
- Email addresses
- Names
- Physical addresses
- Phone numbers
- IP addresses
- Passwords stored as salted SHA-512 hashes, including historical passwords
- Partial credit card data consisting of card type, name on the card, expiry date, and the last four digits
Exact confirmation of every record contained in the 70 GB archive remains limited to these reported fields.
Why it matters
Exposure of email addresses and passwords, even when hashed, increases the chance that individuals will encounter credential-stuffing attempts on other websites where the same login details were reused. Partial credit card information combined with names and addresses can facilitate targeted fraud attempts, though the absence of full card numbers limits certain forms of immediate misuse. For the organization, the incident highlights the long-term retention of historical password data and the storage of payment details that together expand the potential impact on customers.
Were you affected?
Individuals can check whether their email address appears in known breach datasets by using a free exposure scan service. Practical next steps include changing passwords on the Bonobos account and any other sites that share the same credentials, enabling multi-factor authentication where available, and monitoring bank or credit card statements for unauthorized activity. Organizations that have not already done so should review password storage practices and limit retention of payment information to what is strictly necessary.
AICompiled with AI assistance from public sources and published under our editorial standards.
How this breach connects
More recent breaches
MEO Data Breach (2020)NetGalley Data Breach (2020)MMG Fusion Data Breach (2020)DriveSure Data Breach (2020)Latest breaches
Read GalaxyWarden’s full analysis of the Bonobos Data Breach (2020) →
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.