{"id":1202,"date":"2026-06-06T11:46:01","date_gmt":"2026-06-06T11:46:01","guid":{"rendered":"https:\/\/thedigitalfortress.us\/?p=1202"},"modified":"2026-06-06T11:46:01","modified_gmt":"2026-06-06T11:46:01","slug":"miasma-worm-hits-73-microsoft-github-repositories-in-major-supply-chain-attack","status":"publish","type":"post","link":"https:\/\/thedigitalfortress.us\/?p=1202","title":{"rendered":"Miasma Worm Hits 73 Microsoft GitHub Repositories in Major Supply Chain Attack"},"content":{"rendered":"<div>\n<p><span class=\"p-author\"><i class=\"icon-font icon-user\">\ue804<\/i><span class=\"author\">Ravie Lakshmanan<\/span><i class=\"icon-font icon-calendar\">\ue802<\/i><span class=\"author\">Jun 06, 2026<\/span><\/span><span class=\"p-tags\">Supply Chain Attack \/ Malware<\/span><\/p>\n<\/div>\n<div id=\"articlebody\">\n<div class=\"separator\" style=\"clear: both;\"><a href=\"https:\/\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEgG8k6LtHNQ3cHl_X1AZbXRn6LZCNZ6lMLjy-9HG7-_OQekMOhCQKkktrnMqVteXfmGHBMMlbTv3v9Rl6kKjXlNQBSHUVybmD_IBVvMDT7IsMGV49OMSfF5V8bMFVW4ZwFjlg_gddyYtiiQqmdpYIJjuKLTZz_rxooZZQQye7omBEOjyxMFFjAaiZuc6Non\/s1700-e365\/azure-npm.jpg\" style=\"display: block;  text-align: center; clear: left; float: left;\"><\/a><\/div>\n<p>Microsoft&#8217;s GitHub repositories have become the latest to fall victim to the ongoing <b>Miasma<\/b> self-replicating supply chain attack campaign.<\/p>\n<p>The incident impacted 73 Microsoft repositories across four of its GitHub organizations, including Azure, Azure-Samples, Microsoft, and MicrosoftDocs, per <a href=\"https:\/\/opensourcemalware.com\/blog\/miasma-reaches-azure\">OpenSourceMalware<\/a>. The development has GitHub to disable access to those repositories.<\/p>\n<p>\u00abAccess to this repository has been disabled by GitHub Staff due to a violation of GitHub&#8217;s terms of service,\u00bb reads the message when attempting to access the \u00ab<a href=\"https:\/\/github.com\/Azure\/azure-functions-host\">Azure\/azure-functions-host<\/a>\u00bb repository. \u00abIf you are the owner of the repository, you may reach out to GitHub Support for more information.\u00bb<\/p>\n<p>According to OpenSourceMalware, some of the repositories impacted by the incident are listed below &#8211;<\/p>\n<ul>\n<li>azure-search-openai-demo-purviewdatasecurity<\/li>\n<li>Connectors-NET-LSP<\/li>\n<li>Connectors-NET-SDK<\/li>\n<li>durabletask<\/li>\n<li>durabletask-dotnet<\/li>\n<li>durabletask-go<\/li>\n<li>durabletask-js<\/li>\n<li>durabletask-mssql<\/li>\n<li>functions-container-action<\/li>\n<li>homebrew-functions<\/li>\n<li>llm-fine-tuning<\/li>\n<li>windows-driver-docs<\/li>\n<\/ul>\n<p>What&#8217;s notable about the latest campaign is the re-compromise of the \u00abdurabletask\u00bb PyPI package, which was infected by TeamPCP last month to deliver an information stealer on Linux systems.<\/p>\n<div class=\"dog_two clear\">\n<div class=\"cf\"><a href=\"https:\/\/thehackernews.uk\/ai-cant-stop-d\" rel=\"nofollow noopener sponsored\" target=\"_blank\"><img loading=\"lazy\" decoding=\"async\" class=\"lazyload\" alt=\"Cybersecurity\" src=\"https:\/\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEjPEV6-530TOlxG6PjrmdlY623wpBwduZ7t1HV6flcmO5R4q4AmfixDUzW0CrhlvMVNWbhvOIso-UDNTka4W_W9Chrdj_dglwBZwi7DuePM2IMIl-hfUYVIqBXgfpr_2619K8Gptb4LzwJ6gUbi7lWl2M8AFQJsHEaw63Q7tZ6708YGruiHrr0Y2W9YYxLQ\/s728-e100\/ThreatLocker-d.png\" width=\"729\" height=\"91\"\/><\/a><\/div>\n<\/div>\n<p>\u00abA month later, not only is Azure\/durabletask gone &#8211; so is every sibling repo in the Durable Task ecosystem, sitting one org over in Microsoft: the .NET, Go, Java, JS, MSSQL, Netherite, and protobuf implementations, plus the Durable Functions monitor,\u00bb security researcher Paul McCarty (aka 6mile) said.<\/p>\n<p><a name=\"more\"\/><\/p>\n<p>\u00abWhen the repo at the root of last month&#8217;s compromise is the hub of this month&#8217;s takedown, that is not a coincidence &#8211; that is the same wound reopening. Whoever held those credentials in May plausibly never fully lost them.\u00bb<\/p>\n<div class=\"separator\" style=\"clear: both;\"><a href=\"https:\/\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEhemNR9h_g1pzbtSuNnKWfQIxypfGLWb52x73fTBT1EhzNvDMk7ko7Gt6UPk2IkMPHd1N3TLkYDJmCi1gxMLbale7wTeVdxUfX67kY5D3rGDsiW12pRHdEAMhylTCo-GOikjN6IEJQkgTQ_xH0zDi9LShfBUXh14P9JS7ROjez0Z8vsXJZzHlGS8S6S7WjN\/s1700-e365\/githubs.jpg\" style=\"display: block;  text-align: center; clear: left; float: left;\"><img decoding=\"async\" src=\"https:\/\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEhemNR9h_g1pzbtSuNnKWfQIxypfGLWb52x73fTBT1EhzNvDMk7ko7Gt6UPk2IkMPHd1N3TLkYDJmCi1gxMLbale7wTeVdxUfX67kY5D3rGDsiW12pRHdEAMhylTCo-GOikjN6IEJQkgTQ_xH0zDi9LShfBUXh14P9JS7ROjez0Z8vsXJZzHlGS8S6S7WjN\/s1700-e365\/githubs.jpg\" alt=\"\" border=\"0\" data-original-height=\"916\" data-original-width=\"1502\"\/><\/a><\/div>\n<p>Miasma is assessed to be a variant of the Mini Shai-Hulud worm that TeamPCP <a href=\"https:\/\/www.akamai.com\/blog\/security-research\/mini-shai-hulud-worm-returns-goes-public\">publicly released<\/a> in mid-May 2026. It has since continued to mutate and refine its tactics, even as it has <a href=\"https:\/\/www.ox.security\/blog\/600000-monthly-downloads-affected-miasma-supply-chain-attack-is-back-on-npm\/\">infected more packages<\/a> over the past couple of days, using <a href=\"https:\/\/x.com\/OX__Security\/status\/2063025560738050373\">various descriptions<\/a> for the newly-created public repositories containing the stolen secrets &#8211;<\/p>\n<ul>\n<li>Miasma: The Spreading Blight<\/li>\n<li>Miasma : The Spreading Blight<\/li>\n<li>Miasma &#8211; The Spreading Blight<\/li>\n<li>Hades &#8211; The End for the Damned<\/li>\n<\/ul>\n<p>As of writing, there are <a href=\"https:\/\/github.com\/search?q=%22Hades%20The%20End%20for%20the%20Damned%22&amp;type=repositories\">13 repositories<\/a> with the description \u00abHades &#8211; The End for the Damned\u00bb and <a href=\"https:\/\/github.com\/search?q=%22Miasma+The+Spreading+Blight%22&amp;type=repositories\">82 repositories<\/a> with the remaining three naming patterns.<\/p>\n<p>Miasma has also been observed skipping the npm registry entirely, with the threat actors pushing malicious code directly to \u00abicflorescu\/mantine-datatable\u00bb and four related repositories: \u00abmantine-contextmenu,\u00bb \u00abnext-server-actions-parallel,\u00bb \u00abmantine-datatable-v6,\u00bb and \u00abmantine-contextmenu-v6.\u00bb<\/p>\n<p>\u00abThe commit added no dependencies. It planted a 4.3 MB payload runner and wired it to execute automatically through five developer tools: Claude Code, Gemini CLI, Cursor, VS Code, and the npm test script,\u00bb SafeDep <a href=\"https:\/\/safedep.io\/miasma-worm-ai-coding-agent-config-injection\/\">said<\/a>. \u00abThe attack detonates when a developer clones one of the affected repos and opens it in an AI coding agent. The dropper is the same staged Bun loader, here repurposed for GitHub source-repo persistence rather than registry poisoning.\u00bb<\/p>\n<div class=\"dog_two clear\">\n<div class=\"cf\"><a href=\"https:\/\/thehackernews.uk\/vpn-threat-report-m\" rel=\"nofollow noopener sponsored\" target=\"_blank\"><img loading=\"lazy\" decoding=\"async\" class=\"lazyload\" alt=\"Cybersecurity\" src=\"https:\/\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEhFlTC7RrRZGiFAgASS0noWSL0qsQGFVp8-Hvuw9yp3X3VKRuTcb5SsPX09wJzrdIM6pu1_5lS4EeZp7Sx4iYBpNJkrGnpr08yyaS1HQ5_5TxaCsP6O0OtHNuOkesn6CbNjao1GPulCJk-uljYMSfMZfBYNrngpe669t7jlRn1FqiEnXhsFD1WVkpaYIVgh\/s728-e100\/ai-d.jpg\" width=\"729\" height=\"91\"\/><\/a><\/div>\n<\/div>\n<p>These software supply chain attacks have <a href=\"https:\/\/www.uvcyber.com\/resources\/reports\/threat-advisory-tanstack-supply-chain-attack\">exposed<\/a> the underlying weaknesses in the trust model that forms the basis of software delivery in open-source ecosystems, making it one of the most significant and sustained campaigns observed to date. What separates the activity from other incidents is its ability to exponentially propagate across the ecosystem by compromising downstream users and repeating the same cycle.<\/p>\n<p>\u00abThe worm&#8217;s genius and the reason conventional defences largely failed is that it operates entirely within legitimate channels. It does not exploit a vulnerability in npm or GitHub,\u00bb FalconFeeds.io <a href=\"https:\/\/falconfeeds.io\/blogs\/shai-hulud-npm-pypi-supply-chain-worm-analysis\/\">said<\/a>. \u00abIt exploits the trust model those platforms are built on: the assumption that if a package is signed with a valid key and published by an authenticated maintainer, it is safe.\u00bb<\/p>\n<p>\u00abShai-Hulud compromises the key and the maintainer, then proceeds to act exactly as a legitimate publisher would. From the registry&#8217;s perspective, every malicious publish event is indistinguishable from a routine update.\u00bb<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>\ue804Ravie Lakshmanan\ue802Jun 06, 2026Supply Chain Attack \/ Malware Microsoft&#8217;s GitHub repositories have become the latest to fall victim to the ongoing Miasma self-replicating supply chain attack campaign. The incident impacted&hellip;<\/p>\n","protected":false},"author":1,"featured_media":1203,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[220,219,71,825,1117,1856,147,1738,218,821],"class_list":["post-1202","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-attack","tag-chain","tag-github","tag-hits","tag-major","tag-miasma","tag-microsoft","tag-repositories","tag-supply","tag-worm"],"_links":{"self":[{"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=\/wp\/v2\/posts\/1202","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1202"}],"version-history":[{"count":0,"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=\/wp\/v2\/posts\/1202\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=\/wp\/v2\/media\/1203"}],"wp:attachment":[{"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1202"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1202"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1202"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}