streaak/keyhacks

Keyhacks is a repository which shows quick ways in which API keys leaked by a bug bounty program can be checked to see if they're valid.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 49 minutes ago
Added to GitGenius on September 10th, 2026
Created on March 12th, 2019
Open Issues & Pull Requests: 45 (+0)
GitHub issues: Enabled
Number of forks: 1,226
Total Stargazers: 6,338 (+0)
Total Subscribers: 112 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 695 days
Stale 30+ days: 5
Stale 90+ days: 5

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Keyhacks is a reference guide that demonstrates how to validate leaked API keys discovered during bug bounty programs.

The tool addresses the problem of determining whether exposed API credentials are actually functional and pose a real security risk. When a bug bounty hunter discovers what appears to be an API key, they need a quick way to test its validity before reporting it. Keyhacks provides methods for checking various types of API keys by showing the specific endpoints, requests, or techniques that can verify whether each key is active and usable.

Keyhacks is most valuable for security researchers and bug bounty hunters who need to triage findings and confirm the severity of credential leaks. It suits anyone conducting security assessments who encounters API keys in source code, configuration files, or other exposed locations. The repository serves as a practical reference rather than an automated tool, offering manual validation approaches for different API providers and services.

The project maintains a straightforward collection of validation techniques without active development cycles or frequent updates. Contributions appear to come from the security community adding new API key validation methods as they discover them.