IDE extension community
Risk level
critical
100/100

Roo Code ↗

Roo Code is a community-maintained IDE extension from Roo 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

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

Roo Code is an open-source AI coding agent for VS Code, originally forked from Cline and now developed independently with expanded provider support, more granular permission modes, and a community focused on configurability. Like its upstream, Roo Code can drive an entire feature end-to-end: planning a change, editing files in batches, running tests in the terminal, and reaching out to MCP servers for additional tools.

The extension's declared capabilities span filesystem read and write across the workspace, shell execution for builds and tests, outbound network connections to the configured LLM provider, and access to provider API keys and tokens stored in the secret store. Operators can install custom "modes" that further widen or narrow that surface — for example, an architect mode that can plan but not execute, or a code mode with the full toolbelt.

Because Roo Code is community-maintained and inherits the shell + network + credentials trio, it triggers both the data-exfiltration and credential-theft dangerous combinations in Anomity's catalog. The recommended posture is to enable the most restrictive mode that meets the team's need, restrict tools at the MCP server level, and avoid running it under accounts that hold production credentials.

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