registry / @lotics/cli / 0.318.1
@lotics/cli@0.318.1
Lotics SDK and CLI for AI agents
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe flagged network and process-execution indicators resolve to opt-in CLI telemetry and explicit build support. The inspected source does not establish credential harvesting, unrelated command-output export, or another concrete attack.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Telemetry requires LOTICS_TELEMETRY=1; flushing occurs during an authenticated CLI invocation after enough events have accumulated.
Impact
No concrete malicious effect was established from the inspected source.
Mechanism
The CLI records command metadata, an error summary, and argument shape, then posts queued events to the configured API URL.
AI rationale
The flagged network and process-execution indicators resolve to opt-in CLI telemetry and explicit build support. The inspected source does not establish credential harvesting, unrelated command-output export, or another concrete attack.
Evidence
package.jsondist/src/cli.js
Network endpoints1
api.lotics.ai
Decision evidence
public snapshotAI called this Clean at 97.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes the CLI and SDK entrypoints; its prepublish hook runs the build script.
- The CLI collects telemetry only when LOTICS_TELEMETRY is set to 1.
- Telemetry argument data is reduced to a hash and a shape describing value types.
- Telemetry flushing is also opt-in and waits until at least five events are queued.
- Telemetry is posted to the resolved API URL with that context's API key; the default API host is api.lotics.ai.
- The CLI's npm spawning supports explicit build operations, consistent with its build and install workflow.
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.316.26
matchedIdentity = npm:QGxvdGljcy9jbGk:0.316.26
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.1.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.318.1 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.