Analysis Of Leaked NASA Passwords

NASA has yet again been hacked and their data leaked. The data can be found as a list of accounts or a full SQL dump with a size of 6.6Gb. The leak contains a total of 444 passwords.

No passwords were cracked as the passwords were in cleartext.

The Results

Length distribution
 
Average password length: 8,479729

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
ERA2011 9
Nasa1234 8
llama 5
green 5
bd122253 5
dixie777 4
Jud4532 3
password 3
Mar0ngelli 3
12345 3
123456 3
Wes&Jo4Ever 2
mdjwaj35 2
Nicole12 2
VDkiwilander 2
Nasalarss08 2
Matt1q!Q 2
chs12345 2
vote 2
keithwa 2
!QAZ1qaz 2
reset123 2
letmein 2
abc123 2
test 2
amsco86 2
1dragon 2
firstship1 2
nasa1234 2
iitdreamer1 2

Top 30 longest passwords


Password Length
$kF9(8{pc%{^6Cn3v4N28,3@&@43qt 30
henry.p.russell@nasa.gov 24
Hopemontcircle358 17
2vote4vid@LaRC! 15
Club123Club123! 15
JupiterPl@net5 14
PortWarwick12* 14
c,=$*06iT~gPht 14
JacksonHole690 14
samanapatiala 13
Tni2wg22@1234 13
Endwave!@#123 13
blackpearl007 13
varshavarsha1 13
peashooterP26 13
BlueMoon#8354 13
Shummies@5272 13
vreauCosmin13 13
greenaviation 13
123Mic=hel123 13
Kokalolloms86 13
shadow5714(4) 13
Steve@123456# 13
Wallflowers#1 13
Funvegas2009! 13
Tiff20045467! 13
VotesCount123 13
prasannakumar 13
Ymqcaadp#1232 13
nMPPOle^ed042 13

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