DailyObjects Data Breach (2018)
If you are a customer of DailyObjects, here’s what’s now in circulation.
In approximately January 2018, a collection of more than 464k customer records from the Indian online retailer DailyObjects were leaked online. The data included names, physical and email addresses, phone numbers and "pincodes" stored in plain text. After multiple attempts to contact them, DailyObjects responded and received a copy of the data for verification, however failed to respond to multiple contact attempts following that.
DailyObjects customer?
See what’s already exposed about you — free, 15sWe check your email against known public breach records and the sites that publish your address, then show you what to do about each one. We don’t hold this company’s data. No account, no card.
What the free scan actually returns
Found on people-search siteswe remove these
These listings are live, public, and legal to remove — and removing them is what we do.
Found in breach recordsverifiedreported — unverified
Each record is labeled: confirmed breach data, or an attacker’s claim no one has verified.
Leaked data cannot be deleted from the internet — anyone claiming otherwise is lying. Broker listings can be removed. We do the second, and show you exactly what to fix from the first.
For security and vendor-risk teams: a staff address in a leak does not mean you were breached — it usually means a third party was. We monitor a domain against 13.1B+ leaked records and tell you when one of your people appears. See what we would check →
Report details & sourcing
Related breaches
Dubsmash — 162 Million Accounts Sold in a Job Lot (2018)
The video-messaging app used PBKDF2, one of the better choices on this list. Its data still ended up…
MyFitnessPal — 144 Million Accounts, and Whether Yours Was Safe Depended on When You Joined (2018)
MyFitnessPal used SHA-1 for older accounts and bcrypt for newer ones. Whether your password survived…
Exactis — 340 Million Records of Profiling Data Nobody Consented To (2018)
A marketing data broker left an ElasticSearch node exposed with no firewall. It held about 340 milli…