I scanned all of GitHub's "oops commits" for leaked secrets

Re:I scanned all of GitHub's "oops commits" for leaked secrets by john2go3 on Thursday July 03, 2025 @04:38AM (#44452922)

Unfortunately for those of us without a Google account, it seems one is required to download the mentioned SQLite database (force_push_commits.sqlite3.)

[ Parent | on HN ]

Re:I scanned all of GitHub's "oops commits" for leaked secrets by gen6acd60af on Thursday July 03, 2025 @05:08AM (#44453094)

Concerning.

It's interesting research, but will Truffle Security use the email addresses for lead gen or marketing purposes, like how they mined users' pingbacks from their XSS Hunter fork for stats?

https://portswigger.net/daily-swig/new-xss-hunter-host-truff...

[ Parent | on HN ]

Re:I scanned all of GitHub's "oops commits" for leaked secrets by CHUCKEESH on Thursday July 03, 2025 @10:18PM (#44460609)

That’s a common hurdle when trying to access files like this. You might want to check out LeadsApp—they can help organize data without needing a Google login. It made sorting through similar issues easier for me.

[ Parent | on HN ]