registry / @lotics/cli / 0.316.20
@lotics/cli@0.316.20
Lotics SDK and CLI for AI agents
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe manifest has no install-time hook, and the inspected CLI telemetry is opt-in and sent to the configured Lotics API. The scanner’s credential-redirection and command-output-exfiltration claims are unsupported by these source paths.
Static reason
One or more suspicious static signals were detected.
Trigger
Telemetry requires LOTICS_TELEMETRY=1; authenticated commands may flush queued events.
Impact
No confirmed attack surface was established; telemetry is opt-in and follows the configured Lotics API destination.
Mechanism
The CLI posts event data to the selected API URL. The inspected source does not show a package-selected unrelated recipient or a credential redirect.
AI rationale
The manifest has no install-time hook, and the inspected CLI telemetry is opt-in and sent to the configured Lotics API. The scanner’s credential-redirection and command-output-exfiltration claims are unsupported by these source paths.
Evidence
package.jsondist/src/cli.js
Network endpoints1
api.lotics.ai
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes the CLI and declares only a prepublish build hook; it has no install-time hook.
- Background telemetry requires LOTICS_TELEMETRY=1, and the telemetry send uses the selected Lotics API URL.
- The CLI sends telemetry events to that API endpoint; inspected code does not establish an unrelated credential recipient or command-output exfiltration.
Evidence against
- The scanner’s credential redirect and command-output exfiltration claims are not supported by the inspected source paths.
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.20.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.316.20 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.