registry / @lotics/cli / 0.318.32
@lotics/cli@0.318.32
Lotics SDK and CLI for AI agents
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe reported shell command is only displayed as update guidance, and the telemetry path is explicitly opt-in and targets the configured Lotics API. Credential use is consistent with requests to the package’s service; the inspected source does not substantiate the scanner’s exfiltration claims.
Static reason
One or more suspicious static signals were detected.
Trigger
CLI use; telemetry requires LOTICS_TELEMETRY=1.
Impact
No evidence found of credential redirection, host fingerprint exfiltration, or automatic execution of the printed shell command.
Mechanism
Service requests send credentials to the Lotics API. Optional telemetry posts CLI events to the configured API. The update check prints an install command without running it.
AI rationale
The reported shell command is only displayed as update guidance, and the telemetry path is explicitly opt-in and targets the configured Lotics API. Credential use is consistent with requests to the package’s service; the inspected source does not substantiate the scanner’s exfiltration claims.
Evidence
~/.lotics/telemetry-<api-url-hash>.ndjson~/.lotics/session.json
Network endpoints3
api.lotics.airegistry.npmjs.orgLOTICS_API_URL (user-configured)
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a CLI entry and a library export; its only lifecycle script is prepublishOnly, which runs the build.
- Telemetry is disabled unless LOTICS_TELEMETRY is set to "1".
- Enabled telemetry posts CLI events to the configured Lotics API; the default host is api.lotics.ai.
- The CLI sends API keys as bearer credentials in service requests.
- The flagged curl command is printed as an update instruction, not executed.
Evidence against
- Telemetry may include captured error text and argument shape when explicitly enabled.
- The CLI performs network requests for its service features and checks the npm registry for updates.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
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
1827// docs/cli_reference.md
L1828: 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...
L1829:
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.32.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.32 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.