@octavus/agent@1.0.17
Octavus Agent CLI - run one of your cloud Octavus Agents on a machine you control, using that machine as the agent's computer. The agent lives in the cloud (fully configured and observable); the local machine only supplies the computer and the trigger.
AI Security Review
scanned 29d ago · by lpm-firewall-aiStatic inspection found a user-invoked automation CLI with local MCP helpers, not an install-time or covert attack chain. No lifecycle hook, self-dependency, or concrete exfiltration behavior was identified.
Decision evidence
public snapshot- The package declares a CLI entry point and no npm lifecycle hooks.
- The main CLI obtains an API key and connects its computer session to the configured operator service only after the user invokes it.
- The bundled MCP components use standard input/output or explicit allowed directories, and the browser bridge uses loopback networking.
- The code MCP limits full-file reads of oversized files.
Source & flagged code
12 flagged · loading sourcePackage source references child process execution.
dist/computer-mcp/dist/index.jsView on unpkg · L53Source file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/computer-mcp/dist/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to @octavus/agent@1.0.17.
See all versions of @octavus/agent for other recorded verdicts.
- Review the evidence and your use of @octavus/agent@1.0.17 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.