# GitHub API Key Scraper – Real-Time Leaked Credentials 🔑

**URL:** <https://onehack.st/t/github-api-key-scraper-real-time-leaked-credentials/316290>\
**Category:** Tools & Scripts\
**Tags:** programming, hacking\
**Created:** [January 6, 2026, 1:40am UTC](https://onehack.st/t/github-api-key-scraper-real-time-leaked-credentials/316290 "2026-01-06T01:40:03Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zaim\_Abbasi](https://onehack.st/user_avatar/onehack.st/zaim_abbasi/32/167921_2.png) [@Zaim\_Abbasi](https://onehack.st/u/Zaim_Abbasi)\
**Post date:** [January 6, 2026, 1:40am UTC](https://onehack.st/t/github-api-key-scraper-real-time-leaked-credentials/316290/1 "2026-01-06T01:40:03Z")

</div>

# Real Working API Keys Leaked Every Hour on GitHub 🔓

> 🗺 **One-Line Flow:** Live GitHub scraper that finds accidentally-leaked API keys every second — OpenAI, Anthropic, DeepSeek, all free if you’re fast enough.

* * *

### Why devs accidentally fund your next project

Thousands of working API keys hit public GitHub repos every day because people push `.env` files they shouldn’t.

By the time the leak gets noticed, you’ve already burned through $47 worth of credits that weren’t yours.

This is how broke developers ship features wealthy companies can’t. No ethics lecture here — just mechanics.

* * *

Every hour, live credentials leak: **OpenAI, DeepSeek, Anthropic, Google AI, AWS, Stripe.**

Not expired tokens. Not rate-limited demos. **Funded accounts someone’s paying for right now.**

> **🎯 What you actually get**
>
> **🔍 Live API keys** — copy straight from the dashboard  
> **📍 Direct repo links** — exact file where it leaked  
> **⏱ Leak timestamps** — see if it’s 30 seconds old or already dead

**API Radar** scrapes GitHub in real time. Updated the second a new key appears.

Open it once. Watch the counter climb while you’re still reading this sentence.

Every refresh shows keys that didn’t exist 10 seconds ago.

## [https://apiradar.live](https://apiradar.live)

The leak happens. The tool catches it. You decide how fast you move.

* * *

**The feed exists.** Whether you use it or keep paying full price is your problem.

Bookmark it. Won’t be posted again.

Edited by @SRZ for readability 🔧

---

<div class="post-metadata">

**Author:** ![MAHIN\_HASAN\_RAJ](https://onehack.st/user_avatar/onehack.st/mahin_hasan_raj/32/167943_2.png) [@MAHIN\_HASAN\_RAJ](https://onehack.st/u/MAHIN_HASAN_RAJ)\
**Post date:** [January 6, 2026, 8:17am UTC](https://onehack.st/t/github-api-key-scraper-real-time-leaked-credentials/316290/2 "2026-01-06T08:17:13Z")

</div>

Hi everyone,

I wanted to share a free website that helps you find leaked API keys and secrets on GitHub.

What it does:

Scans Public Repos: Automatically searches GitHub for sensitive strings (like OpenAI keys, AWS credentials, and Firebase configs).

Real-time Results: Monitors recent commits to find keys before they are rotated.

No Setup Required: Everything is web-based, so you don’t need to run complex Python scripts or CLI tools locally.

How to use it:

Go to the websites (link below).

[https://www.unsecuredapikeys.com/](https://www.unsecuredapikeys.com/)

Search for specific service you are looking for.

Browse the results for exposed credentials.

Disclaimer: This tool is intended for security researchers, bug hunters, and developers who want to check if their own keys have been leaked. Please use this information responsibly and ethically.

---

<div class="post-metadata">

**Author:** ![azertyyou](https://onehack.st/user_avatar/onehack.st/azertyyou/32/157064_2.png) [@azertyyou](https://onehack.st/u/azertyyou)\
**Post date:** [January 6, 2026, 9:29am UTC](https://onehack.st/t/github-api-key-scraper-real-time-leaked-credentials/316290/3 "2026-01-06T09:29:28Z")

</div>

Please, what to use it for ?  
Building our own apps or tools

---

<div class="post-metadata">

**Author:** ![check](https://onehack.st/user_avatar/onehack.st/check/32/167963_2.png) [@check](https://onehack.st/u/check)\
**Post date:** [January 6, 2026, 10:06am UTC](https://onehack.st/t/github-api-key-scraper-real-time-leaked-credentials/316290/4 "2026-01-06T10:06:39Z")

</div>

u can see more about [here](https://letmegooglethat.com/?q=How+can+I+use+an+artificial+intelligence+api%3F), try.

---

<div class="post-metadata">

**Author:** ![KrishnDhola](https://onehack.st/user_avatar/onehack.st/krishndhola/32/160605_2.png) [@KrishnDhola](https://onehack.st/u/KrishnDhola)\
**Post date:** [January 6, 2026, 3:31pm UTC](https://onehack.st/t/github-api-key-scraper-real-time-leaked-credentials/316290/6 "2026-01-06T15:31:57Z")

</div>

Bro, thank you. I was using it a month ago. They accidentally deleted their database, but now it is back

---

<div class="post-metadata">

**Author:** ![MAHIN\_HASAN\_RAJ](https://onehack.st/user_avatar/onehack.st/mahin_hasan_raj/32/167943_2.png) [@MAHIN\_HASAN\_RAJ](https://onehack.st/u/MAHIN_HASAN_RAJ)\
**Post date:** [January 6, 2026, 7:38pm UTC](https://onehack.st/t/github-api-key-scraper-real-time-leaked-credentials/316290/7 "2026-01-06T19:38:29Z")

</div>

Anything you want. It’s upto you

---

<div class="post-metadata">

**Author:** ![Zaim\_Abbasi](https://onehack.st/user_avatar/onehack.st/zaim_abbasi/32/167921_2.png) [@Zaim\_Abbasi](https://onehack.st/u/Zaim_Abbasi)\
**Post date:** [January 7, 2026, 11:59am UTC](https://onehack.st/t/github-api-key-scraper-real-time-leaked-credentials/316290/8 "2026-01-07T11:59:17Z")

</div>

thanks, i justchecked this tool, and it’s just providing a single api key. i might be wrong, but that’s what i saw.

---

<div class="post-metadata">

**Author:** ![MAHIN\_HASAN\_RAJ](https://onehack.st/user_avatar/onehack.st/mahin_hasan_raj/32/167943_2.png) [@MAHIN\_HASAN\_RAJ](https://onehack.st/u/MAHIN_HASAN_RAJ)\
**Post date:** [January 7, 2026, 2:16pm UTC](https://onehack.st/t/github-api-key-scraper-real-time-leaked-credentials/316290/9 "2026-01-07T14:16:35Z")

</div>

There are two websites which one you cheaked?

---

<div class="post-metadata">

**Author:** ![Zaim\_Abbasi](https://onehack.st/user_avatar/onehack.st/zaim_abbasi/32/167921_2.png) [@Zaim\_Abbasi](https://onehack.st/u/Zaim_Abbasi)\
**Post date:** [January 7, 2026, 6:14pm UTC](https://onehack.st/t/github-api-key-scraper-real-time-leaked-credentials/316290/10 "2026-01-07T18:14:58Z")

</div>

abt the [unsecuredapikeys.com](http://unsecuredapikeys.com) one

---

<div class="post-metadata">

**Author:** ![MAHIN\_HASAN\_RAJ](https://onehack.st/user_avatar/onehack.st/mahin_hasan_raj/32/167943_2.png) [@MAHIN\_HASAN\_RAJ](https://onehack.st/u/MAHIN_HASAN_RAJ)\
**Post date:** [January 8, 2026, 5:33am UTC](https://onehack.st/t/github-api-key-scraper-real-time-leaked-credentials/316290/11 "2026-01-08T05:33:30Z")

</div>

Oh, you can select which platform api key you want. It doesn’t shows a single key.

---

<div class="post-metadata">

**Author:** ![Zaim\_Abbasi](https://onehack.st/user_avatar/onehack.st/zaim_abbasi/32/167921_2.png) [@Zaim\_Abbasi](https://onehack.st/u/Zaim_Abbasi)\
**Post date:** [January 11, 2026, 6:56am UTC](https://onehack.st/t/github-api-key-scraper-real-time-leaked-credentials/316290/12 "2026-01-11T06:56:49Z")

</div>

**[MAJOR UPDATE] – Backend Hardening & Secure-by-Design Architecture**

I’ve spent the weekend refactoring the entire data layer. To the users who mentioned the tool only showing specific results, the engine has now indexed over **3,100+ unique leaks** across the global GitHub ecosystem.

**What’s New:**

- **Redact-First Controller:** I’ve moved the security logic to the backend. Raw API keys are now masked at the database fetch level. Even if someone inspects the network payload, the “fullKey” is physically not there.

- **Attack Surface Reduction:** I’ve removed the ‘Copy’ button. The platform is now a pure **Discovery Radar**. We are focusing on identifying leaks, not facilitating exploitation.

- **Performance Plumbing:** Refined the Nginx and Node.js config for zero-latency infinite scrolling through the 3k+ leak history.

**Question:** I’m looking to add more providers next. Should I prioritize **Stripe** , **AWS** , or **Discord** webhooks?

Test the new secure architecture here: [https://apiradar.live](https://apiradar.live)

---

<div class="post-metadata">

**Author:** ![mulejuice1](https://onehack.st/user_avatar/onehack.st/mulejuice1/32/154047_2.png) [@mulejuice1](https://onehack.st/u/mulejuice1)\
**Post date:** [January 11, 2026, 10:12am UTC](https://onehack.st/t/github-api-key-scraper-real-time-leaked-credentials/316290/13 "2026-01-11T10:12:59Z")

</div>

add dark screen. easier on the eyes.

---

<div class="post-metadata">

**Author:** ![MAHIN\_HASAN\_RAJ](https://onehack.st/user_avatar/onehack.st/mahin_hasan_raj/32/167943_2.png) [@MAHIN\_HASAN\_RAJ](https://onehack.st/u/MAHIN_HASAN_RAJ)\
**Post date:** [January 12, 2026, 6:39am UTC](https://onehack.st/t/github-api-key-scraper-real-time-leaked-credentials/316290/14 "2026-01-12T06:39:03Z")

</div>

Everything good, but i think i need the copy option 😁

---

<div class="post-metadata">

**Author:** ![Zaim\_Abbasi](https://onehack.st/user_avatar/onehack.st/zaim_abbasi/32/167921_2.png) [@Zaim\_Abbasi](https://onehack.st/u/Zaim_Abbasi)\
**Post date:** [January 18, 2026, 6:11pm UTC](https://onehack.st/t/github-api-key-scraper-real-time-leaked-credentials/316290/15 "2026-01-18T18:11:33Z")

</div>

check now, changed the site entirely to dark mode. 😉

---

<div class="post-metadata">

**Author:** ![slimjval](https://onehack.st/user_avatar/onehack.st/slimjval/32/30254_2.png) [@slimjval](https://onehack.st/u/slimjval)\
**Post date:** [January 18, 2026, 8:54pm UTC](https://onehack.st/t/github-api-key-scraper-real-time-leaked-credentials/316290/16 "2026-01-18T20:54:44Z")

</div>

useful share, thanks.  
It takes patience to get something that works

---

<div class="post-metadata">

**Author:** ![Zaim\_Abbasi](https://onehack.st/user_avatar/onehack.st/zaim_abbasi/32/167921_2.png) [@Zaim\_Abbasi](https://onehack.st/u/Zaim_Abbasi)\
**Post date:** [February 13, 2026, 4:48am UTC](https://onehack.st/t/github-api-key-scraper-real-time-leaked-credentials/316290/17 "2026-02-13T04:48:03Z")

</div>

added more providers incl

 ![image](https://onehack.st/uploads/default/original/3X/8/a/8ae41e8dfcf7dc8300fb4c468d4eac7499500a9c.png)

---

<div class="post-metadata">

**Author:** ![crashyroot](https://onehack.st/user_avatar/onehack.st/crashyroot/32/170588_2.png) [@crashyroot](https://onehack.st/u/crashyroot)\
**Post date:** [February 13, 2026, 6:21am UTC](https://onehack.st/t/github-api-key-scraper-real-time-leaked-credentials/316290/18 "2026-02-13T06:21:12Z")

</div>

Good find! Have star the repos!

---

<div class="post-metadata">

**Author:** ![KrishnDhola](https://onehack.st/user_avatar/onehack.st/krishndhola/32/160605_2.png) [@KrishnDhola](https://onehack.st/u/KrishnDhola)\
**Post date:** [May 12, 2026, 5:41am UTC](https://onehack.st/t/github-api-key-scraper-real-time-leaked-credentials/316290/19 "2026-05-12T05:41:12Z")

</div>

But how can I see API keys? I want Gemini API keys. I am creating a CAPTCHA solver API. Please support me for this. i can create an API checker for you run on my server fast and easy

---

<div class="post-metadata">

**Author:** ![kanji](https://onehack.st/user_avatar/onehack.st/kanji/32/167864_2.png) [@kanji](https://onehack.st/u/kanji)\
**Post date:** [July 22, 2026, 6:52pm UTC](https://onehack.st/t/github-api-key-scraper-real-time-leaked-credentials/316290/21 "2026-07-22T18:52:26Z")

</div>

site down.. any alternative?

---

<div class="post-metadata">

**Author:** ![Zaim\_Abbasi](https://onehack.st/user_avatar/onehack.st/zaim_abbasi/32/167921_2.png) [@Zaim\_Abbasi](https://onehack.st/u/Zaim_Abbasi)\
**Post date:** [September 14, 2026, 8:48pm UTC](https://onehack.st/t/github-api-key-scraper-real-time-leaked-credentials/316290/22 "2026-09-14T20:48:38Z")

</div>

**Major update:** APIRadar 2.0 is live.

Changes in this release:

- New domain: [https://apiradar.bot.nu](https://apiradar.bot.nu)
- Codebase open-sourced on GitHub (MIT): [https://github.com/zaim-abbasi/APIRadar](https://github.com/zaim-abbasi/APIRadar)
- Redesigned UI and dashboard.
- Inspect leaked repos, exact file paths, and copy keys directly.
- Added entropy filtering to remove false positives.
- Redacted key previews.

Check out the GitHub repo and live scanner. Feedback and stars are welcome.
