runlot@0.1.0-rc.139
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe package exposes a CLI without install lifecycle hooks, and the flagged MCP configuration behavior is explicit setup guidance. Inspected credential routing and dynamic evaluation are consistent with ordinary package operation, so the scanner’s malicious label is not supported by source evidence.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The MCP configuration instructions are displayed only when a user invokes runlot mcp install; the server runs when the user starts runlot mcp.
Impact
No credential theft, remote code execution, or unconsented agent configuration change was established.
Mechanism
The MCP server uses Runlot’s API by default, and saved credentials are selected for a matching API origin. The inspected dynamic evaluation compiles generated schema validator code.
AI rationale
The package exposes a CLI without install lifecycle hooks, and the flagged MCP configuration behavior is explicit setup guidance. Inspected credential routing and dynamic evaluation are consistent with ordinary package operation, so the scanner’s malicious label is not supported by source evidence.
Network endpoints1
dash.runlot.io
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes dist/index.js as the runlot command and declares no install lifecycle hook.
- The MCP configuration path is returned by configPath; mcp install prints setup instructions only when explicitly invoked.
- The default API is https://dash.runlot.io, and stored credentials are selected by matching the API origin.
- The dynamic Function call builds a validator from generated schema code.
Evidence against
- Inspected source does not support the scanner’s claim that credentials are redirected to an unofficial gateway or that remote response code is executed.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
10 flaggeddist/index.jsView file
44function gitQuery(ref, path) {
L45: const q = new URLSearchParams();
L46: if (ref !== "") q.set("ref", ref);
...
L87: async request(method, path, init) {
L88: const res = await fetch(new URL(path, this.opts.baseUrl), {
L89: ...init,
...
L95: try {
L96: body = await res.json();
L97: } catch {
...
L1039: * hostname (the original request went there), and the server derives the org
L1040: * and project names from it. Doing `location.replace` with the `redirect` that
L1041: * comes back is the caller's job.
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L4444function gitQuery(ref, path) {
L45: const q = new URLSearchParams();
L46: if (ref !== "") q.set("ref", ref);
...
L87: async request(method, path, init) {
L88: const res = await fetch(new URL(path, this.opts.baseUrl), {
L89: ...init,
...
L95: try {
L96: body = await res.json();
L97: } catch {
...
L1039: * hostname (the original request went there), and the server derives the org
L1040: * and project names from it. Doing `location.replace` with the `redirect` that
L1041: * comes back is the caller's job.
Critical
Remote Response Code Execution
Source passes code obtained from a remote response into a dynamic execution sink.
dist/index.jsView on unpkg · L44Findings
3 Critical5 High5 Medium5 Low
CriticalCredential Exfiltrationdist/index.js
CriticalRemote Response Code Executiondist/index.js
CriticalTrigger Reachable Dangerous Capabilitydist/index.js
HighChild Processdist/index.js
HighEvaldist/index.js
HighCredential Redirect Persistencedist/index.js
HighCommand Output Exfiltrationdist/index.js
HighTrigger Reachable Credential Exfiltrationdist/index.js
MediumDynamic Requiredist/index.js
MediumNetwork
MediumEnvironment Vars
MediumShips Native Binarybin/linux-x64/runlot-dev-runtime
Medium
Affected versions and remediation
This report applies to runlot@0.1.0-rc.139.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.139 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.