registry / @lotics/cli / 0.318.22
@lotics/cli@0.318.22
Lotics SDK and CLI for AI agents
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe scanner flags resolve to documented, opt-in telemetry and an official Lotics installer invoked by the explicit upgrade command. The manifest has no install-time hook, and the inspected source did not show the reported automatic credential redirect or host-data exfiltration.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Normal CLI use; telemetry collection requires LOTICS_TELEMETRY=1, and the installer pipeline requires the user to run upgrade.
Impact
No unauthorized credential transfer, host fingerprinting, or command-output exfiltration was identified. Opted-in telemetry may send the documented failure message.
Mechanism
The CLI contacts its configured Lotics API and checks the npm registry for updates. The upgrade command runs an installer from lotics.ai. Opted-in telemetry stores command metadata and disclosed failure text for later sending to the same configured service.
AI rationale
The scanner flags resolve to documented, opt-in telemetry and an official Lotics installer invoked by the explicit upgrade command. The manifest has no install-time hook, and the inspected source did not show the reported automatic credential redirect or host-data exfiltration.
Evidence
~/.lotics/session.json~/.lotics/telemetry-<host>.ndjson~/.lotics/config.json./.lotics/config.json
Network endpoints4
api.lotics.airegistry.npmjs.org/@lotics/cli/latestlotics.ai/install.shlotics.ai/install.ps1
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a CLI and SDK; its only lifecycle script is prepublishOnly, which runs the build.
- Runtime telemetry is disabled unless LOTICS_TELEMETRY=1 is set.
- The README discloses that opted-in telemetry records command status and printed failure messages, while arguments contribute only a hash and shape; it says nothing is stored or sent when telemetry is unset.
- The shell pipeline downloads from lotics.ai and is reached only through the explicit upgrade command.
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.19
matchedIdentity = npm:QGxvdGljcy9jbGk:0.318.19
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
1824// docs/cli_reference.md
L1825: 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...
L1826:
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.22.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.22 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.