@octavus/agent@1.0.28
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 14d ago · by lpm-firewall-aiStatic inspection found a user-invoked cloud agent CLI with package-aligned network use and no install lifecycle hook. The flagged command execution and project-context collection fit the package’s runtime agent function; no concrete attack behavior was established.
Decision evidence
public snapshot- The manifest exposes a CLI and declares no install lifecycle hook.
- The agent reads workspace instruction and command files to build its runtime context; this is an explicit cloud-agent feature.
- The CLI’s default platform endpoint is Octavus, and it stores configuration under the user’s .octavus directory.
- The required executable paths contain bundled CLI or MCP entrypoints; the screen publisher uses the caller’s LiveKit settings.
- The cited bundled browser and filesystem artifacts are package components, with no reviewed excerpt establishing a malicious action.
Source & flagged code
13 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.28.
See all versions of @octavus/agent for other recorded verdicts.
- Review the evidence and your use of @octavus/agent@1.0.28 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.