registry / @lotics/cli / 0.318.2
@lotics/cli@0.318.2
Lotics SDK and CLI for AI agents
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe manifest exposes the CLI and client, with `prepublishOnly` limited to a build rather than an install-time hook. The flagged telemetry path requires explicit opt-in and sends events to the configured Lotics API; inspected command execution inherits stdio, so the scanner labels do not establish command-output exfiltration.
Static reason
One or more suspicious static signals were detected.
Trigger
Telemetry requires LOTICS_TELEMETRY=1; command execution occurs through the CLI's selected command path.
Impact
No confirmed malicious impact was established from the inspected source.
Mechanism
Opt-in telemetry posts events to the configured API URL. The inspected command runner inherits stdio and does not capture command output for that request.
AI rationale
The manifest exposes the CLI and client, with `prepublishOnly` limited to a build rather than an install-time hook. The flagged telemetry path requires explicit opt-in and sends events to the configured Lotics API; inspected command execution inherits stdio, so the scanner labels do not establish command-output exfiltration.
Evidence
package.jsondist/src/cli.js
Network endpoints1
api.lotics.ai
Decision evidence
public snapshotAI called this Clean at 87.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes the CLI and client; its only lifecycle entry shown is prepublishOnly, which runs the build.
- The CLI telemetry code is disabled unless LOTICS_TELEMETRY is set to 1.
- When enabled, telemetry posts events to the configured Lotics API URL; the CLI command runner inherits process output rather than sending it through that request.
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.2.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.2 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.