B-TIER tool
OpenAI — you can literally search for them
100k ft — What is this?
OpenAI — you can literally search for them
50k ft — Why care?
there are 8,000 exposed openai api keys on github right now — @deonnahodges; uses OpenAI; demonstrates API integration.
10k ft — Key takeaways
(no takeaways yet)
5k ft — Tools & techniques
OpenAI
API integration
1k ft — Deep-dive / try it
there are 8,000 exposed openai api keys on github right now
you can literally search for them
29 million secrets leaked on the platform in 2025
ai-generated code leaks credentials at 2x the normal rate
.env file. .gitignore. that’s it. that’s the whole security plan.
#softwareengineer #vibecoding #cybersecurity #ai #buildinpublic
genzbestie
6w
Omg 🙈🙈
Transcript excerpt
This is gonna be between you and me. There are 8,000 free AI API keys. Just send that there on the internet. I am about to commit what looks like a crime, but it's technically just a public GitHub search. Here's what you need to do. First, you go to GitHub. You type in the search bar open AI API key equals SK underscore and hit enter. And baby, there they are. The API keys live exposed like an unlock diary at a slumber party, 29 million secrets leaked on GitHub in 2025. And here's the part that just scare you. AI generated code leaks credentials at twice the rate it's human generated code. Now obviously do not use somebody else's key. I really need everybody to see this video as a horror story and not a how to guide. The Wi-Fi is terrible in jail. So go vibe code, go build your things, just do it right. Put your keys in a dot ENV file and add that dot ENV to your Git Ignore. The bots scraping GitHub for exposed keys do not know that you're building a side project and they don't care if you were just testing. So you can vibe code all you want. Just don't vibe commit your secrets.