registry / @lotics/cli / 0.318.41
@lotics/cli@0.318.41
Lotics SDK and CLI for AI agents
AI Security Review
scanned 14h ago · by lpm-firewall-aiThe reported credential flow targets the Lotics API configured for the client, and telemetry is gated behind an explicit opt-in with disclosed fields. The shell command is printed as an update instruction and targets the official Lotics installer host; no malicious behavior was found.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Normal CLI or SDK use; telemetry collection requires LOTICS_TELEMETRY=1.
Impact
No unauthorized credential forwarding, unrelated collection, or harmful automatic action was found.
Mechanism
The SDK sends its configured key to its configured API URL. Opt-in telemetry posts CLI events to that same API URL. The update notice queries the npm registry, and the installer command points to Lotics’ official host.
AI rationale
The reported credential flow targets the Lotics API configured for the client, and telemetry is gated behind an explicit opt-in with disclosed fields. The shell command is printed as an update instruction and targets the official Lotics installer host; no malicious behavior was found.
Evidence
~/.lotics/config.json~/.lotics/session.json~/.lotics/telemetry-<host>.ndjson
Network endpoints5
api.lotics.aiLOTICS_API_URL (user-configured)registry.npmjs.org/@lotics/cli/latestlotics.ai/install.shlotics.ai/install.ps1
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exposes a CLI and an SDK client entry point.
- The only lifecycle script is prepublishOnly, which runs the build.
- The SDK sends its API key in an Authorization header; the CLI uses https://api.lotics.ai by default or the user-configured LOTICS_API_URL.
- Telemetry is disabled unless LOTICS_TELEMETRY=1; its disclosed records contain command outcomes and failure messages, while tool arguments contribute a hash and shape.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
WildcardDependency
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.41.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.41 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.