registry / @lotics/cli / 0.316.19
@lotics/cli@0.316.19
Lotics SDK and CLI for AI agents
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe package exposes a CLI and SDK, with no install-time hook shown in its manifest. The flagged credential and telemetry paths use the configured Lotics API, and passive telemetry is disabled unless explicitly enabled; no concrete attack behavior was found.
Static reason
One or more suspicious static signals were detected.
Trigger
A user invokes the CLI; passive telemetry additionally requires LOTICS_TELEMETRY to be enabled.
Impact
No confirmed attack impact; authenticated requests perform the user's Lotics CLI or SDK operations.
Mechanism
The CLI routes credentials and telemetry to the configured API URL, which defaults to Lotics. The inspected code showed no unrelated recipient or unconsented installation behavior.
AI rationale
The package exposes a CLI and SDK, with no install-time hook shown in its manifest. The flagged credential and telemetry paths use the configured Lotics API, and passive telemetry is disabled unless explicitly enabled; no concrete attack behavior was found.
Evidence
package.jsondist/src/cli.jsdist/src/client.js
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 exposes the CLI and SDK entry points; its prepublishOnly script runs the build.
- The CLI exits before installing telemetry handlers unless LOTICS_TELEMETRY is enabled.
- When enabled, telemetry records the command and flags, and uses captured stderr on failed commands.
- Credentialed requests use the API URL selected from the supplied key or saved profile; telemetry is sent to that same API URL.
- The SDK client builds requests from its configured API URL and API key.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
WildcardDependency
Source & flagged code
7 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
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.19.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.316.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.