registry / wildcrane-runner / 0.6.14
wildcrane-runner@0.6.14
WildCrane's Local Runner — connects this computer to WildCrane and runs its jobs on your local Claude Code, Codex, OpenCode or Cursor.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe flagged environment, network, and process behavior aligns with a CLI that connects a local runner to WildCrane and launches local agent tools. The inspected flows send WildCrane session credentials to its configured cloud services and selected provider credentials to the chosen agent; no unrelated credential collection or exfiltration was found.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review
Trigger
The runner starts when the user invokes the wildcrane-runner CLI; job and provider activity occurs as part of runner operation.
Impact
Observed network and process activity supports the package’s stated runner purpose; no credential exfiltration or unrelated automatic action was identified.
Mechanism
The runner refreshes its WildCrane session with Supabase, uses its session token for WildCrane API requests, and passes configured provider credentials to the selected local agent.
AI rationale
The flagged environment, network, and process behavior aligns with a CLI that connects a local runner to WildCrane and launches local agent tools. The inspected flows send WildCrane session credentials to its configured cloud services and selected provider credentials to the chosen agent; no unrelated credential collection or exfiltration was found.
Evidence
~/.wildcrane/machine.json
Network endpoints2
yajrbpprmdvtkvjjfpbk.supabase.coapi.ai4kanban.dev
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exposes a CLI entry point, and the launcher starts its bundled runner when invoked.
- Session refresh tokens go to the configured Supabase authentication endpoint; cloud API requests use the runner’s session token.
- Provider credentials are removed from inherited environment variables and added to the selected agent’s environment from its settings.
Evidence against
- The launcher and runner use process execution and network access as part of the package’s stated purpose: connecting a local runner to WildCrane and running jobs with local agent CLIs.
- The manifest declares a prepare build script, but the package snapshot contains no scripts/build.mjs and the hook is not an install lifecycle hook.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
9 flaggeddist/akb/dist/kanban.mjsView file
58* Constructs the CommanderError class
L59: * @param {number} exitCode suggested exit code which could be used with process.exit
L60: * @param {string} code an id string representing the error
...
L1168: var EventEmitter = __require("node:events").EventEmitter;
L1169: var childProcess = __require("node:child_process");
L1170: var path87 = __require("node:path");
...
L1218: this._outputConfiguration = {
L1219: writeOut: (str5) => process2.stdout.write(str5),
L1220: writeErr: (str5) => process2.stderr.write(str5),
...
L1257: * @returns {Command[]}
L1258: * @private
L1259: */
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
dist/akb/dist/kanban.mjsView on unpkg · L581168var EventEmitter = __require("node:events").EventEmitter;
L1169: var childProcess = __require("node:child_process");
L1170: var path87 = __require("node:path");
High
Child Process
Package source references child process execution.
dist/akb/dist/kanban.mjsView on unpkg · L11682008}
L2009: const execArgv = process2.execArgv ?? [];
L2010: if (execArgv.includes("-e") || execArgv.includes("--eval") || execArgv.includes("-p") || execArgv.includes("--print")) {
Findings
1 Critical5 High5 Medium6 Low
CriticalCredential Exfiltrationdist/akb/dist/kanban.mjs
HighChild Processdist/akb/dist/kanban.mjs
HighShelldist/akb/dist/kanban.mjs
HighSame File Env Network Executiondist/launcher.mjs
HighCommand Output Exfiltrationdist/akb/dist/kanban.mjs
HighKnown Malware Source Similaritydist/akb/dist/kanban.mjs
MediumDynamic Requiredist/akb/bin/ai4kanban.mjs
MediumNetwork
MediumEnvironment Vars
MediumOversized Source Filedist/runner.mjs
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
Affected versions and remediation
This report applies to wildcrane-runner@0.6.14.
See all versions of wildcrane-runner for other recorded verdicts.
- Review the evidence and your use of wildcrane-runner@0.6.14 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.