registry / @cloop/runner / 0.2.4
@cloop/runner@0.2.4
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 found no install hook or concrete attack behavior. The scanner's process execution and file-writing signals correspond to local runner setup and an explicit disconnect command.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user runs a CLI command such as connect or disconnect.
Impact
These operations implement the advertised runner lifecycle; the inspected code does not establish an attack.
Mechanism
The package uses a local T3 executable for runner operations, writes its box configuration during setup, and stops its named service during disconnect.
AI rationale
Source inspection found no install hook or concrete attack behavior. The scanner's process execution and file-writing signals correspond to local runner setup and an explicit disconnect command.
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a CLI and lists build, typecheck, development, lint, formatting, and test scripts; it defines no install lifecycle script.
- The CLI loads disconnect code only when the user selects the disconnect command.
- Disconnect stops the package's named service and removes its associated files; the flagged child process call runs the service's stop steps.
- The flagged chunk runs a locally discovered T3 executable with explicit arguments, and writes runner configuration to its configured box file during setup.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggeddist/disconnect-ZAVMFITZ.jsView file
28// src/commands/disconnect.ts
L29: import { execFileSync } from "child_process";
L30: import { existsSync, readFileSync, rmSync } from "fs";
High
Child Process
Package source references child process execution.
dist/disconnect-ZAVMFITZ.jsView on unpkg · L2828// src/commands/disconnect.ts
L29: import { execFileSync } from "child_process";
L30: import { existsSync, readFileSync, rmSync } from "fs";
L31: import { homedir } from "os";
L32: var DONE_LINE = "This computer is no longer a Cloop runner. To connect it again: npx -y @cloop/runner connect";
L33: function unitOrigin(contents) {
High
Runtime Package Install
Package source invokes a package manager install command at runtime.
dist/disconnect-ZAVMFITZ.jsView on unpkg · L28dist/chunk-M6U2YVEB.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @cloop/runner@0.2.1
matchedIdentity = npm:QGNsb29wL3J1bm5lcg:0.2.1
similarity = 0.619
summary = stored previous version shares package body but lacks this dangerous source file
Findings
1 Critical2 High3 Medium6 Low
CriticalPrevious Version Dangerous Deltadist/chunk-M6U2YVEB.js
HighChild Processdist/disconnect-ZAVMFITZ.js
HighRuntime Package Installdist/disconnect-ZAVMFITZ.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @cloop/runner@0.2.4.
See all versions of @cloop/runner for other recorded verdicts.
- Review the evidence and your use of @cloop/runner@0.2.4 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.