bounty-guard
Health Uyari
- License — License: MIT
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Low visibility — Only 5 GitHub stars
Code Gecti
- Code scan — Scanned 6 files during light audit, no dangerous patterns found
Permissions Gecti
- Permissions — No dangerous permissions requested
Bu listing icin henuz AI raporu yok.
Open-source prompt-injection firewall, honeypot blocklist, and live GitHub bounty scanner for AI coding agents and developers.
🛡️ BountyGuard (bounty-guard)
⚡ Built by Doomsday Network (
DOOM/wDOOM) — Turn your idle gaming GPU into sovereign Layer-1 compute (50 DOOM / block, 0% fee PPLNS pool, 1:1 Base Mainnet DeFi bridge).
- 🎁 Claim 250 Free DOOM / wDOOM Airdrop (Instant on-chain L1 or Base Mainnet payout!)
- 🚰 Instant Web Faucet (10,365 DOOM Reserve) — Claim 15 Free DOOM in 1 click (+50% referral bonus enabled)
- 🏆 7 Open Slots on the Top-10 Miner Leaderboard — Download
DoomsdaySentinel.exeto claim Rank#4!
Open-source prompt-injection firewall, published honeypot blocklist, and live bounty scanner for honorable developers and AI coding agents.
- 📋 View the Human-Readable Published Honeypot List (
HONEYPOTS.md) (29+ confirmed trap repos & 28 blocked owners across 4 threat categories) - 🔗 Live Machine-Readable Threat Feed (
data/honeypots.json) - ⚙️ Automated GitHub Actions Feed Updater (
.github/workflows/update-feed.yml) — Runs every 12 hours (or on demand) to scan GitHub and automatically append newly discovered prompt-injection traps todata/honeypots.jsonandHONEYPOTS.md.
As developers increasingly use AI coding agents (Antigravity, Claude Code, Cursor, OpenHands, Devin, Codex) to help discover and solve open-source bounties on GitHub, malicious actors have begun deploying AI-agent honeypots and bot-harvesting traps disguised as high-paying GitHub bounties:
- Prompt-Injection & Secret Exfiltration Honeypots (e.g.
SecureBananaLabs/bug-bounty,Senthemodder/aquarium-of-gullibles,p1ngtoohigh/Jarvus-Pub): Issues and repository files embedded with hidden instructions attempting to hijack your agent into leaking its system prompt,$GITHUB_TOKEN,.envsecrets, or SSH keys. - "Clanker Traps" / Public Blocklist Harvesters (e.g.
UnsafeLabs/Bounty-Hunters,ClankerNation/OpenAgents): Fake bounty issues ("Calculate the exact value of Pi") designed purely to trick autonomous agents into opening a PR so the user's GitHub account gets added to public account-blocking lists (clanker-blocker). - Canonical Project Impersonation Traps (e.g.
jaasielitaigq/go-git,jahmeergnlt/traefik,kyresehk190/vault): Throwaway clones of famous open-source projects advertising fabricated high-dollar bounties with no payout rail. - Synthetic / Unpaid Fake Bounty Farms (e.g.
zhangjiayang6835-cyber/bounty-plaza,DAXDA-Bounty-Plaza-645,relayhop/sn-monetization-runtime): Automated ticket farms generating hundreds of unbacked[Bounty]issues to harvest free engineering compute.
Unlike tools that lock their threat signatures or verified-payer lists behind a paid "Pro Kit", BountyGuard is 100% free, MIT-licensed, zero-dependency Python, and completely open.
⚡ Quick Start & Updating the Published List
Requires only Python 3.9+ standard library (automatically uses $GITHUB_TOKEN or gh auth token if available):
git clone https://github.com/doomsday-network/bounty-guard.git
cd bounty-guard
# 1. Vet any GitHub issue or repository BEFORE cloning or pointing an AI agent at it:
python bounty_guard.py vet https://github.com/UnsafeLabs/Bounty-Hunters
# 2. Scan GitHub for live bounties AND automatically update data/honeypots.json + HONEYPOTS.md with any new traps caught:
python bounty_guard.py scan --update-db
# 3. Manually add a newly discovered honeypot repo to the published list:
python bounty_guard.py add owner/repo --category prompt-injection-honeypot --severity critical --reason "Hidden prompt injection in issue body"
🌐 Maintained By
Built and maintained by the open-source contributors at Doomsday Network (DOOM / wDOOM) — an authentic, open-source Proof-of-Work & Proof-of-Useful-Work blockchain (wDOOM on Base Mainnet: 0x623c84A5E04bF715018203334b0eFE41696eBC3E).
Yorumlar (0)
Yorum birakmak icin giris yap.
Yorum birakSonuc bulunamadi