registry / @cloop/runner / 0.3.13
@cloop/runner@0.3.13
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 13d ago · by lpm-firewall-aiThe flagged session-file access feeds the runner’s presence feature, and the inspected source does not show credential collection or an unrelated recipient. The manifest has no install lifecycle hook, and the remaining flagged behavior did not establish a concrete attack.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user connects and runs the runner, which sends periodic presence updates.
Impact
The inspected source supports package-aligned presence behavior and does not establish an attack surface.
Mechanism
The runner reads recent Claude session files and places session metadata in its presence update.
AI rationale
The flagged session-file access feeds the runner’s presence feature, and the inspected source does not show credential collection or an unrelated recipient. The manifest has no install lifecycle hook, and the remaining flagged behavior did not establish a concrete attack.
Evidence
dist/box-DTLW25MA.js
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI and has no install lifecycle hook.
- The runner reads recent Claude session metadata and includes it in its periodic presence update when other-thread sharing is enabled.
- The inspected dependency files show MCP server transport code and the ws package’s normal client and server implementation; no install scripts were indicated.
Evidence against
- Session sharing is part of the runner’s presence behavior; the inspected source does not establish an unrelated recipient or credential transfer.
- The flagged child-process helper runs supplied steps, while the other flagged file handles local run records.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggeddist/chunk-6OWQEIFN.jsView file
17// src/commands/runs.ts
L18: import { spawnSync } from "child_process";
L19: import {
High
Child Process
Package source references child process execution.
dist/chunk-6OWQEIFN.jsView on unpkg · L17dist/chunk-T3B3OPMM.jsView file
31windowsExecutable,
L32: windowsPowerShellEnv,
L33: writeBoxConfig
...
L89: import { delimiter, join, posix, win32 } from "path";
L90: var CODEX_RELEASES = "https://github.[redacted]";
L91: var CODEX_TRIPLES = {
...
L104: var psQuote = (value) => `'${value.replace(/'/g, "''")}'`;
L105: function codexInstallCommand(home, platform = process.platform, arch = process.arch) {
L106: const asset = codexAsset(platform, arch);
...
L174: }
L175: function findLocalCodex(home, env = process.env) {
L176: findIn(codexBinDir(home), "codex", env);
High
Sandbox Evasion Gated Capability
Source gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
dist/chunk-T3B3OPMM.jsView on unpkg · L31Findings
1 Critical3 High3 Medium5 Low
CriticalPrevious Version Dangerous Deltadist/box-DTLW25MA.js
HighChild Processdist/chunk-6OWQEIFN.js
HighSandbox Evasion Gated Capabilitydist/chunk-T3B3OPMM.js
HighRuntime Package Installdist/chunk-T3B3OPMM.js
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.13.
See all versions of @cloop/runner for other recorded verdicts.
- Review the evidence and your use of @cloop/runner@0.3.13 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.