registry / @cloop/runner / 0.3.0
@cloop/runner@0.3.0
Make your machine and your agents Cloop runners: device login, the runner daemon, the Cloop MCP server, and Claude Code hooks.
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe manifest declares no install lifecycle hook. The flagged process and network activity are part of the user-invoked runner workflow, and the inspected source did not establish concrete attack behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user invokes a CLI command; local runner work begins through the configured runner workflow.
Impact
No unauthorized credential transfer, unrequested account action, or hidden install-time mutation was established.
Mechanism
The flagged package-manager text is reconnect guidance. Runtime process and network activity support the runner’s stated function.
AI rationale
The manifest declares no install lifecycle hook. The flagged process and network activity are part of the user-invoked runner workflow, and the inspected source did not establish concrete attack behavior.
Network endpoints2
mcp.mycloop.commcp-staging.mycloop.com
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with high false-positive risk.
Evidence for AI clean decision
- The manifest lists build and development scripts but declares no install lifecycle hook.
- The flagged npx command is generated as reconnection guidance; the disconnect command performs cleanup when explicitly invoked.
- The runner launches its configured agent in the selected repository, and its permission mapping uses ask mode unless full access is requested.
- Connection reports are sent to the configured service origin, which defaults to Cloop’s production or staging service.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggeddist/chunk-QLCIEJ4C.jsView file
24// src/drivers/local.ts
L25: import { execFile, execFileSync, spawn } from "child_process";
L26: import { chmodSync, mkdirSync, readFileSync, renameSync, writeFileSync } from "fs";
High
Child Process
Package source references child process execution.
dist/chunk-QLCIEJ4C.jsView on unpkg · L24dist/disconnect-WAQTAXN3.jsView file
31// src/commands/disconnect.ts
L32: import { execFileSync } from "child_process";
L33: import { existsSync, readFileSync, rmSync } from "fs";
L34: import { homedir } from "os";
L35: var DONE_LINE = "This computer is no longer a Cloop runner. To connect it again: npx -y @cloop/runner@latest connect";
L36: function unitOrigin(contents) {
High
Runtime Package Install
Package source invokes a package manager install command at runtime.
dist/disconnect-WAQTAXN3.jsView on unpkg · L31dist/chunk-EN3XHHWJ.js#virtual:normalized:round1
Findings
1 Critical3 High3 Medium5 Low
CriticalPrevious Version Dangerous Deltadist/chunk-34XAQRBL.js
HighChild Processdist/chunk-QLCIEJ4C.js
HighRuntime Package Installdist/disconnect-WAQTAXN3.js
HighSemantic Analysis Limiteddist/chunk-EN3XHHWJ.js#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @cloop/runner@0.3.0.
See all versions of @cloop/runner for other recorded verdicts.
- Review the evidence and your use of @cloop/runner@0.3.0 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.