runlot@0.1.0-rc.153
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe manifest has no install hook, and inspected login and MCP setup behavior is tied to the configured API and explicit user commands. Scanner labels do not establish malicious behavior; the inspected source does not support its credential-redirection or agent-configuration claims.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The user runs the CLI; MCP configuration text is produced only by an explicit install subcommand.
Impact
No confirmed credential theft, automatic agent-setting mutation, or other attack surface was established.
Mechanism
Login saves credentials for the selected API origin, and MCP setup prints a configuration snippet rather than modifying agent files.
AI rationale
The manifest has no install hook, and inspected login and MCP setup behavior is tied to the configured API and explicit user commands. Scanner labels do not establish malicious behavior; the inspected source does not support its credential-redirection or agent-configuration claims.
Evidence
package.jsondist/index.js
Network endpoints1
dash.runlot.io
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes dist/index.js as the CLI and declares no install lifecycle hook.
- The CLI defaults to Runlot’s API and stores credentials under an origin-specific key; login saves the session for the selected API.
- MCP setup prints configuration only when the user invokes the install subcommand; it does not write agent settings automatically.
- The API client sends requests to its configured base URL, consistent with the user-selected API destination.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
12 flaggeddist/index.jsView file
43// ../../packages/api/src/index.ts
L44: function base64urlJson(v) {
L45: const bytes = new TextEncoder().encode(JSON.stringify(v));
...
L50: function gitQuery(ref, path) {
L51: const q = new URLSearchParams();
L52: if (ref !== "") q.set("ref", ref);
...
L97: async request(method, path, init) {
L98: const res = await fetch(new URL(path, this.opts.baseUrl), {
L99: ...init,
...
L1108: * hostname (the original request went there), and the server derives the org
L1109: * and project names from it. Doing `location.replace` with the `redirect` that
L1110: * 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 · L4343// ../../packages/api/src/index.ts
L44: function base64urlJson(v) {
L45: const bytes = new TextEncoder().encode(JSON.stringify(v));
...
L50: function gitQuery(ref, path) {
L51: const q = new URLSearchParams();
L52: if (ref !== "") q.set("ref", ref);
...
L97: async request(method, path, init) {
L98: const res = await fetch(new URL(path, this.opts.baseUrl), {
L99: ...init,
...
L1108: * hostname (the original request went there), and the server derives the org
L1109: * and project names from it. Doing `location.replace` with the `redirect` that
L1110: * 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 · L43Findings
3 Critical5 High7 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
MediumSecret Patterndist/index.js
MediumDynamic Requiredist/index.js
MediumNetwork
MediumEnvironment Vars
MediumShips Native Binarybin/linux-x64/runlot-dev-runtime
Affected versions and remediation
This report applies to runlot@0.1.0-rc.153.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.153 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.