Leak Exposes 1.1M Extremely Private Records

Keep on Guard!

So another data breach, and no surprise here, but another dating site. This time the Leak has exposed 1.1 million customer records, including 15 million private messages sent between users.

Not so private now is it. Leak Exposes 1.1M Extremely Private Records

And no surprise either the entry point for this leak, was the not-so excellent NoSQL database MongoDB which has amazing passwordless defaults and listens on ALL network interfaces rather than binding to localhost.

Sexual preference. Relationship status. Income. Address. These are just some details applicants for the controversial dating site are asked to supply before their physical appeal is judged by the existing user base, who vote on who is allowed in to the “elite” club based on looks alone. All of this, of course, is supposed to remain confidential. But much of that supposedly-private information is now public, thanks to the leak of a database containing sensitive data of 1.1 million users. The leak, according to one researcher, also included 15 million private messages between users. Another said the data is now being sold by traders lurking in the murky corners of the web.

But the information – which now appears to be real user data despite being hosted on a non-production server – was taken by one or more less-than-scrupulous individuals before the lockdown, making it out into the dirty world of data trading this year. That’s according to Troy Hunt, an Australian security expert who runs the website, where people can check if their own information has been leaked in some of the biggest breaches in recent memory, from Adobe to Ashley Madison.

It seems like the records are for sale on the shadier parts of the web and actively being traded by those who trade these kind of things. Fortunately payment details weren’t leaked, and passwords were encrypted.

So it’s a privacy issue more than a financial loss or threat, but as always this kind of info is a goldmine for social engineering, blackmail and identity theft.

Two users confirmed their information was in the leaked database, which also contained encrypted passwords. They shared their entries as found in the database, which showed an entry for descriptions of themselves, revealing more private details about their personal lives. One confirmed the latitude and longitude details were correct, pointing to Cambridge, UK, where they’d signed up., which brags about being “the largest network of attractive people in the world”, has courted controversy in the past by removing thousands of users from the service for not being attractive enough. In 2009, it boasted 1.8 million “ugly people” had been denied access to the site. In 2010, 5,000 were culled after gaining too much weight over a festive break. Last year, weight gain and ageing led to another 3,000 being thrown out.

Today, the company re-sent its original statement on the breach, first received by FORBES in December. “We can confirm we were notified of a breach on December 24th of 2015 of one of our MongoDB test servers. This was a staging server and not part of our production data base. The staging server was immediately shut down.” The company claimed all affected members were informed of “the vulnerability” in December, whilst noting passwords were encrypted and no financial data was exposed.

The user data apparently is only for users that signed up and were active before July 2015, anyone who joined after that shouldn’t be affected.

And yah, be careful with your staging servers – don’t have production data on them unless you absolutely have to (which honestly you don’t). You can mock whatever data structures you need to develop on it.

And don’t use MongoDB.

Source: Forbes

Posted in: Exploits/Vulnerabilities, Privacy, Web Hacking

, , ,

Latest Posts:

Uber Paid Hacker To Hide 57 Million User Data Breach Uber Paid Hackers To Hide 57 Million User Data Breach
Uber is not known for it's high level of ethics, but it turns out Uber paid hackers to not go public with the fact they'd breached 57 Million accounts.
RDPY - RDP Security Tool For Hacking Remote Desktop Protocol RDPY – RDP Security Tool For Hacking Remote Desktop Protocol
RDPY is an RDP Security Tool in Twisted Python with RDP Man in the Middle proxy support which can record sessions and Honeypot functionality.
Terabytes Of US Military Social Media Spying S3 Data Exposed Terabytes Of US Military Social Media Spying S3 Data Exposed
Once again the old, default Amazon AWS S3 settings are catching people out, the US Military has left terabytes of social media spying S3 data exposed.
SNIFFlab - Create Your Own MITM Test Environment SNIFFlab – Create Your Own MITM Test Environment
SNIFFlab is a set of scripts in Python that enable you to create your own MITM test environment for packet sniffing through a WiFi access point.
Skype Log Viewer Download - View Logs on Windows Skype Log Viewer Download – View Logs on Windows
Skype Log Viewer allows you to download and view the Skype history and log files, on Windows, without actually downloading the Skype client itself.
Ethereum Parity Bug Destroys Over $250 Million In Tokens Ethereum Parity Bug Destroys Over $250 Million In Tokens
If you are into cryptocurrency or blockchain at all, you will have heard about the Ethereum Parity Bug that has basically binned $280 Million + ETH.

6 Responses to Leak Exposes 1.1M Extremely Private Records

  1. Mariusz April 28, 2016 at 7:53 pm #

    C’mon, it wasn’t Mongo problem, but a stupid administrator who doesn’t know that default settings are usually not the best choice.

    • Darknet April 29, 2016 at 11:54 am #

      So why is necessary to listen on all interfaces by default? No other DB does that, that would have solved all these problems, binding to localhost by default like every other sane piece of software.

      • unknow April 29, 2016 at 3:01 pm #

        Sorry but by default MongoDB only listening on localhost….

        Stupid SysAdmin =/= Bad Database

        • Darknet April 29, 2016 at 6:31 pm #

          Only recently they’ve fixed that, and that’s not the only problem with MongoDB. Yah it’s an oversight by the sys-admin too, but MongoDB is terrible, we stopped using it in production 4 years ago and haven’t missed it at all.

      • Dave May 2, 2016 at 1:54 pm #

        MySQL listens on all interfaces by default.