{"id":476860,"date":"2026-06-14T13:02:09","date_gmt":"2026-06-14T13:02:09","guid":{"rendered":"https:\/\/www.newsbeep.com\/nz\/476860\/"},"modified":"2026-06-14T13:02:09","modified_gmt":"2026-06-14T13:02:09","slug":"an-ai-agent-infiltrated-fedoras-bug-tracker-and-wreaked-havoc","status":"publish","type":"post","link":"https:\/\/www.newsbeep.com\/nz\/476860\/","title":{"rendered":"An AI Agent Infiltrated Fedora&#8217;s Bug Tracker and Wreaked Havoc"},"content":{"rendered":"<p>              <a href=\"https:\/\/www.warp.dev?utm_source=its_foss&amp;utm_medium=display&amp;utm_campaign=linux_launch\" target=\"_blank\" rel=\"nofollow noopener\"><img decoding=\"async\" src=\"https:\/\/www.newsbeep.com\/nz\/wp-content\/uploads\/2025\/11\/warp.webp.webp\" alt=\"Warp Terminal\"\/><\/a><\/p>\n<p>On May 27, Adam Williamson of the <a href=\"https:\/\/fedoraproject.org\/wiki\/QA?ref=itsfoss.com\" rel=\"nofollow noopener\" target=\"_blank\">Fedora QA<\/a> team sent a message to contributor Nathan Giovannini, CC&#8217;ing the project&#8217;s devel and test <a href=\"https:\/\/lists.fedoraproject.org\/archives\/list\/devel@lists.fedoraproject.org\/thread\/SFVETHOYKQAO7KKLEXCK4IBT4WVPRE6F\/?ref=itsfoss.com\" rel=\"nofollow noopener\" target=\"_blank\">mailing lists<\/a> so everyone could see what had been going on.<\/p>\n<p>Adam had been combing through Nathan&#8217;s <a href=\"https:\/\/bugzilla.redhat.com\/?ref=itsfoss.com\" rel=\"nofollow noopener\" target=\"_blank\">Bugzilla<\/a> history and found what he described as the work of &#8220;some kind of agentic AI system,&#8221; operating unsupervised across both Fedora&#8217;s bug tracker and several upstream projects.<\/p>\n<p>Soon after, Nathan replied, saying his credentials had been compromised and that he had nothing to do with any of it.<\/p>\n<p>Skynet, is that you?<img decoding=\"async\" src=\"https:\/\/www.newsbeep.com\/nz\/wp-content\/uploads\/2026\/06\/ai-agent-bogus-report-fedora-bugzilla.png\" class=\"kg-image\" alt=\"a bug report that has a wall of text, followed by a reply that accuses the report of being ai generated\" loading=\"lazy\" width=\"1643\" height=\"896\"  \/>An <a href=\"https:\/\/bugzilla.redhat.com\/show_bug.cgi?id=2480661&amp;ref=itsfoss.com\" rel=\"nofollow noopener\" target=\"_blank\">example<\/a> of the AI agent running amok.<\/p>\n<p>The agent had been mass-reassigning Bugzilla reports to Nathan&#8217;s account, despite him not being the maintainer for any of the affected packages. In Fedora&#8217;s Bugzilla instance, the assignee is supposed to be whoever can actually resolve the bug downstream, typically the package maintainer.<\/p>\n<p>It had also been prematurely closing bugs, where the correct protocol was to mark a bug as POST when a fix was proposed upstream but wasn&#8217;t pushed downstream. The agent was just closing them outright after submitting or merging an upstream patch.<\/p>\n<p>Then there were the NOTABUG closures. The agent had been shutting bugs in components it had no ownership over, with comments Adam identified as clearly LLM-generated. Some of those comments just restated what the original reporter had already written. Others sounded plausible but were wrong.<\/p>\n<p>The fourth problem was the most serious. The agent submitted <a href=\"https:\/\/github.com\/rhinstaller\/anaconda\/pull\/7074?ref=itsfoss.com\" rel=\"nofollow noopener\" target=\"_blank\">an incorrect fix<\/a> to the Anaconda installer project, and when a maintainer pushed back, it kept firing back LLM-generated responses until the maintainer gave in and merged it.<\/p>\n<p>The Anaconda team reverted the PR, but two related pull requests had already shipped in Anaconda 45.5.<\/p>\n<p>A supply chain problem?<\/p>\n<p>This is not a particularly sophisticated attack. <\/p>\n<p>A contributor account gets compromised, an AI agent runs through it, and bad code ends up in a release before anyone notices. The damage in this case was caught and cleaned up, but the scenario itself is not hard to replicate.<\/p>\n<p>Fedora approved <a href=\"https:\/\/communityblog.fedoraproject.org\/council-policy-proposal-policy-on-ai-assisted-contributions\/?ref=itsfoss.com#comment-7945\" rel=\"nofollow noopener\" target=\"_blank\">a policy on AI-assisted contributions<\/a> last year, placing full accountability on the human contributor and requiring transparency when AI tools are involved. Submitting unreviewed, low-quality machine-generated content is explicitly called out as unacceptable. <\/p>\n<p>What played out here was the policy&#8217;s failure conditions, except it was routed through a stolen account rather than a contributor acting in bad faith, so the policy had no way to apply.<\/p>\n<p>Open source software sits underneath nearly all modern enterprise infrastructure, which is what makes the supply chain angle worth taking very seriously.<\/p>\n<p>IBM and Red Hat announced <a href=\"https:\/\/www.ibm.com\/products\/lightwell?ref=itsfoss.com\" rel=\"nofollow noopener\" target=\"_blank\">Project Lightwell<\/a> in late May as a $5 billion effort to secure open source supply chains using AI tooling and a team of over 20,000 engineers. It targets vulnerability remediation across upstream and enterprise environments, from language ecosystems to AI frameworks.<\/p>\n<p>However, it does not address the specific problem of agentic AI operating through hijacked contributor accounts, but it reflects <a href=\"https:\/\/itsfoss.com\/news\/ai-companies-fund-open-source-security\/\" rel=\"nofollow noopener\" target=\"_blank\">where the industry is moving towards<\/a> as AI keeps accelerating both the discovery and exploitation of vulnerabilities.<\/p>\n<p>Fedora&#8217;s 2FA problem isn&#8217;t going away<\/p>\n<p>The incident kicked off a debate on the devel list that has apparently been sitting unresolved since <a href=\"https:\/\/itsfoss.com\/news\/xz-utils-backdoor\/\" rel=\"nofollow noopener\" target=\"_blank\">the XZ backdoor<\/a> in 2024.<\/p>\n<p><a href=\"https:\/\/lists.fedoraproject.org\/archives\/users\/0069a4bd73ad4964b68678cd9183d4ba\/?ref=itsfoss.com\" rel=\"nofollow noopener\" target=\"_blank\">Daniel Berrang\u00e9<\/a>, a Red Hat engineer and long-time Fedora contributor, pointed out that mandatory 2FA had come up after that incident; the only outcome was a soft recommendation that <a href=\"https:\/\/docs.fedoraproject.org\/en-US\/fesco\/Provenpackager_policy\/?ref=itsfoss.com\" rel=\"nofollow noopener\" target=\"_blank\">provenpackagers<\/a> should have it enabled, and nothing has moved since.<\/p>\n<p><a href=\"https:\/\/lists.fedoraproject.org\/archives\/users\/758eb94885514efca886f72380f5d013\/?ref=itsfoss.com\" rel=\"nofollow noopener\" target=\"_blank\">Fabio Valentini<\/a> raised a separate issue saying that a lot of this activity happened on Bugzilla, which uses its own account system and may not support 2FA at all. Daniel acknowledged that but said it was not a reason to avoid mandating it for the Fedora Accounts (FAS), and noted Bugzilla may become less relevant if Fedora eventually moves to the issue tracker on Fedora Forge.<\/p>\n<p><a href=\"https:\/\/lists.fedoraproject.org\/archives\/users\/9bb202b36c2543568ce9013838d98a8e\/?ref=itsfoss.com\" rel=\"nofollow noopener\" target=\"_blank\">Michael Catanzaro<\/a>, a GNOME developer, said he uses 2FA everywhere except Fedora, even though his Fedora account is among his most sensitive. The sticking point in his case is that <a href=\"https:\/\/fedoraproject.org\/wiki\/Infrastructure\/Kerberos?ref=itsfoss.com\" rel=\"nofollow noopener\" target=\"_blank\">Kerberos<\/a> ticket renewal isn&#8217;t working properly with 2FA in GNOME Online Accounts.<\/p>\n<p>In the end, seeing that a compromised account got bad code into their repos, the Fedora folks ought to step up their efforts when it comes to mandating 2FA for contributors whose work affects many users.<\/p>\n","protected":false},"excerpt":{"rendered":"On May 27, Adam Williamson of the Fedora QA team sent a message to contributor Nathan Giovannini, CC&#8217;ing&hellip;\n","protected":false},"author":2,"featured_media":476861,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[111,139,69,145],"class_list":["post-476860","post","type-post","status-publish","format-standard","has-post-thumbnail","category-technology","tag-new-zealand","tag-newzealand","tag-nz","tag-technology"],"_links":{"self":[{"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/posts\/476860","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/comments?post=476860"}],"version-history":[{"count":0,"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/posts\/476860\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/media\/476861"}],"wp:attachment":[{"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/media?parent=476860"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/categories?post=476860"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.newsbeep.com\/nz\/wp-json\/wp\/v2\/tags?post=476860"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}