Config files for AI coding assistants can run commands on developer machines, so reviews must check them
POLICYAnthropicredteam/daily · 1 source
- Severity
- Medium
- Sources
- 1
What happened
The article argues that merging a configuration change for an AI coding assistant can distribute execution instructions to everyone working in the repository. It cites StepSecurity's October 8 analysis of the June Miasma campaign, which planted AI-tool and editor configuration in a Microsoft repository to harvest credentials, and recommends named owners, enforced review through branch protection, and checks on user-level and shared skills and plugins.
For IT people · Written by AI from 1 source · Wrong?
What to do
- Treat changes to AI assistant configuration files, hooks and skills as executable code and review what they can trigger before approving them.
- Require a code owner to approve these files through branch protection, and check the rule with a sample pull request.
- Retest any control that was checked only at a developer terminal in the automated workflow that uses the same repository.
- Review the shared skills, plugins and user-level configuration that developers load outside the project.
Written by AI from the sources, checked against them
Full story timeline · 1 update
Who reported · 1 outlet
CSO Online
Who and what is in it
Products