# 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.

- **Canonical URL:** https://catalog.anomity.ai/extension/kilo-code
- **Kind:** IDE extension
- **Publisher:** Kilo Code
- **Trust level:** community
- **Risk score:** 100/100 (critical)
- **Website:** https://kilocode.ai
- **Last updated:** 2026-09-02
- **JSON:** https://catalog.anomity.ai/api/entries/extension/kilo-code

## Description

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 it scored 100

The score starts at the catalog's neutral base of 50 and moves only through the signals below. The formula is published at https://catalog.anomity.ai/about — there is no model and no hidden heuristic.

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

Clamped result: **100/100**, band **critical**.

## Capabilities

| Capability | Name | Security implication |
| --- | --- | --- |
| `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

### Data exfiltration risk (high)

Shell execution combined with outbound network access can exfiltrate arbitrary data from the machine.

Capabilities: `shell:execute`, `network:outbound`

### Credential theft risk (high)

Filesystem write combined with credentials access can plant persistent credential stealers.

Capabilities: `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).

Capabilities: `shell:execute`, `filesystem:write`

### Full-control risk (critical)

Shell + filesystem write + network is effectively a remote shell on the employee machine.

Capabilities: `shell:execute`, `filesystem:write`, `network:outbound`

## Related IDE extensions

- [Claude Code for VS Code](https://catalog.anomity.ai/extension/claude-code-for-vscode) — risk 100 (critical)
- [Cline](https://catalog.anomity.ai/extension/cline) — risk 100 (critical)
- [OpenAI Codex for VS Code](https://catalog.anomity.ai/extension/openai-codex-vscode) — risk 100 (critical)
- [Roo Code](https://catalog.anomity.ai/extension/roo-code) — risk 100 (critical)
- [Refact.ai](https://catalog.anomity.ai/extension/refact-ai) — risk 100 (critical)
- [Continue](https://catalog.anomity.ai/extension/continue) — risk 75 (high)

---

Source: Anomity Catalog (https://catalog.anomity.ai/). Scoring methodology: https://catalog.anomity.ai/about. Machine-readable index: https://catalog.anomity.ai/llms.txt · https://catalog.anomity.ai/openapi.json