1-minute read
What a defender needs to know
StepSecurity now inventories Claude Code and Codex plugins in two places: Dev Machine Guard shows installations on developer machines, while GitHub > AI Agents shows plugins published by organization repositories and those enabled in repository settings. A plugin can bundle hooks and MCP servers that run with the developer’s privileges. The company is describing its own product; the earlier incidents cited in its announcement used related extension or repository mechanisms, not agent plugins.
The endpoint view records version, installation scope, enabled state, marketplace and the separate source of plugin files. The repository view places manifest-declared author and repository beside the repository, folder, branch and commit StepSecurity scanned. Look for a declared publisher that differs from the observed source. Project settings in .claude/settings.json can enable a plugin for contributors, but each contributor still installs it on their machine. Dev Machine Guard agent v1.17.0 or later is required for the endpoint inventory.
Review both views for a plugin you cannot account for. Remove the repository enablement through a reviewed change and disable affected machine installations; then confirm the “Used by” listing and device states changed. A disabled plugin remains installed and visible for follow-up.