registry / @lotics/cli / 0.316.23
@lotics/cli@0.316.23
Lotics SDK and CLI for AI agents
AI Security Review
scanned 12d ago · by lpm-firewall-aiSource inspection found an ordinary CLI and SDK package with no install-time execution beyond a prepublish build. The flagged telemetry is opt-in and targets the configured Lotics API, so the scanner’s exfiltration signals do not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
Telemetry collection and upload require LOTICS_TELEMETRY=1; upload also occurs through authenticated CLI operations when a telemetry spool is ready.
Impact
No unrelated recipient or credential redirection was established; the observed behavior is opt-in service telemetry.
Mechanism
The CLI batches session and command metadata, and error text for failed commands, then posts it with the API key to the configured API endpoint, defaulting to api.lotics.ai.
AI rationale
Source inspection found an ordinary CLI and SDK package with no install-time execution beyond a prepublish build. The flagged telemetry is opt-in and targets the configured Lotics API, so the scanner’s exfiltration signals do not establish malicious behavior.
Evidence
package.jsondist/src/cli.js
Network endpoints1
api.lotics.ai
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI and SDK entrypoint; its only lifecycle hook is prepublishOnly running the build.
- Telemetry is disabled unless LOTICS_TELEMETRY is set to 1, and its startup path returns immediately otherwise.
- When enabled, telemetry records command and session details and sends them to the configured Lotics API endpoint with the API key; the default endpoint is api.lotics.ai.
- The inspected subprocess helpers serve user-invoked build and archive operations; no command-output-to-unrelated-network transfer was established.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
WildcardDependency
Source & flagged code
6 flaggeddist/src/cli.jsView file
1746// src/cli_dispatch.ts
L1747: import { spawn as spawn2 } from "node:child_process";
L1748:
High
1779// docs/cli_reference.md
L1780: 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...
L1781:
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.23.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.316.23 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.