runlot@0.1.0-rc.138
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe inspected manifest has no install lifecycle hook, and the reported agent configuration behavior is user-directed setup guidance. MCP credentials are associated with the selected API origin, so the scanner's exfiltration claim is not supported by these source facts.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user invokes the Runlot CLI or starts its MCP command.
Impact
No unrelated credential forwarding or unconsented agent configuration change was established.
Mechanism
The MCP command selects credentials by API origin and displays configuration instructions for the user.
AI rationale
The inspected manifest has no install lifecycle hook, and the reported agent configuration behavior is user-directed setup guidance. MCP credentials are associated with the selected API origin, so the scanner's exfiltration claim is not supported by these source facts.
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 a CLI and lists only build, test, and typecheck scripts; no install lifecycle hook is present.
- The reported Cursor configuration location is presented as a path for MCP configuration.
- MCP login credentials are selected for the API origin in use; the server uses that API URL and returns without starting when no token is available.
- The MCP setup text gives the user configuration instructions instead of writing agent configuration files.
Evidence against
- dist/index.js contains network, dynamic loading, and telemetry code, but the inspected credential path does not show forwarding a saved session token to an unrelated destination.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
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.138.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.138 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.