registry / @lotics/cli / 0.318.42
@lotics/cli@0.318.42
Lotics SDK and CLI for AI agents
AI Security Review
scanned 13h ago · by lpm-firewall-aiThe flagged network and process behaviors fit the CLI’s documented service and build functions. Telemetry is disabled by default, and the reviewed credential flow uses the configured Lotics API URL.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Telemetry requires LOTICS_TELEMETRY=1; API calls occur when a user runs CLI or client operations.
Impact
No source evidence showed credential forwarding to an unrelated host, concealed execution, or harmful automatic actions.
Mechanism
The CLI queues command metadata and posts it to the configured Lotics API. Client requests send credentials to the configured base URL.
AI rationale
The flagged network and process behaviors fit the CLI’s documented service and build functions. Telemetry is disabled by default, and the reviewed credential flow uses the configured Lotics API URL.
Evidence
~/.lotics/telemetry-<shard>.ndjson~/.lotics/session.json
Network endpoints2
api.lotics.airegistry.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 package exports a client module and provides a CLI binary; its only lifecycle script is prepublishOnly running the build.
- Telemetry is gated on LOTICS_TELEMETRY being exactly "1" and records command metadata rather than raw argument values.
- Telemetry is sent to the configured Lotics API URL; normal client requests use the configured base URL.
Evidence against
- The CLI sends authenticated telemetry when telemetry is enabled.
- The CLI can spawn shell commands for explicit build or upgrade operations.
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.42.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.42 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.