<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Again, with #github #githubactions at the center of another PR driven compromise?]]></title><description><![CDATA[<p class="quote-inline">RE: <a href="https://infosec.exchange/@cidu/116563888871363394" rel="nofollow noopener"><span>https://</span><span>infosec.exchange/@cidu/1165638</span><span>88871363394</span></a></p><p>Again, with <a href="https://infosec.exchange/tags/github" rel="tag">#<span>github</span></a> <a href="https://infosec.exchange/tags/githubactions" rel="tag">#<span>githubactions</span></a> at the center of another PR driven compromise? </p><p>You would think their wonderful <a href="https://infosec.exchange/tags/AI" rel="tag">#<span>AI</span></a> would catch these by now if they're not going to fix the underlying problem. </p><p>Is it called <a href="https://infosec.exchange/tags/copilot" rel="tag">#<span>copilot</span></a> too??</p>]]></description><link>https://board.circlewithadot.net/topic/66dbd5e5-a96a-4274-a6c9-40901ff3f18a/again-with-github-githubactions-at-the-center-of-another-pr-driven-compromise</link><generator>RSS for Node</generator><lastBuildDate>Fri, 15 May 2026 02:11:13 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/66dbd5e5-a96a-4274-a6c9-40901ff3f18a.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 12 May 2026 22:34:17 GMT</pubDate><ttl>60</ttl></channel></rss>