The default server and daemon expose the task API on all interfaces without an authentication layer, while headless operation automatically approves tool use. This creates a serious remote-control risk for reachable instances, though it is a vulnerability in the server’s defaults rather than evidence of malicious package intent.
Static reason
No blocking static signals were detected.
Trigger
A remote caller sends a request to the running server; headless operation is the default for the detached daemon.
Impact
A reachable instance may let an attacker direct the agent to perform tool actions in the configured project, potentially including command execution or file access; callers can also stop the server.
Mechanism
The /v1/messages route passes caller-controlled task content to the orchestrator, while headless mode selects automatic tool approval.
Evidence
dist/index.jsdist/routes/messages.jsbin/cortex-daemon.jsprocess.cwd() project files accessible to agent toolsprocess.cwd()/logs/nexus-cortex-<timestamp>.logprocess.cwd()/logs/nexus-cortex-<timestamp>.error.log