Skip to content

MCP tools that act on remote hosts are labelled as local activity, and an offensive MCP server is not recognised #436

Open

Description

@blitzcrieg1

Context

jm33-m0/emp3r0r (about 1.8k stars, GPL-3.0, v5.9.0 on 2026-11-15) is a post-exploitation C2. Its emp3r0r mcp command exposes the operator surface as a stdio MCP server, and its README names Claude Code and Codex as the clients: the coding agent selects targets, runs modules, moves files and builds agents in natural language. Tools include ls, cat, cp, mv, rm, mkdir, ps, kill, socks_start, list_agents, read_job_output and module execution (core/internal/cc/mcp/).

So "a coding agent on a laptop attached to an offensive MCP server" is an off-the-shelf setup. Agentmetry would record those calls through the hooks or the MCP proxy. Two gaps follow. Neither was reproduced against a running emp3r0r; this is from its source and README.

1. Remote-acting tools read as local activity

emp3r0r's file tools take a path that names a file on the compromised target. With the location-key rule on the detection-pass branch (#435), mcp__emp3r0r__cat {"path": "/root/.ssh/id_rsa"} is tagged T1552.004 as a private-key read, and mcp__emp3r0r__rm {"path": ...} counts toward a deletion burst, both as if they happened on the recording machine. The record is useful; the meaning is wrong. Nothing in the event says the action ran somewhere else, and the tool cannot tell local from remote.

The same applies to any MCP server that operates on remote systems (SSH, cloud shells, remote desktops). Possible direction: an event field or trait for "acts on a remote target", set from a small list of known remote-acting servers or from the proxy's server config, and rules that keep remote and local evidence apart.

2. An offensive MCP server attached to an agent is not recognised

Nothing flags that an agent's MCP config, or its live tool calls, names a known C2 or offensive framework. agentmetry scan reads agent configs and could report it, and a live detection could fire on mcp__emp3r0r__* tool names or an emp3r0r mcp server command. This belongs to the MCP fingerprinting backlog.

Status

Feature work under the maintenance rule. Filed so the case is on record for the detection pass or a request from a named person. Not for 0.13.0.

🤖 Generated with Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    detection-ruleBehavioral sequence detectionenhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions