runlot@0.1.0-rc.110
runlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe inspected source does not substantiate the scanner's malicious behavior claims, including the indicated agent integration location and its caller. Network authentication, generated validation code, and local runtime execution are package-aligned operations without a concrete attack chain.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Explicit CLI commands activate these operations; no npm install lifecycle hook is defined.
Impact
No credential theft, remote payload execution, or unconsented agent control change was established.
Mechanism
Agent configuration paths are displayed without mutation, saved credentials are selected by API origin, and generated validators account for dynamic execution.
AI rationale
The inspected source does not substantiate the scanner's malicious behavior claims, including the indicated agent integration location and its caller. Network authentication, generated validation code, and local runtime execution are package-aligned operations without a concrete attack chain.
Network endpoints2
dash.runlot.ioo4512108816105473.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines a CLI without install lifecycle hooks or a runtime self-dependency.
- The indicated Cursor configuration location supplies an instruction string; the MCP install caller only prints instructions.
- Saved credentials are scoped to API origins; browser login verifies and saves the session for the selected API.
- Dynamic Function execution compiles generated schema validation code.
- Crash reporting scrubs exception text and command arguments and supports telemetry opt-out.
- Development secrets are passed to a local runtime child process selected from packaged files or an explicit override.
Evidence against
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 {
...
L978: * hostname (the original request went there), and the server derives the org
L979: * and project names from it. Doing `location.replace` with the `redirect` that
L980: * 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 {
...
L978: * hostname (the original request went there), and the server derives the org
L979: * and project names from it. Doing `location.replace` with the `redirect` that
L980: * 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.110.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.110 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.