Friendfinder and their brands are run by Andrew Conru. They're quite successful; they own Penthouse. At one point he tried to buy Playboy, but Hefner wouldn't sell. They don't really have 300,000,000 accounts; there's been litigation over their fake accounts. It's probably going to turn out to be like Ashley Madison, where over 95% of the female accounts were fake.
They had a breach last year, but it wasn't as big.[1]
"the hashed passwords seem to have been changed to all lowercase before storage". I have no words to describe how idiotic this is. How do people come up with this and still get paid?
This would mean that 80% of the Dutch adult population has an Adult Friend Feinnder account!?
(Of course people may have multiple accounts, but still, 80% is when taking into account the full (men+women) population.)
The first estimate I see of worldwide Dutch speakers is ~23 million[0]. There's over 5 million Dutch speakers (Flemish) in Belgium alone.
So you're looking at somewhere between 15-20% of Dutch speakers have accounts, which seems more reasonable, particularly if some people have more than one account (very likely, I'm guessing).
Simple. Most accounts are fake. The thing with AFF is that it's paying top dollars in affiliate programs. So everyone and their dog are building a fake profile to lure some naive guys into buying a subscription.
When I moved to NL I was surprised to hear swinger/secret affair advertisements on the radio. I think a higher-than-average percentage of the Dutch population uses those sites compared to the US
> How did it happen? They were hacked via a Local File Inclusion exploit and you can read more about the situation when it was initially reported from this link.
> LFI vulnerabilities allow an attacker to include files located elsewhere on the server into the output of a given application.
How did they do that ? append /../../../etc to an url that is supposed to serve a file and hope the server doesn't check for directory traversal ?
Adding &some_url_parametr=../../../etc/passwd (or ../../../var/uploads/evil_script.txt) allows you to insert arbitrary text file from the server into the generated HTML or execute arbitrary PHP code (which in turn can even run arbitrary shell commands if this is enabled on the server).
Since PHP has such feature, people use it and to this day you'll occasionally run into a website which employs this pattern. Common use case is
bad-example.com/article.php?id=article_name.txt
where article.php contains headers, footers, formatting, etc and actual articles are stored in text files.
IMO, if you're checking the URL for directory traversal it's already too late. Whenever I build a server that serves files, I maintain a whitelist set of served files, and the first thing I do in the file request handler is check if the URL is in the set. If not, immediately drop to 404. There's too much that can go wrong with trying to sanitize inputs; it's better to rule out the possibility of unsanitized data by design. There's more than one approach to this, and none of them admit directory traversal.
That's one possibility. Another common flaw is upload/download features, where you can get directory traversal (../) in the upload or download file name that you are specifying.
I feel this is a defeatist stance to take; LFI's are a solved problem and we should be looking to how and why this happened and prevent it in the future.
Another angle: we're supposed to not do anything that requires any form of confidentiality online? can't book a doctors appointment, transfer money, send emails to family?
The internet is becoming too important to our lives, we can't just say "presume everything is public"
Your advice means that someone should refuse to visit a doctor or hospital which uses computers, since "I have to act like everything online could be public!". That's just unworkable.
> Friend Finder Network Inc is a company that operates a wide range of 18+ services and was hacked in October of 2016 for over 400 million accounts representing 20 years of customer data which makes it by far the largest breach we have ever seen
They didn't see the Yahoo break with 500m accounts?
Also, why is "pakistan" such a popular password? Deployed soldiers?
As a pakistani, that cracked me up. We are at the top of the list of porn searching countries, I think ( http://tribune.com.pk/story/823696/pakistan-tops-list-of-mos... ) and porn sites often have AdultFriendFinder ads, so it is possible that a pretty large number of pakistani people signed up. (Assuming there's a free sign up)
So I have always wondered this, but what is the most common way to realize that your data was hacked? Is it from very careful monitoring of connection logs? Do hackers typically leave notes and/or obvious traces? Do you start to notice your stored information online (possibly for sale) in sketchy places? Do specifically your customers start getting spam?
If you're being proactive about it, one approach is to create "canary" accounts: single purpose email addresses that signup for your service and nothing else. When those email addresses start getting spam, it's a strong indicator your database has been accessed.
Many users signup for each online service with a single-purpose email address. e.g. <servicename>@uniquedomain.com, so many customers will often know of a leak as soon as the service provider does.
At the last company I worked for, we discovered an intrusion when we started getting a ridiculous number of credit card fraud complaints. It should be noted that we sold scientific instrumentation to other small companies and rural markets so it was pretty easy for them to figure where their info got stolen from when they only used their cards for infrequent transactions.
99.3% of all passwords from this website are now plaintext (cracked).
As someone who cares about security, this is very, very painful to read. But it also makes me curious about that password data set. It might be used for security research, like estimating the entropy of passwords more accurately.
It definitely shows how terrible people are at password generation and reuse but even more so how little it matters on individual sites if those folks have no understanding or don't care about protecting passwords. Yet people keep using 123456 as a password.
I often store my password using PHP's password_hash('password', PASSWORD_DEFAULT) function. This function has been baked into the language since version 5.0 I think. I'm sure most other languages must have a similar function too, yet so many sites save the password in plain text. Doesn't make any sense.
Major props to Anthony https://github.com/ircmaxell for adding this as a language supported feature to PHP as well for his work on techniques for preventing injection.
I work with C#, Java, Python Go and JS on backends a lot and no other language I worked with had such a simple but secure API.
I would be interested to see if it is possible to work out what percentage of the profiles are fake/bots from the data leaked. Is that possible or would they simply blend in too easily?
It would probably be difficult to prove with certainty, but depending on what the passwords are, you could potentially be able to do something like that. For example, if there are enough accounts that have the same password (which is also relatively unique), then at some point it will be a statistical impossibility that they were all created by different people.
tl;dr: Last months AdultFriendFinder.com, Cams.com, Penthouse.com, Stripshow.com, iCams.com databases in a "statistics" advertisement for leakedsource.com's services.
I'm guessing they got an exclusive on that one. Want to ramp up the PR machine before delivering the goods. They'll drop it when everyone's excited enough. I doubt they care about privacy, the whole point of their service is/was not caring about it (as opposed to haveibeenpwned).
They say the hashes were peppered. What does that mean? If it's similar to a unique salt per user, I find it hard to believe they could crack that many very strong looking passwords.
I don't see how that helps anyone when a technical person can trivially setup a search, and a non-tech person could pay someone a small sum to do the same.
If we could use a different identifier (like email address) for every website such hack would not be a problem. Or if we used a hardware key without email address.
[+] [-] Animats|9 years ago|reply
They had a breach last year, but it wasn't as big.[1]
[1] http://www.ibtimes.com/adult-friend-finder-dating-site-known...
[+] [-] coldcode|9 years ago|reply
[+] [-] catoc|9 years ago|reply
This would mean that 80% of the Dutch adult population has an Adult Friend Feinnder account!? (Of course people may have multiple accounts, but still, 80% is when taking into account the full (men+women) population.)
[+] [-] jnbiche|9 years ago|reply
So you're looking at somewhere between 15-20% of Dutch speakers have accounts, which seems more reasonable, particularly if some people have more than one account (very likely, I'm guessing).
0. http://www.ucl.ac.uk/atlas/dutch/who.html
[+] [-] elorant|9 years ago|reply
[+] [-] anc84|9 years ago|reply
[+] [-] jj89|9 years ago|reply
"15-24 years: 12.11% (male 1,050,889/female 1,010,596) 25-54 years: 39.83% (male 3,400,998/female 3,377,311)"
[+] [-] cbcoutinho|9 years ago|reply
[+] [-] TazeTSchnitzel|9 years ago|reply
Belgians?
[+] [-] c3534l|9 years ago|reply
[+] [-] aikah|9 years ago|reply
> LFI vulnerabilities allow an attacker to include files located elsewhere on the server into the output of a given application.
How did they do that ? append /../../../etc to an url that is supposed to serve a file and hope the server doesn't check for directory traversal ?
[+] [-] qb45|9 years ago|reply
Since PHP has such feature, people use it and to this day you'll occasionally run into a website which employs this pattern. Common use case is
where article.php contains headers, footers, formatting, etc and actual articles are stored in text files.[+] [-] wyager|9 years ago|reply
[+] [-] tetrep|9 years ago|reply
When you've got file read, procfs is very nice :)
[+] [-] bitJericho|9 years ago|reply
[+] [-] aliakhtar|9 years ago|reply
[+] [-] peter303|9 years ago|reply
[+] [-] wepple|9 years ago|reply
Another angle: we're supposed to not do anything that requires any form of confidentiality online? can't book a doctors appointment, transfer money, send emails to family?
[+] [-] dredmorbius|9 years ago|reply
https://medium.com/message/hello-future-pastebin-readers-39d...
Norton's law: Over time, all data approaches deleted, or public.
[+] [-] unknown|9 years ago|reply
[deleted]
[+] [-] inostia|9 years ago|reply
[+] [-] rmc|9 years ago|reply
The internet is becoming too important to our lives, we can't just say "presume everything is public"
Your advice means that someone should refuse to visit a doctor or hospital which uses computers, since "I have to act like everything online could be public!". That's just unworkable.
[+] [-] perlgeek|9 years ago|reply
They didn't see the Yahoo break with 500m accounts?
Also, why is "pakistan" such a popular password? Deployed soldiers?
[+] [-] aliakhtar|9 years ago|reply
[+] [-] varjag|9 years ago|reply
[+] [-] kimshibal|9 years ago|reply
[+] [-] asafira|9 years ago|reply
[+] [-] rarrrrrr|9 years ago|reply
Many users signup for each online service with a single-purpose email address. e.g. <servicename>@uniquedomain.com, so many customers will often know of a leak as soon as the service provider does.
[+] [-] zombees|9 years ago|reply
[+] [-] Kenji|9 years ago|reply
103,070,536 passwords already plainly visible
232,137,460 passwords hashed with SHA1
99.3% of all passwords from this website are now plaintext (cracked).
As someone who cares about security, this is very, very painful to read. But it also makes me curious about that password data set. It might be used for security research, like estimating the entropy of passwords more accurately.
[+] [-] olegkikin|9 years ago|reply
[+] [-] coldcode|9 years ago|reply
[+] [-] supersan|9 years ago|reply
[+] [-] inglor|9 years ago|reply
I work with C#, Java, Python Go and JS on backends a lot and no other language I worked with had such a simple but secure API.
[+] [-] stephenr|9 years ago|reply
[+] [-] merb|9 years ago|reply
well the biggest problem is probably generating a truly random salt with SecureRandom, which will slow down your program if used incorrect.
[+] [-] have_faith|9 years ago|reply
[+] [-] CoryG89|9 years ago|reply
[+] [-] dredmorbius|9 years ago|reply
Yes. Again:
This event also marks the second time Friend Finder has been breached in two years, the first being around May of 2015.
Data are liability.
[+] [-] inostia|9 years ago|reply
The interesting thing to me is that password choices clearly reflect the demographic of the users.
[+] [-] anc84|9 years ago|reply
[+] [-] encoderer|9 years ago|reply
[+] [-] auganov|9 years ago|reply
[+] [-] Buge|9 years ago|reply
[+] [-] unknown|9 years ago|reply
[deleted]
[+] [-] lemming|9 years ago|reply
[+] [-] mitchh|9 years ago|reply
[+] [-] chomp|9 years ago|reply
[+] [-] WhitneyLand|9 years ago|reply
I don't see how that helps anyone when a technical person can trivially setup a search, and a non-tech person could pay someone a small sum to do the same.
[+] [-] codedokode|9 years ago|reply