<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Zaim Abbasi</title>
    <description>The latest articles on DEV Community by Zaim Abbasi (@zaim_abbasi).</description>
    <link>https://dev.to/zaim_abbasi</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3372444%2F84da5dac-5bff-4247-84a5-568b8e648e8a.jpg</url>
      <title>DEV Community: Zaim Abbasi</title>
      <link>https://dev.to/zaim_abbasi</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/zaim_abbasi"/>
    <language>en</language>
    <item>
      <title>Claude, OpenAI, Google API Keys... All Public. This Is What I Found After Scanning GitHub at Scale</title>
      <dc:creator>Zaim Abbasi</dc:creator>
      <pubDate>Sun, 20 Jul 2025 15:58:09 +0000</pubDate>
      <link>https://dev.to/zaim_abbasi/claude-openai-google-api-keys-all-public-this-is-what-i-found-after-scanning-github-at-scale-fj5</link>
      <guid>https://dev.to/zaim_abbasi/claude-openai-google-api-keys-all-public-this-is-what-i-found-after-scanning-github-at-scale-fj5</guid>
      <description>&lt;p&gt;Hey devs 👋&lt;br&gt;
I'm Zaim – a backend engineer and student, currently diving deep into LLM security.&lt;/p&gt;

&lt;p&gt;A few weeks ago, I was just messing around with GitHub dorks.&lt;br&gt;
You know... the usual:&lt;br&gt;
filename:.env&lt;br&gt;
"sk-" in files pushed last week&lt;br&gt;
Stuff like that.&lt;/p&gt;

&lt;p&gt;What I didn’t expect was how many live API keys I’d find.&lt;/p&gt;

&lt;p&gt;I'm talking:&lt;br&gt;
OpenAI keys (some still active 💀)&lt;br&gt;
Claude / Anthropic keys&lt;br&gt;
Google Cloud API tokens&lt;br&gt;
and even internal test keys from private orgs that somehow made it into public repos.&lt;/p&gt;

&lt;p&gt;Some had been sitting there for weeks. No revokes. No alerts. Just… exposed.&lt;/p&gt;

&lt;p&gt;So I built a tool.&lt;br&gt;
Out of curiosity (and lowkey horror), I spun up a crawler and scanner.&lt;br&gt;
It now continuously monitors public GitHub in real time, flagging leaked keys from:&lt;br&gt;
OpenAI&lt;br&gt;
Claude / Anthropic&lt;br&gt;
Gemini / Google&lt;br&gt;
and more...&lt;/p&gt;

&lt;p&gt;It turned into a project I call API Radar.&lt;br&gt;
It’s a public dashboard showing:&lt;/p&gt;

&lt;p&gt;✅ Real-time leaked API keys&lt;br&gt;
✅ Redacted + raw views&lt;br&gt;
✅ Security leaderboard&lt;br&gt;
✅ Filters by provider&lt;br&gt;
✅ Timeline of exposure&lt;/p&gt;

&lt;p&gt;What I’ve seen so far:&lt;br&gt;
📦 9,200+ public repos scanned&lt;br&gt;
🔑 250+ exposed API keys found&lt;br&gt;
⏱️ First leak spotted within 5 minutes of going live&lt;br&gt;
🌍 Keys from projects across Pakistan, US, EU, and more&lt;/p&gt;

&lt;p&gt;Some people are literally pushing .env files with live keys and leaving them for days.&lt;br&gt;
Others try to hide them in random config folders, but GitHub’s search… doesn’t miss.&lt;/p&gt;

&lt;p&gt;Why it matters&lt;br&gt;
If you’re in security, LLMs, or open source, this matters.&lt;br&gt;
If you're a student, bug bounty hunter, or just curious — this is an underrated goldmine for learning how bad hygiene actually looks in the wild.&lt;/p&gt;

&lt;p&gt;It made me rethink how easy it is to mess up API key security — even for big teams.&lt;/p&gt;

&lt;p&gt;I’m not trying to sell anything here.&lt;br&gt;
Just want to ask:&lt;/p&gt;

&lt;p&gt;Would this help you in CTFs / bug bounties / red teaming?&lt;br&gt;
What else should I track or visualize?&lt;br&gt;
Should I open the scanner as a public API too?&lt;/p&gt;

&lt;p&gt;Let me know — curious what the community thinks 🙌&lt;/p&gt;

</description>
      <category>infosec</category>
      <category>github</category>
      <category>apikeys</category>
      <category>cybersecurity</category>
    </item>
  </channel>
</rss>
