What happens after you accidentally leak secrets to a public code repository

Written by shhgit | Published 2021/02/14
Tech Story Tags: security | cyber-security | devsecops | secrets-detection | shhgit | good-company | cyber-threats | password-security

TLDR Fraudsters constantly scan public code repositories for these secrets to gain a foothold into systems. Shhgit finds over 165,000 secrets everyday single across public GitHub, GitLab, and Bitbucket repositories. The fallout can be catastrophic in terms of financial loss and reputational damage. We purposely leaked valid Amazon AWS credentials to a public GitHub repository. We chose to leak AWS keys because we know they are highly sought after by fraudsters with all sorts of different motives — espionage, spamming, financial gain or blackmail. But what happens immediately after leaking secrets?via the TL;DR App

no story

Written by shhgit | We find secrets in your code — before the bad guys do.
Published by HackerNoon on 2021/02/14