--- title: Attackers turn GitHub issues into supply chain campaign... description: Researchers at Radware found at least 83 malicious GitHub issues, pull requests, or comments across 61 public repositories, including LangExtract, Trivy, Brave... canonical: https://daily.dev/posts/attackers-turn-github-issues-into-supply-chain-campaign-against-61-public-repos-in-less-than-an-hour-qwkbo76ob twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Attackers turn GitHub issues into supply chain campaign against 61 public repos in less than an hour | daily.dev og:description: Researchers at Radware found at least 83 malicious GitHub issues, pull requests, or comments across 61 public repositories, including LangExtract, Trivy, Brave... og:url: https://daily.dev/posts/attackers-turn-github-issues-into-supply-chain-campaign-against-61-public-repos-in-less-than-an-hour-qwkbo76ob og:image: https://api.daily.dev/og/posts/qwkbo76ob.png og:image:alt: Attackers turn GitHub issues into supply chain campaign against 61 public repos in less than an hour og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Attackers turn GitHub issues into supply chain campaign against 61 public repos in less than an hour **[The Register](https://daily.dev/sources/theregister)** · 5 min read · 0 upvotes · 0 comments ## Summary Researchers at Radware found at least 83 malicious GitHub issues, pull requests, or comments across 61 public repositories, including LangExtract, Trivy, Brave browser, and MLflow. Most of the 77 malicious items were posted within a 43-minute window on September 1, with six more following within two minutes. The attacker, likely one person using 74 compromised accounts, hid shell commands in HTML comments that trigger vulnerable GitHub Actions workflows, attempting to exfiltrate environment variables and secrets. Researchers recommend least-privilege CI/CD permissions and treating external content as untrusted. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How are attackers using GitHub issues to compromise CI/CD pipelines? Attackers hide malicious shell commands inside HTML comments in a GitHub issue, pull request, or comment, which stays invisible on the rendered page. If the repository's workflow is configured to trigger on that event and injects the content directly into shell code, the command executes automatically within a second, harvesting environment variables and exfiltrating them to an attacker-controlled server. _Teams hardening CI/CD against untrusted triggers can track emerging GitHub Actions attack patterns on daily.dev._ ### Which popular open source GitHub repositories were hit by the September 2026 GitHub Actions supply chain campaign? Radware researchers identified 83 malicious items across 61 repositories, including agno-agi/agno (42.7K stars), ToolJet/ToolJet, google/langextract, aquasecurity/trivy, CopilotKit/CopilotKit, QwenLM/qwen-code, mlflow/mlflow, discordjs/discord.js, cilium/cilium, brave/brave-browser, and github/docs. Most maintainers were notified and fixed or closed the issue, though not all fixes were confirmed. _Maintainers tracking which major projects got hit by supply chain campaigns follow incident reports like this on daily.dev._ ### How can I protect GitHub Actions workflows from malicious issue or pull request content? Apply least-privilege access to CI/CD workflows and separate workflows triggered by external events, like issues or pull requests, from jobs that hold elevated permissions. Treat all external content such as issue text or PR comments as untrusted, and limit the secrets and environment variables exposed to any workflow that can be triggered externally. _Developers locking down CI/CD against external-trigger abuse keep up with workflow security guidance on daily.dev._ ## Similar posts on daily.dev - [Four Credential-Harvesting Campaigns Hit Open Source Ecosystems in Two Weeks](https://daily.dev/posts/four-credential-harvesting-campaigns-hit-open-source-ecosystems-in-two-weeks-gtsbqgosw) · GitGuardian · 1 upvotes · 0 comments - [GitHub Actions abused by Megalodon attack to slip malicious commits into 5,500 repos](https://daily.dev/posts/github-actions-abused-by-megalodon-attack-to-slip-malicious-commits-into-5-500-repos-iymmmkb5w) · CSO Online · 3 upvotes · 0 comments - [The vulnerabilities nobody sees in your repository, and how to catch them before they merge](https://daily.dev/posts/the-vulnerabilities-nobody-sees-in-your-repository-and-how-to-catch-them-before-they-merge-qmufkovsn) · Medium · 1 upvotes · 0 comments - [GitHub disables Microsoft repos pushing password-stealing malware](https://daily.dev/posts/github-disables-microsoft-repos-pushing-password-stealing-malware-oglknbpvl) · BleepingComputer · 1 upvotes · 0 comments --- Tags: [#cyber](https://daily.dev/tags/cyber), [#github](https://daily.dev/tags/github), [#github-actions](https://daily.dev/tags/github-actions), [#devsecops](https://daily.dev/tags/devsecops), [#prompt-injection](https://daily.dev/tags/prompt-injection) [View this post on daily.dev](https://daily.dev/posts/attackers-turn-github-issues-into-supply-chain-campaign-against-61-public-repos-in-less-than-an-hour-qwkbo76ob) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Attackers turn GitHub issues into supply chain campaign against 61 public repos in less than an hour","url":"https://daily.dev/posts/attackers-turn-github-issues-into-supply-chain-campaign-against-61-public-repos-in-less-than-an-hour-qwkbo76ob","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/attackers-turn-github-issues-into-supply-chain-campaign-against-61-public-repos-in-less-than-an-hour-qwkbo76ob"},"datePublished":"2026-10-29T12:04:05.532Z","dateModified":"2026-10-29T12:05:17.356Z","description":"Researchers at Radware found at least 83 malicious GitHub issues, pull requests, or comments across 61 public repositories, including LangExtract, Trivy, Brave...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/e0994275216848f1e94f53692e10f45b?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/e0994275216848f1e94f53692e10f45b?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"The Register","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"The Register","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/66aa2113fdad463992ffcbf0e8963fda","url":"https://daily.dev/sources/theregister"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/attackers-turn-github-issues-into-supply-chain-campaign-against-61-public-repos-in-less-than-an-hour-qwkbo76ob","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"cyber,github,github-actions,devsecops,prompt-injection","timeRequired":"PT5M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"The Register","item":"https://daily.dev/sources/theregister"},{"@type":"ListItem","position":3,"name":"Attackers turn GitHub issues into supply chain campaign against 61 public repos in less than an hour"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/attackers-turn-github-issues-into-supply-chain-campaign-against-61-public-repos-in-less-than-an-hour-qwkbo76ob#faq","mainEntity":[{"@type":"Question","name":"How are attackers using GitHub issues to compromise CI/CD pipelines?","acceptedAnswer":{"@type":"Answer","text":"Attackers hide malicious shell commands inside HTML comments in a GitHub issue, pull request, or comment, which stays invisible on the rendered page. If the repository's workflow is configured to trigger on that event and injects the content directly into shell code, the command executes automatically within a second, harvesting environment variables and exfiltrating them to an attacker-controlled server. Teams hardening CI/CD against untrusted triggers can track emerging GitHub Actions attack patterns on daily.dev."}},{"@type":"Question","name":"Which popular open source GitHub repositories were hit by the September 2026 GitHub Actions supply chain campaign?","acceptedAnswer":{"@type":"Answer","text":"Radware researchers identified 83 malicious items across 61 repositories, including agno-agi/agno (42.7K stars), ToolJet/ToolJet, google/langextract, aquasecurity/trivy, CopilotKit/CopilotKit, QwenLM/qwen-code, mlflow/mlflow, discordjs/discord.js, cilium/cilium, brave/brave-browser, and github/docs. Most maintainers were notified and fixed or closed the issue, though not all fixes were confirmed. Maintainers tracking which major projects got hit by supply chain campaigns follow incident reports like this on daily.dev."}},{"@type":"Question","name":"How can I protect GitHub Actions workflows from malicious issue or pull request content?","acceptedAnswer":{"@type":"Answer","text":"Apply least-privilege access to CI/CD workflows and separate workflows triggered by external events, like issues or pull requests, from jobs that hold elevated permissions. Treat all external content such as issue text or PR comments as untrusted, and limit the secrets and environment variables exposed to any workflow that can be triggered externally. Developers locking down CI/CD against external-trigger abuse keep up with workflow security guidance on daily.dev."}}]} ```