@lotics/cli@0.318.26
Lotics SDK and CLI for AI agents
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package does not show a malicious credential redirect or install-time action, and telemetry is opt-in. However, enabled telemetry sends failure text and argument-derived hashes and shapes despite the embedded disclosure that it sends no arguments, making this an undisclosed telemetry risk.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user sets LOTICS_TELEMETRY=1 and runs commands; failed commands add stderr text to events, while tool calls add argument hashes and shapes.
Impact
Failure messages may contain user-specific details, and argument hashes or shapes are undisclosed argument-derived telemetry. This is a privacy concern, but the collection is opt-in and targets the configured Lotics API.
Mechanism
The CLI captures stderr, spools event data locally, and posts batches to the configured API URL using the API key as authorization.
AI rationale
The package does not show a malicious credential redirect or install-time action, and telemetry is opt-in. However, enabled telemetry sends failure text and argument-derived hashes and shapes despite the embedded disclosure that it sends no arguments, making this an undisclosed telemetry risk.
Evidence
dist/src/cli.js~/.lotics/telemetry-<API URL hash>.ndjson~/.lotics/session.json
Network endpoints1
api.lotics.ai/v1/cli/telemetry (default; API URL is configurable via LOTICS_API_URL)
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Telemetry runs only when LOTICS_TELEMETRY=1 is set.
- When enabled, the CLI captures stderr and includes failure text in telemetry events.
- Events also contain a hash and shape derived from tool arguments, despite the embedded documentation saying telemetry sends no arguments.
- Telemetry batches are posted to the configured Lotics API URL with the API key as a bearer token.
Evidence against
- The manifest has no install, preinstall, or postinstall hook.
- Telemetry requires explicit opt-in, and the default endpoint is the package’s own Lotics API service.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
WildcardDependency
Source & flagged code
7 flaggeddist/src/cli.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @lotics/cli@0.318.25
matchedIdentity = npm:QGxvdGljcy9jbGk:0.318.25
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.26.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.26 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.