registry / @lotics/cli / 0.318.39
@lotics/cli@0.318.39
Lotics SDK and CLI for AI agents
AI Security Review
scanned 20h ago · by lpm-firewall-aiThe flagged credential flow sends the key to the configured Lotics API, while telemetry is disclosed and opt-in. The manifest has no install hook, and the inspected shell-related behavior only prints an update command for the user to run.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Normal CLI API calls; telemetry is recorded and sent only when LOTICS_TELEMETRY=1 is set.
Impact
Expected service requests and diagnostics; no unrelated credential collection or hidden command execution was identified.
Mechanism
The client sends its API key to the configured API instance. Opt-in telemetry batches diagnostic events to that instance, and the CLI checks npm for version metadata.
AI rationale
The flagged credential flow sends the key to the configured Lotics API, while telemetry is disclosed and opt-in. The manifest has no install hook, and the inspected shell-related behavior only prints an update command for the user to run.
Evidence
~/.lotics/session.json~/.lotics/telemetry-<shard>.ndjson
Network endpoints3
api.lotics.ai${LOTICS_API_URL}/v1/cli/telemetryregistry.npmjs.org/@lotics/cli/latest
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a CLI and SDK client; its only lifecycle script is prepublishOnly, which runs the build.
- The client sends its configured API key as a bearer token with requests to its configured API instance.
- Telemetry is collected only when LOTICS_TELEMETRY=1 is set.
- The README discloses the telemetry fields, including command, exit code, duration, failure message, argument hash and shape; it says telemetry is off by default.
- Telemetry posts to the configured API instance's /v1/cli/telemetry endpoint; the default instance is api.lotics.ai.
Evidence against
- The CLI checks the npm registry for the latest package version and prints an update command; the inspected code does not execute that printed installer command.
- The flagged child-process usage is in CLI build and packaging paths, not an automatic install or import-time execution path.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetwork
Source & flagged code
8 flaggeddist/src/cli.jsView file
1850// src/cli_dispatch.ts
L1851: import { spawn as spawn2 } from "node:child_process";
L1852:
High
1886// docs/cli_reference.md
L1887: 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...
L1888:
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
2 Critical6 High4 Medium6 Low
CriticalHardcoded Runtime Data Exfiltrationdist/src/client.js
CriticalTrigger Reachable Dangerous Capabilitydist/src/client.js
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
MediumStructural Risk Force Deep Review
MediumWildcard Dependency
LowNon Install Lifecycle Scripts
Affected versions and remediation
This report applies to @lotics/cli@0.318.39.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.39 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.