Analysis Of The XboxLiveClans Leak

XboxLiveClans was hacked by a hacker with the alias alsa7r. Their database was leaked with a total of 94 columns. A total of 34501 users reside in the database. The password hashes are salted with a dynamic sized salt that is also contained in the database.

No passwords were cracked. 21002 cracked passwords were leaked by the hacker.

The Hash Function

The hacker talks about the hash function being md5(md5($pass).md5($salt)), however, I have not been able to confirm this. The description of the hash function, given by the hacker, is vague and filled with spelling errors, which only complicates the cracking of the hashes.

The Results

Length distribution
 
Average password length: 7,99123893

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 140
password 106
123456789 91
xbox360 49
abc123 47
7uGd5HIp2J 46
ike02banaA 40
football 39
qwerty123456 30
qwerty 29
baseball 29
monkey 28
111111 26
timosha 26
xboxlive 25
Russian1 24
asDGVy3898 23
eqeS606898 23
ZVjmHgC355 23
liverpool 21
killer 21
skills12 20
hockey 20
arsenal 20
Russian7 18
cheese 18
qq123456 18
master 18
Bigman12131 17
Blabla159 16

Top 30 longest passwords

Password Length
Moneymaker87654321 18
JXthtnmrjdflbv1 15
takenoprisoners 15
123123123123123 15
dynastywarriors 15
sklifsupermudak 15
moneymoneymoney 15
johnnyknoxville 15
celtic6rangers2 15
godblessamerica 15
monkeybusiness 14
smallville1987 14
Czechoslovakia 14
mightymariner1 14
hjgjfvgjcdgjdj 14
drujokbyviagra 14
dragonslayer12 14
77obafanovka77 14
liverpoolfc123 14
newpassword123 14
u0HgtKt617bvfd 14
blackandyellow 14
CtNI3F97ullian 14
lkfdjkfjkdfdgg 14
5435idaeinthis 14
thekingofkings 14
electricguitar 14
masterchief117 14
bloodyknuckles 14
westviewgold11 14

Comments

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