{"id":566,"date":"2026-05-21T23:20:11","date_gmt":"2026-05-21T23:20:11","guid":{"rendered":"https:\/\/fluffyworld.org\/?p=566"},"modified":"2026-05-21T23:20:11","modified_gmt":"2026-05-21T23:20:11","slug":"a-hacker-group-is-poisoning-open-source-code-at-an-unprecedented-scale","status":"publish","type":"post","link":"https:\/\/fluffyworld.org\/?p=566","title":{"rendered":"A Hacker Group Is Poisoning Open Source Code at an Unprecedented Scale"},"content":{"rendered":"<p> <br \/>\n<\/p>\n<div>\n<p>A so-called software <a href=\"https:\/\/www.wired.com\/story\/the-untold-story-of-solarwinds-the-boldest-supply-chain-hack-ever\/\" class=\"text link\">supply chain attack<\/a>, in which hackers corrupt a legitimate piece of software to hide their own malicious code, was once a relatively rare event but one that haunted the cybersecurity world with its insidious threat of turning any innocent application into a dangerous foothold in a victim\u2019s network. Now <a href=\"https:\/\/www.wired.com\/story\/meta-pauses-work-with-mercor-after-data-breach-puts-ai-industry-secrets-at-risk\/\" class=\"text link\">one group of cybercriminals<\/a> has turned that occasional nightmare into a near-weekly episode, corrupting hundreds of open source tools, extorting victims for profit, and sowing a new level of distrust in an entire ecosystem used to create the world\u2019s software.<\/p>\n<p class=\"paywall\">On Tuesday night, open source code platform GitHub announced that it had been breached by hackers in one such software supply chain attack: A GitHub developer had installed a \u201cpoisoned\u201d extension for VSCode, a plug-in for a commonly used code editor that, like GitHub itself, is owned by Microsoft. As a result, the hackers behind the breach, an increasingly notorious group called TeamPCP, claim to have accessed around 4,000 of GitHub\u2019s code repositories. GitHub\u2019s statement confirmed that it had found at least 3,800 compromised repositories while noting that, based on its findings so far, they all contained GitHub\u2019s own code, not that of customers.<\/p>\n<p class=\"paywall\">\u201cWe are here today to advertise GitHub\u2019s source code and internal orgs for sale,\u201d TeamPCP wrote on BreachForums, a forum and marketplace for cybercriminals. \u201cEverything for the main platform is there and I very am happy to send samples to interested buyers to verify absolute authenticity.\u201d<\/p>\n<p class=\"paywall\">The GitHub breach is just the latest incident in what has become the longest-running spree of software supply chain attacks ever, with no end in sight. According to cybersecurity firm Socket, which focuses on software supply chains, TeamPCP has, in just the last few months, carried out 20 \u201cwaves\u201d of supply chain attacks that have hidden malware in more than 500 distinct pieces of software, or well over a thousand counting all of the various versions of the code that TeamPCP has hijacked.<\/p>\n<p class=\"paywall\">Those tainted pieces of code have allowed TeamPCP\u2019s hackers to breach hundreds of companies that installed the software, says Ben Read, who leads strategic threat intelligence at the cloud security firm Wiz. GitHub is only the latest on the group\u2019s long list of victims, which has also included AI firm OpenAI and the data contracting firm Mercor. \u201cIt may be their biggest one,&#8221; Read says of the GitHub breach. \u201cBut each one of these is a big deal for the company that it happens to. It&#8217;s not qualitatively different from the 14 breaches that happened last week.\u201d<\/p>\n<p class=\"paywall\">TeamPCP\u2019s core tactic has become a kind of cyclical exploitation of software developers: The hackers gain access to a network where an open source tool commonly used by coders is being developed\u2014for example, the VSCode extension that led to the GitHub breach or the data visualization software AntV that TeamPCP hijacked earlier this week. The hackers plant malware in the tool that ends up on other software developers\u2019 machines, including some who are writing other tools intended to be used by coders.<\/p>\n<p class=\"paywall\">The malware allows TeamPCP\u2019s hackers to steal credentials that let them publish malicious versions of <em>those<\/em> software development tools, too. The cycle repeats, and TeamPCP\u2019s collection of breached networks grows. \u201cIt\u2019s a flywheel of supply chain compromises,\u201d says Read. \u201cIt\u2019s self-perpetuating, and it\u2019s been a hugely successful way to get access to networks and steal stuff.\u201d<\/p>\n<p class=\"paywall\">Most recently, the group appears to have automated many of its software supply chain attacks with a self-spreading worm that\u2019s come to be known as Mini Shai-Hulud. The name comes from GitHub repositories the worm creates that include encrypted credentials stolen from victims, each of which includes the phrase \u201cA Mini Shai-Hulud Has Appeared\u201d along with a handful of other references to the sci-fi novel <em>Dune<\/em>. That message in turn appears to be a reference not just to <em>Dune<\/em>\u2019s sandworms but to a similar <a href=\"https:\/\/www.wired.com\/story\/a-dangerous-worm-is-eating-its-way-through-software-packages\/\" class=\"text link\">supply chain compromise worm known as Shai-Hulud that appeared in September<\/a>, though there\u2019s no evidence TeamPCP was behind that earlier self-spreading malware.<\/p>\n<\/div>\n<p><br \/>\n<br \/><a href=\"https:\/\/www.wired.com\/story\/teampcp-software-supply-chain-attack-spree-github\/\">Source link <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>A so-called software supply chain attack, in which hackers corrupt a legitimate piece of software to hide their own malicious code, was once a relatively [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":567,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[],"class_list":["post-566","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-technology"],"_links":{"self":[{"href":"https:\/\/fluffyworld.org\/index.php?rest_route=\/wp\/v2\/posts\/566","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fluffyworld.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fluffyworld.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fluffyworld.org\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fluffyworld.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=566"}],"version-history":[{"count":0,"href":"https:\/\/fluffyworld.org\/index.php?rest_route=\/wp\/v2\/posts\/566\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/fluffyworld.org\/index.php?rest_route=\/wp\/v2\/media\/567"}],"wp:attachment":[{"href":"https:\/\/fluffyworld.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=566"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fluffyworld.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=566"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fluffyworld.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=566"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}