Notifications
Clear all
Topic starter
20/08/2026 5:43 pm
TL;DR: The Claude Code leak exposed structural attack surfaces in coding agents, including memory poisoning, command chaining, and cross-tool privilege escalation, according to Fiddler. It also showed that most enterprises lack visibility into agent activity, tool use, and governance records, and the lesson is that coding-agent adoption now depends on runtime controls, not post-incident review.
NHIMG editorial — based on content published by Fiddler: The Claude Code Source Code Leak Is Fixed. Future Risks Aren't
By the numbers:
- 84% of developers use or plan to use AI coding tools.
- 90% of Fortune 100 companies use GitHub Copilot.
- 53% of Fortune 1000 companies use Cursor.
Questions worth separating out
Q: What fails when coding agents are allowed broad tool access without runtime controls?
A: The failure is usually not a single malicious command.
Q: Why do AI agents complicate existing IAM and PAM controls?
A: AI agents complicate IAM and PAM because they often inherit delegated credentials, operate across multiple systems, and keep acting after the initial approval moment has passed.
Q: How can security teams tell whether agent access is actually under control?
A: Look for evidence that the team can trace every tool call, secret use, and cross-system action back to a named owner and a valid approval path.
Practitioner guidance
- Build a complete coding agent inventory Discover every agent running in IDEs, CLIs, CI pipelines, and cloud workflows, then classify each by the tools, files, and networks it can touch.
- Enforce runtime policy at the tool boundary Block or alert on unsafe command sequences, unexpected file access, and unusual MCP interactions at execution time rather than after output is produced.
- Log full execution traces for every agent session Capture every tool call, permission decision, and policy outcome so security and compliance teams can reconstruct what happened if an agent behaves unexpectedly.
What's in the full article
Fiddler's full article covers the operational detail this post intentionally leaves for the source:
- The article breaks down the Claude Code leak mechanics, including the source map exposure, mirrored code, and the specific behaviours the leaked code revealed.
- It outlines the risk patterns in more implementation detail, including memory poisoning, command chaining, and cross-tool privilege escalation.
- It explains the four control layers Fiddler recommends for coding agents, including discovery, execution traces, runtime policy enforcement, and a governance record.
- It positions the AI Control Plane for coding agents as the vendor's implementation response, which is useful if you are evaluating control architecture choices.
👉 Read Fiddler's analysis of Claude Code source code leak risks for enterprise AI teams →
Coding agent security gaps: are enterprise controls keeping up?
Explore further
20/08/2026 6:26 pm
AI coding agents are becoming non-human identities, and that changes the control model. Once an agent can execute commands, access tools, and persist memory, it is no longer just an application feature. It becomes an identity-bearing runtime that needs discovery, scope control, and auditability across its lifecycle. IAM and PAM teams should stop treating agent access as an extension of developer privilege and instead govern it as a separate identity class.
A question worth separating out:
Q: Who is accountable when a coding agent makes an unsafe change?
A: Accountability should sit with the delegating owner of the workflow, the policy administrator who allowed the action, and the platform team that exposed the tool path. If the organisation cannot trace who authorised the task, which tools were available, and why the action was permitted, governance has failed.
👉 Read our full editorial: Coding agent security gaps outpace governance in enterprise AI
