registry / @lotics/cli / 0.312.23
@lotics/cli@0.312.23
Lotics SDK and CLI for AI agents
AI Security Review
scanned 23d ago · by lpm-firewall-aiThe manifest has no install-time hook, and the required agent-configuration location is documentation metadata. The suspicious telemetry behavior is gated by an explicit opt-in and posts to the package’s Lotics API endpoint, so the inspected source does not establish an attack.
Static reason
One or more suspicious static signals were detected.
Trigger
Telemetry collection requires LOTICS_TELEMETRY=1; sending queued events also requires an authenticated CLI command.
Impact
The inspected behavior supports package telemetry and does not establish credential theft, unauthorized agent configuration changes, or another attack.
Mechanism
When enabled, the CLI records invocation metadata and may include captured error text, then posts events to the Lotics API telemetry endpoint.
AI rationale
The manifest has no install-time hook, and the required agent-configuration location is documentation metadata. The suspicious telemetry behavior is gated by an explicit opt-in and posts to the package’s Lotics API endpoint, so the inspected source does not establish an attack.
Evidence
package.jsondist/src/cli.js
Network endpoints1
api.lotics.ai/v1/cli/telemetry
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes the CLI and client; its only lifecycle hook is prepublishOnly, which runs a build.
- The required CLI location is embedded documentation metadata describing AGENTS.md and cli_reference.md, not agent configuration code.
- Telemetry is disabled unless LOTICS_TELEMETRY is set to 1.
- Opt-in telemetry records command, session, flags, duration, exit status, and error text; it is sent to the Lotics API telemetry route.
- The CLI initializes telemetry through its entrypoint and defaults the API host to api.lotics.ai.
Evidence against
- The scanner’s host-fingerprinting, credential-redirection, command-output exfiltration, and remote-agent-bridge labels are not established by the inspected source; the observed telemetry is opt-in and uses the Lotics API.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStrings
Source & flagged code
8 flaggeddist/src/cli.jsView file
46924// src/cli_dispatch.ts
L46925: import { spawn as spawn2 } from "node:child_process";
L46926:
High
Child Process
Package source references child process execution.
dist/src/cli.jsView on unpkg · L4692446945// docs/cli_reference.md
L46946: 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...
L46947:
High
661loggedProperties[propertyName] = true;
L662: _logger2["default"].log("error", 'Handlebars: Access has been denied to resolve the property "' + propertyName + '" because it is not an "own property" of its parent.\nYou can add ...
L663: }
...
L955: },
L956: data: function data(value, depth) {
L957: while (value && depth--) {
...
L2968:
L2969: // ../../node_modules/handlebars/node_modules/source-map/lib/base64.js
L2970: var require_base64 = __commonJS({
...
L5756: (function() {
L5757: var reservedWords = "break else new var case finally return void catch for switch while continue function this with default if throw delete in try do instanceof typeof abstract enu...
L5758: var compilerWords = JavaScriptCompiler.RESERVED_WORDS = {};
Findings
8 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
HighSandbox Evasion Gated Capabilitydist/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
Affected versions and remediation
This report applies to @lotics/cli@0.312.23.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.312.23 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.