registry / @lotics/cli / 0.318.28
@lotics/cli@0.318.28
Lotics SDK and CLI for AI agents
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe scanner flags are explained by CLI functions: app toolchain subprocesses, an explicit shell-based upgrade command, and a latest-version check. Telemetry is disabled by default, documents the failure text it records, and sends it to the Lotics API or a user-configured API endpoint.
Static reason
One or more suspicious static signals were detected.
Trigger
No malicious trigger identified. Telemetry requires LOTICS_TELEMETRY=1; the shell-based upgrade requires the user to invoke lotics upgrade.
Impact
No malicious impact identified; the observed behavior matches the CLI's stated purpose and telemetry disclosure.
Mechanism
No attack mechanism identified. Telemetry records disclosed command metadata and failure text, then posts it to the Lotics API or the API URL configured by the user.
AI rationale
The scanner flags are explained by CLI functions: app toolchain subprocesses, an explicit shell-based upgrade command, and a latest-version check. Telemetry is disabled by default, documents the failure text it records, and sends it to the Lotics API or a user-configured API endpoint.
Evidence
~/.lotics/session.json~/.lotics/telemetry-<host>.ndjson
Network endpoints3
api.lotics.ai/v1/cli/telemetryregistry.npmjs.org/@lotics/cli/latestLOTICS_API_URL (user-configured API base URL)
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes dist/src/cli.js as the CLI and dist/src/client.js as the library entry; its only lifecycle hook is prepublishOnly, which runs the build.
- Telemetry is off by default and requires LOTICS_TELEMETRY=1; its documented fields include command, exit code, duration, and the printed message on failure.
- The docs state that telemetry records argument hashes and shapes, not argument values, file contents, or record data.
- Telemetry is posted to the Lotics API endpoint, or to the API URL explicitly configured by the user.
- The update check fetches only the CLI's latest version from the npm registry; the shell-based upgrade runs through the explicit upgrade command.
Evidence against
- The CLI captures up to 2,000 characters of stderr on failures, so the disclosed telemetry can include error text.
- The CLI uses child processes for app toolchain operations and the explicit upgrade command; these have package-related purposes.
Behavioral surface
ChildProcessCryptoEnvironmentVars
Source & flagged code
6 flaggeddist/src/cli.jsView file
1791// src/cli_dispatch.ts
L1792: import { spawn as spawn2 } from "node:child_process";
L1793:
High
1824// docs/cli_reference.md
L1825: var cli_reference_default = "# @lotics/cli \u2014 CLI Command Reference\n\nPer-command syntax, flags, contracts, and gotchas for the public `lotics` CLI. Start at [AGENTS.md](../AG...
L1826:
High
9// src/cli.ts
L10: import dns from "node:dns";
L11: import net from "node:net";
...
L111: import path from "node:path";
L112: function telemetryEnabled(env = process.env) {
L113: return env.LOTICS_TELEMETRY === "1";
...
L142: function sessionStorePath() {
L143: return path.join(os.homedir(), ".lotics", "session.json");
L144: }
...
L146: try {
L147: const parsed = JSON.parse(fs.readFileSync(file2, "utf-8"));
L148: if (typeof parsed !== "object" || parsed === null) return null;
High
Host Fingerprint Exfiltration
Source collects local host identity data and sends it to an external endpoint.
Findings
6 High3 Medium6 Low
HighChild Processdist/src/cli.js
HighShelldist/src/cli.js
HighHost Fingerprint Exfiltrationdist/src/cli.js
HighCredential Redirect Persistencedist/src/cli.js
HighCommand Output Exfiltrationdist/src/cli.js
HighTrigger Reachable Command Output Exfiltrationdist/src/cli.js
MediumNetwork
MediumEnvironment Vars
MediumWildcard Dependency
LowNon Install Lifecycle Scripts
LowScripts Present
LowEval
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @lotics/cli@0.318.28.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.28 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.