registry / @lotics/cli / 0.318.12
@lotics/cli@0.318.12
Lotics SDK and CLI for AI agents
AI Security Review
scanned 8d ago · by lpm-firewall-aiSource inspection found no install-time execution hook or concrete attack behavior. The scanner's telemetry and subprocess signals resolve to opt-in Lotics telemetry and user-invoked CLI operations.
Static reason
One or more suspicious static signals were detected.
Trigger
Telemetry requires LOTICS_TELEMETRY=1; app build and upgrade subprocesses run when the user invokes those commands.
Impact
No confirmed credential theft, host fingerprinting, or unsolicited command-output transfer was established.
Mechanism
Telemetry spools command metadata and failed-command error text, then posts it to the configured API URL with the account key. Build subprocess output is used to report the result of an invoked build.
AI rationale
Source inspection found no install-time execution hook or concrete attack behavior. The scanner's telemetry and subprocess signals resolve to opt-in Lotics telemetry and user-invoked CLI operations.
Network endpoints1
api.lotics.ai/v1/cli/telemetry
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json has no install or import lifecycle hook; prepublishOnly runs the build.
- Telemetry is disabled unless LOTICS_TELEMETRY is set to 1.
- Telemetry records command metadata and includes the captured error message only for failed commands; the event requires an enabled session.
- Telemetry posts events to the configured Lotics API URL, which defaults to api.lotics.ai, using the account API key.
- The npm build helper captures output only for machine-readable runs and reports failures from the explicitly invoked app build path.
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.318.12.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.12 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.