runcastle@1.4.6
Burn tickets into shipped features with Claude Code.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe source shows undisclosed telemetry that runs automatically at server startup, though it sends only an install ID, version and platform. This warrants a warning; the inspected credential and process-execution leads did not establish an attack.
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 service can associate update checks with an installation and observe its version and platform.
Mechanism
The update check POSTs a persistent random install ID, package version and platform to https://ping.runcastle.dev/ping; DO_NOT_TRACK instead checks npm.
AI rationale
The source shows undisclosed telemetry that runs automatically at server startup, though it sends only an install ID, version and platform. This warrants a warning; the inspected credential and process-execution leads did not establish an attack.
Evidence
index.jsruncastle data directory/install-id
Network endpoints2
ping.runcastle.devregistry.npmjs.org
Decision evidence
public snapshotAI called this Suspicious at 95.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- When the server starts, it automatically checks for updates.
- The default update check POSTs a persistent random install ID, package version and platform to ping.runcastle.dev.
- DO_NOT_TRACK switches the check to npm, but the package documentation does not disclose this runtime telemetry.
Evidence against
- The reported fields are limited to an install ID, version and platform; no credentials or project data are sent in this request.
- The package manifest declares 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.400
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 unpkg1378// src/pty/kill-tree.ts
L1379: import { spawn } from "child_process";
L1380: function taskkillTree(pid) {
High
Child Process
Package source references child process execution.
bin/runcastle.jsView on unpkg · L13781310if (/\.(cmd|bat)$/i.test(resolved)) {
L1311: return { file: process.env.ComSpec ?? "cmd.exe", args: ["/c", resolved, ...args] };
L1312: }
High
Findings
1 Critical6 High4 Medium5 Low
CriticalPrevious Version Dangerous Deltabin/runcastle.js
HighChild Processbin/runcastle.js
HighShellbin/runcastle.js
HighCredential Redirect Persistenceindex.js
HighCommand Output Exfiltrationbin/runcastle.js
HighCross File Remote Execution Contextbin/runcastle.js
HighSemantic Analysis Limitedweb/assets/index-7hbR8_dm.js
MediumDynamic Requirepty-host.cjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowEval
LowWeak Cryptobin/runcastle.js
Low
Affected versions and remediation
This report applies to runcastle@1.4.6.
See all versions of runcastle for other recorded verdicts.
- Review the evidence and your use of runcastle@1.4.6 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.