Analysis Of Leaked MilitarySingles.org Passwords

This time I take a look at an interesting leak: MilitarySingles.org. They are operated by ESingles Inc. and they claimed that they had not been hacked by the notorious LulzSec hacker group. They assured their customers that the site had not been hacked and they claimed that "All user passwords in our database are encrypted and secure.". The rest of the story can be seen at databreaches.net.

It turns out that the passwords, despite what ESingles said, was not encrypted nor secure. They are unsalted MD5 hashes and combined with a weak password policy, almost all of the hashes were cracked within a few minutes.

A total of 163.792 hashes were leaked and 151.791 (92.2%) of them were cracked in 9 hours.

The Results

Length distribution
 
Average password length: 7,427

Character distribution
 

Unique character distribution


Contained in common wordlists
 

Contained in IQ wordlist (Click here for more info)


Top 30 most common passwords

Password Frequency
123456 763
password 415
iloveyou 177
military 165
sunshine 152
princess 146
ranger 131
marines 128
michael 118
12345678 118
love 113
marine 110
123456789 110
jennifer 109
tigger 100
loveme 99
freedom 98
michelle 97
ashley 97
justin 95
single 94
jessica 94
airborne 93
fuckyou 93
nicole 89
football 87
1234 82
matthew 81
monkey 81

Top 30 longest passwords

Password Length
chocolatemint12 15
iloveallmy4kids 15
Septembergirl13 15
restoration2010 15
alwayslovingyou 15
salveregina1988 15
plastickitten58 15
123456789101112 15
screamingeagles 15
whiskeygirl2012 15
pharmaceuticals 15
philippines2012 15
catherine102484 15
airforcegirl711 15
loveme163456123 15
schoolofrock123 15
hannahjones1989 15
youllneverguess 15
ctxcolormonitor 15
flexiblecouch10 15
1cutestrawberry 15
destinyschild20 15
coloradosprings 15
rockfordfosgate 15
americansingles 15
danielradcliffe 15
kimberly1234567 15
Fuckyourself007 15
POPOCATEPEL1978 15

Bonus: Virtualization of the common passwords

Comments

Anonymous said…
Ha lol ... great post ... In da face
April 1, 2012 at 2:53 PM

Post a Comment

Popular posts from this blog

.NET Compression Libraries Benchmark

Image
I often find myself needing a compression library in a software development project, and after a few tests with disappointing results I usually fall back to spawning 7Zip as an external process. This time however, the application specification prohibits any data written to disk, which 7Zip needs to do in order to work correctly. I needed to do everything in memory, and so I had to test some of the C# libraries available for compression as well as the different compression algorithms. Here is a full list of the tested libraries: .NET DeflateStream ICSharpCode SharpZip Zlib.NET DotNetZip Managed LZMA LZMA SDK QuickLZ    Compression 101 Before I get to the results of the benchmark, I think it is important to understand the different archive formats and compression algorithms in order to compare the results with other benchmarks/and or tests. Lets get to it! A compression algorithm can be compared to a small machine that takes in some data, do some math on it and transfor
Read more

Reducing the size of self-contained .NET Core applications

Just for note keeping, I've written down some methods of reducing the size of a .NET Core application. I thought others could use it as well, so here you go. Original Size First off, let's see how much disk space a self-contained 'hello world' application takes up. > dotnet new console > dotnet publish -r win-x86 -c release Size: 53.9 MB -  yuck! Trimming Microsoft has built a tool that finds unused assemblies and removes them from the distribution package. This is much needed since the 'netcoreapp2.0' profile is basically .NET Framework all over again, and it contains a truckload of assemblies our little 'hello world' application don't use. > dotnet new console > dotnet add package Microsoft.Packaging.Tools.Trimming -v 1.1.0-preview1-25818-01 > dotnet publish -r win-x86 -c release /p:TrimUnusedDependencies=true Size: 15.8 MB Much better! Although, we have only removed unused assemblies - what about unused
Read more

Convex polygon based collision detection

Image
A lot of people have asked me: Why use a convex polygon only engine like Box2D? In this post I will provide some info on why convex polygons is the optimal polygon type to use. What does convex mean? Convex polygons needs to satisfy the following requirements: All internal angles must be below 180 degrees Every line segment between two vertices can be contained fully inside or at the edge the polygon A non-convex polygon is called a concave polygon and it must have an internal angle measuring greater than 180 degrees. As you might have thought about yourself; concave polygons can be quite handy. Convex-only engines can’t represent a simple player polygon like Pac-Man . Why use convex-only? There are really only one big juicy reason: performance Physics engines are able to take quite a few shortcuts and use cheap algorithms to determine the closest vertex, shortest distance and a lot more. An algorithm like Separating Axis Theorem and the Gilbert – Johnson –
Read more