Cit0day leaks

[Asphyxia]

So, we have some Cit0day leaks:


For anyone that does not know, this is many gigabytes of emails/password hashes/etc.

This was attainable via Raid Forums they actually have a pub Torrent link now: Cit0day - Magnet Torrent | RaidForums

magnet:?xt=urn:btih:92d00ba67037fd4397fe5259824b0f0a5d3b0f33&dn=Cit0day.in%5Fspecial%5Ffor%5Fxss.is.zip&tr=udp%3A%2F%2Ftracker.opentrackr.org%3A1337&tr=udp%3A%2F%2F9.rarbg.to%3A2710%2Fannounce&tr=udp%3A%2F%2F9.rarbg.me%3A2920%2Fannounce&tr=udp%3A%2F%2Ftracker.internetwarriors.net%3A1337%2Fannounce&tr=udp%3A%2F%2Ftracker.leechers-paradise.org%3A6969%2Fannounce&tr=udp%3A%2F%2Ftracker.cyberia.is%3A6969%2Fannounce&tr=udp%3A%2F%2Fexodus.desync.com%3A6969%2Fannounce&tr=http%3A%2F%2Fexplodie.org%3A6969%2Fannounce&tr=udp%3A%2F%2Fp4p.arenabg.ch%3A1337%2Fannounce&tr=http%3A%2F%2Ftracker3.itzmx.com%3A6961%2Fannounce&tr=http%3A%2F%2Ftracker1.itzmx.com%3A8080%2Fannounce&tr=http%3A%2F%2Fp4p.arenabg.com%3A1337%2Fannounce&tr=udp%3A%2F%2Ftracker.zerobytes.xyz%3A1337%2Fannounce&tr=udp%3A%2F%2Ftracker.torrent.eu.org%3A451%2Fannounce&tr=udp%3A%2F%2Ftracker.tiny-vps.com%3A6969%2Fannounce

This magnet address is for security research purposes only - do NOT misuse information found. You take full responsibility / liability for your own actions regarding this data.

The intention of sharing this is for security research to alert individuals of email / hash breach.

Should open fine with 7-Zip - caution: download/use at your own risk.

Password for the archive is "xss.is". Everything should be here, seed if you appreciate the download

Not sure how to open the magnet url?

Just install this Torrent client first, then copy/paste the magnet link into your URL and open the client.. https://sourceforge.net/projects/qb....3.1/qbittorrent_4.3.1_x64_setup.exe/download

 

[Asphyxia]

P.S.

at one point when optimizing I was trying sift (sifter) and various other methods of sorting through file data.

The worst bit of this current optimization is I am flat-file DB and just relying on the SSD to perform quickly enough to keep w/ IO demand, which is not that amazing. I'd prefer a RAM-based method.. using a more proper database with much nicer indexing.

432  time grep -x "[email protected]" emails.txt 
  433  time rg [email protected] emails.txt 
  434  cd ~/sifter/sift_0.9.0_linux_amd64/
  435  ls
  436  time ./sift -i --no-filename "[email protected]" /emails.txt
  437  time grep -F "[email protected]" emails.txt 
  438  time grep -F "[email protected]" /emails.txt 
  439  LC_ALL=C grep -F "[email protected]" /emails.txt 
  440  LC_ALL=C grep -Fx "[email protected]" /emails.txt 
  441  time LC_ALL=C grep -Fx "[email protected]" /emails.txt 
  442  time LC_ALL=C grep -Fx "[email protected]" /emails.txt | head -1
  443  LC_ALL=C grep -Fx "[email protected]" /emails.txt | head -1
  444  LC_ALL=C grep -Fx -m1 "[email protected]" /emails.txt
  445  time LC_ALL=C grep -Fx -m1 "[email protected]" /emails.txt
  446  time LC_ALL=C fgrep -Fx -m1 "[email protected]" /emails.txt
  447  time LC_ALL=C grep -Fx -m1 "[email protected]" /emails.txt
  448  ls -lah
  449  time LC_ALL=C grep -Fx -m1 "[email protected]" /emails.txt
  450  time grep -Fx -m1 "[email protected]" /emails.txt
  451  time LC_ALL=C grep -Fx -m1 "[email protected]" /emails.txt

rg = ripgrep
grep = grep
./sift = sift

These all performed relatively similarly in my experience, at the very end for what I was trying to do just grep alone seemed to work although if I started needing to scan through more data than just line-by-line, I think the other tools could be more useful.

Wish I had benchmark times/stats to show you or a graph, but nah.

Just figured I'd diary the effort.. I guess lol