registry / @lotics/cli / 0.316.11
@lotics/cli@0.316.11
Lotics SDK and CLI for AI agents
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe inspected entrypoints show no install-time execution or credential redirection. The suspicious signals are consistent with opt-in diagnostics and authenticated requests to the configured Lotics API.
Static reason
One or more suspicious static signals were detected.
Trigger
Telemetry collection activates only when LOTICS_TELEMETRY is set to 1.
Impact
No attack impact was established; the inspected behavior is opt-in product diagnostics.
Mechanism
Enabled telemetry sends CLI metadata and may include error text to the configured API base URL.
AI rationale
The inspected entrypoints show no install-time execution or credential redirection. The suspicious signals are consistent with opt-in diagnostics and authenticated requests to the configured Lotics API.
Network endpoints1
api.lotics.ai
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 points to the CLI and client entrypoints; its listed lifecycle hook is prepublishOnly, which runs the build.
- CLI telemetry requires LOTICS_TELEMETRY=1, and the startup telemetry handler returns without registering when telemetry is disabled.
- When enabled, telemetry records CLI metadata and represents tool arguments with a hash and shape; failure events may also include error text.
- Telemetry posts to the configured API base URL, which defaults to https://api.lotics.ai.
- The client sends its bearer credential with requests to its configured base URL.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
WildcardDependency
Source & flagged code
7 flaggeddist/src/cli.jsView file
1745// src/cli_dispatch.ts
L1746: import { spawn as spawn2 } from "node:child_process";
L1747:
High
1778// docs/cli_reference.md
L1779: 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...
L1780:
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
7 High4 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
HighRemote Agent Bridgedist/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
LowScripts Present
LowEval
LowFilesystem
Affected versions and remediation
This report applies to @lotics/cli@0.316.11.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.316.11 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.