registry / @cloop/runner / 0.2.9
@cloop/runner@0.2.9
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-aiSource inspection shows the flagged process execution is tied to explicit disconnect and takeover commands, with disconnect targeting the package’s own service and takeover resuming a selected run. The inspected files establish no malicious behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user invokes the disconnect or takeover command.
Impact
No harmful effect beyond the requested local service removal or run handoff was established.
Mechanism
Disconnect stops the package’s registered service and removes its files after revocation; takeover resumes the selected run with the configured local harness.
AI rationale
Source inspection shows the flagged process execution is tied to explicit disconnect and takeover commands, with disconnect targeting the package’s own service and takeover resuming a selected run. The inspected files establish no malicious behavior.
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a command-line entrypoint and lists development scripts.
- The flagged disconnect module is loaded only for the explicit disconnect command.
- Disconnect uses platform service-control commands to stop the package’s own registered service.
- Disconnect revokes the device and then removes its service and runner files.
- Takeover looks up the run selected by the command argument and checks its state.
- Takeover resumes that run with the configured local harness in the run’s repository.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggeddist/disconnect-H3RDATJF.jsView file
30// src/commands/disconnect.ts
L31: import { execFileSync } from "child_process";
L32: import { existsSync, readFileSync, rmSync } from "fs";
High
Child Process
Package source references child process execution.
dist/disconnect-H3RDATJF.jsView on unpkg · L3030// src/commands/disconnect.ts
L31: import { execFileSync } from "child_process";
L32: import { existsSync, readFileSync, rmSync } from "fs";
L33: import { homedir } from "os";
L34: var DONE_LINE = "This computer is no longer a Cloop runner. To connect it again: npx -y @cloop/runner connect";
L35: function unitOrigin(contents) {
High
Runtime Package Install
Package source invokes a package manager install command at runtime.
dist/disconnect-H3RDATJF.jsView on unpkg · L30dist/chunk-3PIT6YXL.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @cloop/runner@0.2.1
matchedIdentity = npm:QGNsb29wL3J1bm5lcg:0.2.1
similarity = 0.524
summary = stored previous version shares package body but lacks this dangerous source file
Findings
1 Critical2 High3 Medium6 Low
CriticalPrevious Version Dangerous Deltadist/chunk-3PIT6YXL.js
HighChild Processdist/disconnect-H3RDATJF.js
HighRuntime Package Installdist/disconnect-H3RDATJF.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowAi Review Evidencepackage.json
LowAi Review Evidencedist/index.js
Affected versions and remediation
This report applies to @cloop/runner@0.2.9.
See all versions of @cloop/runner for other recorded verdicts.
- Review the evidence and your use of @cloop/runner@0.2.9 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.