registry / @lotics/cli / 0.316.26
@lotics/cli@0.316.26
Lotics SDK and CLI for AI agents
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the suspicious runtime indicators resolve to opt-in diagnostics and normal CLI product behavior. The reviewed source does not establish a concrete attack surface.
Static reason
One or more suspicious static signals were detected.
Trigger
Diagnostics require `LOTICS_TELEMETRY=1`; other CLI behavior follows user-invoked commands.
Impact
No unauthorized collection, persistence, destructive behavior, or execution was confirmed.
Mechanism
Diagnostics send CLI invocation details and failed-command stderr to the configured API endpoint. No hidden credential forwarding or host identity collector was identified.
AI rationale
The manifest has no install lifecycle hook, and the suspicious runtime indicators resolve to opt-in diagnostics and normal CLI product behavior. The reviewed source does not establish a concrete attack surface.
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 shows `prepublishOnly` runs the build; the CLI subprocess code is part of its app toolchain.
- Diagnostics are gated on `LOTICS_TELEMETRY=1` and are posted to the configured API endpoint.
- Diagnostic events contain CLI invocation details and may include captured stderr for failed commands.
- The CLI defaults to `api.lotics.ai`; the exported client uses the API URL supplied by its caller.
Evidence against
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.316.26.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.316.26 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.