runlot@0.1.0-rc.128
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 28d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the flagged agent setup is an explicit CLI command that prints instructions. The inspected credential helper associates saved credentials with the requested API origin; no concrete attack behavior was established.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The CLI runs; agent setup instructions are printed only when the user invokes `runlot mcp install`.
Impact
No confirmed credential theft or unconsented agent configuration change was established.
Mechanism
The inspected setup path prints client-specific instructions, while saved credentials are selected for the requested API origin.
AI rationale
The manifest has no install lifecycle hook, and the flagged agent setup is an explicit CLI command that prints instructions. The inspected credential helper associates saved credentials with the requested API origin; no concrete attack behavior was established.
Network endpoints1
dash.runlot.io
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes dist/index.js as the CLI entrypoint and declares no install lifecycle hook.
- The flagged agent configuration path is selected by client; the CLI prints setup instructions only for the explicit `mcp install` subcommand.
- The default API endpoint belongs to runlot, and saved credentials are selected by API origin.
- The credential helper uses RUNLOT_TOKEN when supplied and otherwise selects saved credentials for the requested API origin.
Evidence against
- The inspected source does not show npm installation modifying agent configuration or forwarding saved credentials to an unrelated endpoint.
- Scanner flags for evaluation and remote response execution were not substantiated by the inspected relevant source.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStrings
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.128.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.128 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.