registry / @lotics/cli / 0.318.19
@lotics/cli@0.318.19
Lotics SDK and CLI for AI agents
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe manifest has no install-time hook, and the suspicious network and subprocess indicators resolve to opt-in telemetry and CLI operations. The telemetry destination follows the configured Lotics API, so the inspected source does not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
Telemetry collection activates only when LOTICS_TELEMETRY is set to 1.
Impact
No confirmed attack impact; this is opt-in, service-aligned diagnostics.
Mechanism
Enabled telemetry records command metadata and failure text, then batches events for the configured API.
AI rationale
The manifest has no install-time hook, and the suspicious network and subprocess indicators resolve to opt-in telemetry and CLI operations. The telemetry destination follows the configured Lotics API, so the inspected source does not establish malicious behavior.
Evidence
package.jsondist/src/cli.js
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines a prepublish-only build and no install-time lifecycle hook.
- The CLI enables telemetry only when LOTICS_TELEMETRY is set to 1; telemetry setup returns when it is disabled.
- Telemetry batches command metadata and includes stderr text only for failed commands. The authenticated CLI sends those events to its configured Lotics API.
Evidence against
- When telemetry is enabled, event batches are sent with the API key as an authorization credential.
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.19.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.19 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.