Profile picture
Troy Hunt @troyhunt
, 11 tweets, 3 min read Read on Twitter
This one is obviously a real mess and deserves some more background so let me share what I know:
Firstly, they've acknowledged the breach and taken the sites down pretty promptly once we managed to get through to them. Here's their disclosure on the root of their site (link to a "safe for work" archive version): web.archive.org/web/2018102018…
But there are multiple inaccuracies, the first being the disclosure date which was 3 days earlier than represented. Here's the first attempt I made to a published address of theirs:
Further, I believe their use of the term "security reseacher" [sic] refers to the person who sent the data to me; I didn't download any info from the service, merely confirmed the presence of accounts in the breach by attempting to register with Mailinator addresses in there
They also said that someone was able to "exploit a script we use" which referred to an easily discoverable SQL injection vulnerability which may have been the vector used to pull the data. I agree with their assertion that others may also have found this vulnerability.
Passwords were not encrypted, they were hashed with DEScrypt. Yes, I know that can be a bit semantic in a breach notification but it's important as it provides next to no protection at all. @jmgosney explains:
Then there's the nature of the site: the public face of it had a bunch of guys posting naked photos of their wives with others chiming in and providing their own commentary on the pics (use archive.org if you're really curious). This raises 2 really big issues:
The obvious one is consent: it's hard to imagine these were all shared consensually. Maybe some were and it's just folks in very open relationships, who knows, but it was certainly the first thing that came to my mind.
The other big issue is that this breach discloses the identities of many of the people posting these photos under the veil of anonymity. I took the most recent post at the time titled "Like to bone my wife" and mapped the public username to the private email in the breach...
Minutes later I had a real name, where he lived, his Instagram account and other very personally identifiable information about the person. People *very* frequently use their own addresses for these services which makes mapping them to "anonymous" identities dead simple.
And that's pretty much everything I know, feel free to ask questions if there's anything I missed.
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to Troy Hunt
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member and get exclusive features!

Premium member ($30.00/year)

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!