Re:XAI Dev Leaks API Key for Private SpaceX, Tesla LLMs
by Everdred2dx on Friday May 02, 2025 @01:12AM
(#43866407)
How would you scan for your api keys on repos outside of your organization? I assumed this was a dev’s personal repo.
[ Parent
| on HN ]
Re:XAI Dev Leaks API Key for Private SpaceX, Tesla LLMs
by Everdred2dx on Friday May 02, 2025 @03:33PM
(#43873826)
Neat. Thanks!
Re:XAI Dev Leaks API Key for Private SpaceX, Tesla LLMs
by squigz on Friday May 02, 2025 @05:04AM
(#43867626)
Well 1 option is the service from TFA.
https://www.gitguardian.com/monitor-internal-repositories-fo...
Re:XAI Dev Leaks API Key for Private SpaceX, Tesla LLMs
by romellem on Friday May 02, 2025 @09:01AM
(#43869180)
The company I work for does this. I recently pushed an update to a personal repo that just contained a keyword match (the push included a dictionary.txt file which happened to include the company name) which flagged a review.
Re:XAI Dev Leaks API Key for Private SpaceX, Tesla LLMs
by mcdwayne on Friday May 02, 2025 @03:40PM
(#43873882)
This was on public GitHub, which anyone can scan for anything. Their API is a firehose you can consume: https://api.github.com/events
GitGuardian's public report on secrets sprawl talks about their methodology of scanning any commit https://www.gitguardian.com/state-of-secrets-sprawl-report-2...