←back to thread

199 points elza_1111 | 1 comments | | HN request time: 0.205s | source
Show context
raesene9 ◴[] No.44452472[source]
An interesting look at one of the consequences of using git and public repo's.

Does leave me wondering how long before someone has a setup which detects and tries to exploit these in real-time, which feels like it could be nasty.

Also a challenge with these posts is they were unlikely to have been able to contact all the affected developers who have got exposed secrets, meaning that any that were uncontactable/non-responsive are likely still vulnerable now, I'd guess that means they're about see what happens if those secrets get abused, as people start exploring this more...

replies(2): >>44452481 #>>44452488 #
matsemann ◴[] No.44452488[source]
There are hundred of setups like that already. If you push an AWS key or similar publicly you may have a bitcoin miner or botnet running on your cloud in matter of minutes.
replies(2): >>44452797 #>>44453281 #
sunbum ◴[] No.44452797[source]
Nope. Because if you push an AWS key then it gets automatically revoked by AWS.
replies(2): >>44453107 #>>44453236 #
1. larntz ◴[] No.44453107[source]
I wouldn't rely on anything other than rotating leaked credentials.