registry / @lotics/cli / 0.318.6
@lotics/cli@0.318.6
Lotics SDK and CLI for AI agents
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe flagged source behavior is consistent with the CLI’s opt-in telemetry, version check, and user-invoked upgrade flow. The manifest’s prepublishOnly hook runs a build; inspected evidence does not establish an install-time attack.
Static reason
One or more suspicious static signals were detected.
Trigger
Telemetry requires LOTICS_TELEMETRY=1; the shell-based upgrade requires invoking the upgrade command.
Impact
No confirmed malicious effect or unrelated credential transfer was established.
Mechanism
Opt-in telemetry sends CLI events to the configured Lotics API. The startup version check reads the npm registry, and upgrade runs a CLI-selected command.
AI rationale
The flagged source behavior is consistent with the CLI’s opt-in telemetry, version check, and user-invoked upgrade flow. The manifest’s prepublishOnly hook runs a build; inspected evidence does not establish an install-time attack.
Network endpoints2
api.lotics.airegistry.npmjs.org/@lotics/cli/latest
Decision evidence
public snapshotAI called this Clean at 98.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes the CLI and client entrypoints; its prepublishOnly script runs a build.
- Telemetry is disabled unless LOTICS_TELEMETRY is set to 1, and its startup handler uses that same gate.
- When enabled, telemetry posts CLI events to the configured Lotics API using the API key; the default endpoint is api.lotics.ai.
- The startup version check reads the latest version from the npm registry.
- Shell-based upgrade runs only when the user invokes the upgrade command, using a command selected by the CLI.
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.6.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.6 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.