AxEWS9rg5V
This is the sha1:
caf28fcc9c3e4d88b830b8e5cc52c5b65d3db5f4
It is found in Line 3612910 of combo_not.txt. I believe the file is authentic.
What if they also (or actually) compared password hashes from their database to the ones released in the Gawker breach? In that case, they likely wouldn't have pulled data straight from the database but actually might have pulled passes from the db, output to text files, cut the text files up to parcel out for processing via Hadoop or something? And somehow one of those text files got loose somehow...or someone MiTMed the actual process (I'd vote for a floating text file just because it's been so long; the Gawker breach was in December 2010).
my fairly complex alphanumeric+symbol password IS in the dump, though not prepended truncated with 0's and the other one I found, which my coworker admitted was too short and alpha only, was in the dump with prepended 0's.
This could validate the fact that the truncated hashes are actually already cracked.
Whoops.
At the very least, it should have been longer.
I think I have changed to this password during the last year.
(email me if you need proof)