runcastle@1.4.2
Burn tickets into shipped features with Claude Code.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe source shows default startup telemetry to the package’s own update endpoint, with a persistent install ID and no README disclosure. The payload is limited and DO_NOT_TRACK provides an opt-out, so this warrants a warning rather than a malicious verdict.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Server startup, unless DO_NOT_TRACK is set.
Impact
The service can associate update checks with a persistent installation identifier. No credential or project content is sent in this request.
Mechanism
The startup update check POSTs the install ID, current version, and platform to https://ping.runcastle.dev/ping; when tracking is disabled, it checks npm for the latest version.
AI rationale
The source shows default startup telemetry to the package’s own update endpoint, with a persistent install ID and no README disclosure. The payload is limited and DO_NOT_TRACK provides an opt-out, so this warrants a warning rather than a malicious verdict.
Evidence
index.jsinstall-id under the configured runcastle data directory
Network endpoints2
ping.runcastle.dev/pingregistry.npmjs.org/runcastle/latest
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Server startup calls the update check automatically.
- By default, the update check posts a persistent install ID, package version, and platform to the project’s ping endpoint.
- Setting DO_NOT_TRACK skips that ping and uses the npm version endpoint instead.
Evidence against
- The ping sends only an install ID, version, and platform; no credentials or project data appear in its payload.
- The prompted API credential is saved to the local ~/.runcastle/.env file for use by the selected agent runtime.
- The manifest has no lifecycle scripts.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShellWebSocket
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
Source & flagged code
9 flaggedbin/runcastle.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = runcastle@1.2.11
matchedIdentity = npm:cnVuY2FzdGxl:1.2.11
similarity = 0.600
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
bin/runcastle.jsView on unpkg1316// src/pty/kill-tree.ts
L1317: import { spawn } from "child_process";
L1318: function taskkillTree(pid) {
High
Child Process
Package source references child process execution.
bin/runcastle.jsView on unpkg · L13161248if (/\.(cmd|bat)$/i.test(resolved)) {
L1249: return { file: process.env.ComSpec ?? "cmd.exe", args: ["/c", resolved, ...args] };
L1250: }
High
Findings
1 Critical6 High4 Medium5 Low
CriticalPrevious Version Dangerous Deltabin/runcastle.js
HighChild Processbin/runcastle.js
HighShellbin/runcastle.js
HighSame File Env Network Executionbin/runcastle.js
HighCredential Redirect Persistenceindex.js
HighCommand Output Exfiltrationbin/runcastle.js
HighCross File Remote Execution Contextbin/runcastle.js
MediumDynamic Requirepty-host.cjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowEval
LowWeak Cryptobin/runcastle.js
LowFilesystem
Affected versions and remediation
This report applies to runcastle@1.4.2.
See all versions of runcastle for other recorded verdicts.
- Review the evidence and your use of runcastle@1.4.2 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.