WeSearch

GitHub slashes public bug bounty payouts as AI report flood buries its security team

Carly Page· ·2 min read · 0 reactions · 0 comments · 3 views
#github#slashes#public#bounty#payouts
GitHub slashes public bug bounty payouts as AI report flood buries its security team
TL;DR · WeSearch summary

At the same time, newcomers will find themselves capped on how many reports they can submit until they've demonstrated they can produce something worth reading. REG AD googletag.cmd.push(function() { googletag.display('labrador/thereg/article/desktop/b'); }); The Microsoft-owned biz says that the shake-up is a response to the flood of low-effort and AI-generated reports now accompanying many bug bounty programs. Rather than paying more people to file more reports, GitHub wants to spend more on researchers who've proved they can find the real thing.

Key facts
Original article
www.theregister.com - Articles · Carly Page
Read full at www.theregister.com - Articles →
Opening excerpt (first ~120 words) tap to expand

(function() { let windowUrl = window.location.href; windowUrl = windowUrl.substring(windowUrl.indexOf('?') + 1); let messageElement = document.querySelector('.shareableMessage'); if (windowUrl && windowUrl.includes('code') && windowUrl.includes('expires')) { messageElement.style.display = 'block'; } })(); Dev ops GitHub slashes public bug bounty payouts as AI report flood buries its security team Code shack also putting new limits on first-time researchers, and reserving the biggest rewards for a hand-picked group of proven hunters Carly Page Carly Page Published thu 23 Jul 2026 // 16:15 UTC GitHub has decided that, if everyone with an AI chatbot can file a bug bounty report, it may as well stop paying them like seasoned security researchers.Starting July 27, the Microsoft-owned code…

Excerpt limited to ~120 words for fair-use compliance. The full article is at www.theregister.com - Articles.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments