registry / @lotics/cli / 0.318.30
@lotics/cli@0.318.30
Lotics SDK and CLI for AI agents
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe source does not substantiate the scanner’s exfiltration claims. Telemetry is opt-in and documented, while the shell execution is tied to the user-requested upgrade flow.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Telemetry requires LOTICS_TELEMETRY=1; upgrade execution requires the user to invoke the upgrade operation.
Impact
No evidence of automatic credential redirection, host fingerprint exfiltration, or unrelated command-output transmission.
Mechanism
Telemetry stores command diagnostics locally and sends batches to the configured Lotics API. Upgrade runs a fixed Lotics installer pipeline.
AI rationale
The source does not substantiate the scanner’s exfiltration claims. Telemetry is opt-in and documented, while the shell execution is tied to the user-requested upgrade flow.
Evidence
~/.lotics/session.json~/.lotics/telemetry-<host>.ndjson
Network endpoints3
api.lotics.airegistry.npmjs.org/@lotics/cli/latestLOTICS_API_URL (operator-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 dist/src/cli.js as the CLI and dist/src/client.js as the library entry point.
- Passive telemetry is disabled unless LOTICS_TELEMETRY=1 is set; the README discloses what it records and where it sends it.
- Telemetry records command and error details only when enabled; the documented spool is sent to the same Lotics instance.
- The shell pipeline is part of the explicit upgrade operation and uses a command selected from fixed installer URLs.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
WildcardDependency
Source & flagged code
7 flaggeddist/src/cli.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @lotics/cli@0.318.29
matchedIdentity = npm:QGxvdGljcy9jbGk:0.318.29
similarity = 0.500
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/src/cli.jsView on unpkg1791// 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
Findings
1 Critical6 High3 Medium6 Low
CriticalPrevious Version Dangerous Deltadist/src/cli.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
MediumWildcard Dependency
LowNon Install Lifecycle Scripts
LowScripts Present
LowEval
LowFilesystem
Low
Affected versions and remediation
This report applies to @lotics/cli@0.318.30.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.30 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.