3 ms·
There's no way to know which site the e-mail was coming from, but you could at least grep[2] your password database (depends on how diligent you are with enteri
by ZoomZoomZoom 6y ago
There's no way to know which site the e-mail was coming from, but you could at least grep[2] your password database (depends on how diligent you are with entering urls), and check the top leaked sites manually[1].
Note, that the first list published by Troy is truncated, so it's not full.
1:
cat gist1.txt gist2.txt | awk '{print $1, gensub(/[{}.]*/,"","g",$2)}' | sort -rnk2 > cit0-urls-sorted.txt
2:
cat gist1.txt gist2.txt | awk '{print $1}' | sort -u > cit0-urls.txt
grep -Fif cit0-urls.txt DATABASE.csv
- peteri 6y agoI was planning on an automated check on my passwords via my password manager to see which one have been stolen. Since my passwords are mostly (I may have missed changing some after the linkedin breach) unique these days I thought I could probably figure out which one was stolen as a result.
- scoot 6y ago> the first list published by Troy is truncated Where is that list? I couldn't see it linked from the article. (Sorry if I just missed it)
- ZoomZoomZoom 6y agoThey are at the start of the article. He said he fixed the truncated one down in the comments, but I don't see it being fixed. https://gist.githubusercontent.com/troyhunt/0282a5bad48bd6698672735519ca883a/raw/53ba9bd51256dc658b39094660ac3c2ade7f3aea/Cit0day%20%5B_special_for_xss.is%5D.txt https://gist.githubusercontent.com/troyhunt/0282a5bad48bd669... https://gist.githubusercontent.com/troyhunt/54d421427ae0c32cadc7e18aac28b539/raw/4a12218baf062730eedbbeb8c21b5ef97b5ab86c/Cit0day%20Prem%20%5B_special_for_xss.is%5D.txt https://gist.githubusercontent.com/troyhunt/54d421427ae0c32c...
- aSockPuppeteer 6y agoI couldn't grep any sites from my list but was on the email list. I guess it's just a reminder to not use easy passwords and to change them often. Had to make an icloud keychain password copy script for someone so that was something new.