registry / @lotics/cli / 0.318.38
@lotics/cli@0.318.38
Lotics SDK and CLI for AI agents
AI Security Review
scanned 21h ago · by lpm-firewall-aiThe manifest has no install-time hook, and the flagged runtime telemetry is explicitly opt-in and documented. The reviewed network and process-execution behavior fits the CLI’s Lotics service, update-check, and user-requested app-build functions.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Telemetry runs only when `LOTICS_TELEMETRY=1`; ordinary CLI commands use the configured Lotics API.
Impact
No unauthorized credential theft, unrelated data collection, or harmful automatic action was found.
Mechanism
When enabled, telemetry records command metadata and failure messages, plus argument hashes and shapes, then sends batches to the same configured Lotics API.
AI rationale
The manifest has no install-time hook, and the flagged runtime telemetry is explicitly opt-in and documented. The reviewed network and process-execution behavior fits the CLI’s Lotics service, update-check, and user-requested app-build functions.
Evidence
~/.lotics/config.json~/.lotics/telemetry-<host>.ndjson
Network endpoints2
api.lotics.airegistry.npmjs.org/@lotics/cli/latest
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The only lifecycle script is `prepublishOnly`, which runs the build; no install hook is declared.
- Runtime telemetry is gated on `LOTICS_TELEMETRY=1` and is off by default.
- The README describes telemetry fields and says arguments contribute a hash and shape, not their values or file contents.
- Telemetry posts to the configured Lotics API, which defaults to `https://api.lotics.ai`.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
WildcardDependency
Source & flagged code
8 flaggeddist/src/cli.jsView file
1850// src/cli_dispatch.ts
L1851: import { spawn as spawn2 } from "node:child_process";
L1852:
High
1886// docs/cli_reference.md
L1887: 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...
L1888:
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
2 Critical6 High4 Medium6 Low
CriticalHardcoded Runtime Data Exfiltrationdist/src/client.js
CriticalTrigger Reachable Dangerous Capabilitydist/src/client.js
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
MediumStructural Risk Force Deep Review
MediumWildcard Dependency
LowNon Install Lifecycle Scripts
Affected versions and remediation
This report applies to @lotics/cli@0.318.38.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.38 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.