runlot@0.1.0-rc.164
⚠ Under reviewrunlot CLI — deploy apps and manage PostgreSQL
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe source does not confirm an attack, but it invokes a bundled native runtime with secrets and that runtime could not be inspected. This leaves material behavior unresolved.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs the dev command on a platform where the bundled runtime is selected.
Impact
It is not possible to assess how the runtime handles those secrets or whether it performs network or other sensitive actions.
Mechanism
The CLI starts the native runtime with project paths and copies supplied secrets into its environment. Available offline analysis could not inspect the binary's behavior.
AI rationale
The source does not confirm an attack, but it invokes a bundled native runtime with secrets and that runtime could not be inspected. This leaves material behavior unresolved.
Evidence
package.jsondist/index.jsbin/linux-x64/runlot-dev-runtime.lpm-inspection-yW7xfL/0-a44915dadcc5.txt
Decision evidence
public snapshotAI called this Manual Review at 83.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest exposes the CLI through dist/index.js and includes bin/; its scripts list build, test, and typecheck, with no install lifecycle hook.
- The user-invoked dev command enters the development flow, which can select the bundled platform runtime.
- The CLI passes project configuration and secret values to that runtime process.
- Host analysis identifies the shipped Linux runtime as an ELF binary but could not analyze its behavior.
Evidence against
- No malicious behavior was confirmed in the inspected JavaScript. The generated-code site is part of schema validation; crash reporting filters diagnostics and offers an opt-out.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
11 flaggeddist/index.jsView file
6const __filename = __runlotFilePath(import.meta.url);
L7: const __dirname = __runlotDirname(__filename);
L8: var __create = Object.create;
...
L47: // ../../packages/api/src/index.ts
L48: function base64urlJson(v) {
L49: const bytes = new TextEncoder().encode(JSON.stringify(v));
...
L54: function gitQuery(ref, path) {
L55: const q = new URLSearchParams();
L56: if (ref !== "") q.set("ref", ref);
...
L126: async request(method, path, init) {
L127: const res = await fetch(new URL(path, this.opts.baseUrl), {
L128: ...init,
Critical
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
dist/index.jsView on unpkg · L64246});
L4247: readFromStdout(stdout);
L4248: afterClose(null);
...
L4256: let worker = new worker_threads2.Worker(__filename, {
L4257: workerData: { workerPort, defaultWD, esbuildVersion: "0.24.2" },
L4258: transferList: [workerPort],
L4259: // From node's documentation: https://nodejs.org/api/worker_threads.html
L4260: //
L4261: // Take care when launching worker threads from preload scripts (scripts loaded
L4262: // and run using the `-r` command line flag). Unless the `execArgv` option is
L4263: // explicitly set, new Worker threads automatically inherit the command line flags
Critical
Command Output Exfiltration
Source executes local commands and sends command output to an external endpoint.
dist/index.jsView on unpkg · L4246Findings
4 Critical5 High5 Medium5 Low
CriticalCredential Exfiltrationdist/index.js
CriticalCommand Output 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
HighTrigger Reachable Credential Exfiltrationdist/index.js
HighTrigger Reachable Command Output Exfiltrationdist/index.js
MediumDynamic Requiredist/index.js
MediumNetwork
MediumEnvironment Vars
Medium
Affected versions and remediation
This report applies to runlot@0.1.0-rc.164.
See all versions of runlot for other recorded verdicts.
- Review the evidence and your use of runlot@0.1.0-rc.164 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.