runcastle@1.3.2
Burn tickets into shipped features with Claude Code.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe update check transmits only an install ID, version, and platform, with a DO_NOT_TRACK opt-out. Because the README does not disclose the persistent identifier, this is suspicious runtime telemetry rather than evidence of credential theft.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Automatically when the server starts.
Impact
The endpoint can correlate update checks from the same installation over time.
Mechanism
Posts a persistent install ID, package version, and platform to the package's update ping endpoint; DO_NOT_TRACK switches the check to the npm registry.
AI rationale
The update check transmits only an install ID, version, and platform, with a DO_NOT_TRACK opt-out. Because the README does not disclose the persistent identifier, this is suspicious runtime telemetry rather than evidence of credential theft.
Evidence
index.jsREADME.mddataDir()/install-id
Network endpoints2
ping.runcastle.dev/pingregistry.npmjs.org/runcastle/latest
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The update ping sends a persisted install ID, package version, and platform to ping.runcastle.dev.
- Starting the server triggers the update lookup automatically.
- The README mentions an in-app update banner but does not disclose sending a persistent install ID; DO_NOT_TRACK is supported as an opt-out.
Evidence against
- The manifest describes a server application and exposes its launcher as the runcastle command.
- The inspected credential-saving flow writes a user-provided token to the local .env file for AFK use; no forwarding to an unrelated host was found.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsMinifiedPossibleObfuscationUrlStrings
Source & flagged code
8 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 unpkg1193// src/pty/kill-tree.ts
L1194: import { spawn } from "child_process";
L1195: function taskkillTree(pid) {
High
Child Process
Package source references child process execution.
bin/runcastle.jsView on unpkg · L11931125if (/\.(cmd|bat)$/i.test(resolved)) {
L1126: return { file: process.env.ComSpec ?? "cmd.exe", args: ["/c", resolved, ...args] };
L1127: }
High
Findings
1 Critical5 High4 Medium4 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
HighCross File Remote Execution Contextbin/runcastle.js
MediumDynamic Requirepty-host.cjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowWeak Cryptobin/runcastle.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to runcastle@1.3.2.
See all versions of runcastle for other recorded verdicts.
- Review the evidence and your use of runcastle@1.3.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.