registry / @lotics/cli / 0.318.13
@lotics/cli@0.318.13
Lotics SDK and CLI for AI agents
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe manifest has no consumer install hook, and the CLI's telemetry requires an explicit environment opt-in. Its authenticated telemetry request targets the same configured API service as ordinary CLI requests; the inspected source establishes no concrete attack behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
A CLI invocation enables telemetry by setting LOTICS_TELEMETRY=1; authenticated commands may flush queued events.
Impact
The source shows diagnostic reporting to the configured service and no confirmed unrelated credential recipient or other attack effect.
Mechanism
The CLI queues command metadata and, for failures, captured error text, then posts event batches to the configured API URL using the API key already used for that service.
AI rationale
The manifest has no consumer install hook, and the CLI's telemetry requires an explicit environment opt-in. Its authenticated telemetry request targets the same configured API service as ordinary CLI requests; the inspected source establishes no concrete attack behavior.
Evidence
package.jsondist/src/cli.js
Network endpoints1
api.lotics.ai
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json declares prepublishOnly as a build step; it declares no preinstall, install, or postinstall hook.
- Telemetry exits unless explicitly enabled, and the CLI records argument hashes and shapes rather than raw argument values.
- Telemetry sends event batches to the configured API URL; the client uses the same API URL and key for normal requests.
- The sign-in flow saves the API key and its host after a person confirms sign-in.
Evidence against
- When telemetry is enabled, event batches are sent with a bearer API key to the configured API endpoint.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
WildcardDependency
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.13.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.13 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.