IDE extension community
Risk level
critical
100/100

Kilo Code ↗

Kilo Code is a community-maintained IDE extension from Kilo Code. Anomity scores its risk at 100 out of 100 (critical). It matches 4 dangerous capability combinations.

filesystem:read filesystem:write shell:execute network:outbound credentials:access

Analysis summary

Kilo Code is a community-maintained IDE extension from Kilo Code. Anomity scores its risk at 100 out of 100 (critical). It matches 4 dangerous capability combinations.

Kilo Code is a multi-model AI coding assistant for VS Code that combines the agentic execution loop pioneered by Cline and Roo Code with first-class MCP server integration and a marketplace of curated workflows. It supports OpenAI, Anthropic, Google, Mistral, local Ollama models, and any OpenAI-compatible endpoint, letting teams route different tasks to different models from a single extension.

In day-to-day use, Kilo Code reads files anywhere in the open workspace, writes edits across multiple files in a single turn, executes shell commands through the integrated terminal, calls out to model providers and MCP servers over the network, and stores provider credentials in the VS Code secret store. Each tool invocation can be configured to require explicit approval, batched approval, or full auto-approve.

Kilo Code is community-maintained, and the combination of shell execution plus outbound network and filesystem write plus credentials access matches both Anomity's data-exfiltration and credential-theft dangerous combinations. The recommended controls are workspace-only credential scopes, allow-listed shell commands, and turning on per-tool approval rather than auto-approve for any agent that has internet access.

Why this entry scored 100 out of 100

This profile starts at the catalog's neutral base of 50. Because the entry is community-maintained, trust adjusts the score by -10. Declared high-risk capabilities add +30 (capped at +30). It matches 4 dangerous capability combinations, which contribute additional severity weight. The clamped result is 100, placing it in the critical band.

See the full scoring formula →

Findings

  • Established community project Trust offset
    Contribution to score: -10
  • 3 high-risk capabilities: filesystem:write, shell:execute, credentials:access Critical
    Contribution to score: +30
  • Data exfiltration risk (high) High
    Evidence
    Shell execution combined with outbound network access can exfiltrate arbitrary data from the machine.
    Contribution to score: +15
  • Credential theft risk (high) High
    Evidence
    Filesystem write combined with credentials access can plant persistent credential stealers.
    Contribution to score: +15
  • Persistence + execution risk (medium) Medium
    Evidence
    Shell execution plus filesystem write means the agent can plant persistent backdoors (e.g. modifying startup scripts).
    Contribution to score: +5
  • Full-control risk (critical) Critical
    Evidence
    Shell + filesystem write + network is effectively a remote shell on the employee machine.
    Contribution to score: +25

Capabilities

Every capability the entry declares, with the security implication of each.

  • filesystem:read Filesystem read
    Can read files on the host system. Used for context, indexing, or analysis.
  • filesystem:write Filesystem write
    Can create, edit, or delete files on the host system. High-impact capability — anything from helpful edits to planting persistence.
  • shell:execute Shell execution
    Can run arbitrary shell commands. Combined with network access this becomes effectively a remote shell.
  • network:outbound Outbound network
    Can make outbound network requests. Required for hosted model providers and remote APIs; also the path for data exfiltration if combined with read access.
  • credentials:access Credentials access
    Reads provider API keys, OAuth tokens, or other secrets from the host keychain or environment.

Dangerous combinations matched

Capability pairings that compound into well-known attack patterns.

  • Data exfiltration risk high
    Shell execution combined with outbound network access can exfiltrate arbitrary data from the machine.
    shell:execute network:outbound
  • Credential theft risk high
    Filesystem write combined with credentials access can plant persistent credential stealers.
    filesystem:write credentials:access
  • Persistence + execution risk medium
    Shell execution plus filesystem write means the agent can plant persistent backdoors (e.g. modifying startup scripts).
    shell:execute filesystem:write
  • Full-control risk critical
    Shell + filesystem write + network is effectively a remote shell on the employee machine.
    shell:execute filesystem:write network:outbound