Incident report · Supply chain
Attackers turn GitHub issues into supply chain campaign against 61 public repos in less than an hour
Attackers launched a supply chain campaign targeting 61 public GitHub repositories. In less than an hour, they exploited GitHub issues to automatically trigger vulnerable workflows. The attack was executed successfully within a second of the workflow activation. This method allowed rapid compromise across multiple projects.
- Discovered
- Oct 29 2026
- Failure mode
- Supply chain
- Source
- The Register · Oct 29 2026
- Impact
- 61 public repositories were compromised via automated workflow execution.
Summary from the public record. The failure mode’s analysis follows.
The agent was fine. Everything it trusted was not.
How Fencio prevents this
The agent trusted a component it had never verified: a package, an extension, a skill, or a server that looked legitimate. When that component changed or was compromised, the agent carried the payload straight into a trusted environment.
Fencio inventories every tool, server, and skill an agent can reach, pins their versions and declared capabilities, and blocks calls when a component starts doing something its manifest never declared, like reading env files or mailing new recipients.
Runtime policy example · Supply chainLive
- 13:12:48mcp.tool upload_file(.env)Capability not in pinned manifestBlock
- 13:15:05mcp.tool lint(src/)Manifest match · v1.4.2Allow
- 13:18:22pkg.install(unverified-name)Package not in approved registryBlock
Say yes to the AI your business wants.
Book a 30-minute call. Bring your agents and your rules.