runlot@0.1.0-rc.152
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected MCP setup path prints instructions instead of mutating agent configuration. Credential lookup and browser login are scoped to the selected API origin, with no confirmed unrelated recipient or attack behavior.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs the CLI or explicitly starts its MCP server.
Impact
The inspected behavior supports ordinary CLI and MCP use, with no confirmed attack effect.
Mechanism
The MCP server uses the saved token for requests to the configured API; its install subcommand prints setup text for a selected client.
AI rationale
The manifest has no install lifecycle hook, and the inspected MCP setup path prints instructions instead of mutating agent configuration. Credential lookup and browser login are scoped to the selected API origin, with no confirmed unrelated recipient or attack behavior.
Evidence
package.jsondist/index.js
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 points the CLI to dist/index.js and lists build, test, and typecheck scripts without install lifecycle hooks.
- The indicated agent-integration code describes client configuration locations; the explicit mcp install command prints setup instructions rather than writing configuration files.
- Saved credentials are selected by API origin; RUNLOT_TOKEN is used only when explicitly supplied in the environment.
- Browser login uses the selected API origin for its handoff and login URL.
- MCP requests use the session token for requests to the configured API URL.
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.152.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.152 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.