registry / @lotics/cli / 0.316.22
@lotics/cli@0.316.22
Lotics SDK and CLI for AI agents
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe package manifest points to the inspected CLI and client entrypoints, and the flagged runtime telemetry is explicitly opt-in. Its default recipient is the Lotics API, and inspection did not establish credential theft, host fingerprinting, or command-output exfiltration as an attack.
Static reason
One or more suspicious static signals were detected.
Trigger
Telemetry collection and sending occur only when LOTICS_TELEMETRY is set to 1.
Impact
No malicious behavior was established; telemetry may disclose failure messages when explicitly enabled.
Mechanism
The CLI records command and session metadata, plus error text for failed commands, then posts events to the configured API endpoint.
AI rationale
The package manifest points to the inspected CLI and client entrypoints, and the flagged runtime telemetry is explicitly opt-in. Its default recipient is the Lotics API, and inspection did not establish credential theft, host fingerprinting, or command-output exfiltration as an attack.
Evidence
package.jsondist/src/cli.js
Network endpoints1
api.lotics.ai
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes dist/src/cli.js as the command entrypoint and dist/src/client.js as the library entrypoint.
- CLI telemetry requires LOTICS_TELEMETRY=1; it is not enabled by default.
- Telemetry records command/session metadata and includes error text only for failed commands.
- Telemetry sends events to the API URL used by the CLI, whose default is api.lotics.ai.
Evidence against
- When telemetry is enabled, the CLI captures stderr and may send failure messages along with telemetry events.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
WildcardDependency
Source & flagged code
6 flaggeddist/src/cli.jsView file
1746// src/cli_dispatch.ts
L1747: import { spawn as spawn2 } from "node:child_process";
L1748:
High
1779// docs/cli_reference.md
L1780: 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...
L1781:
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.316.22.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.316.22 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.