registry / @lotics/cli / 0.315.9
@lotics/cli@0.315.9
Lotics SDK and CLI for AI agents
AI Security Review
scanned 22d ago · by lpm-firewall-aiThe scanner’s lifecycle and agent-configuration signals do not match the inspected source: the only lifecycle hook is prepublishOnly, and the flagged agent location catalogs documentation. Telemetry is opt-in and uses the configured API endpoint, which defaults to the package’s Lotics service; no concrete attack behavior was found.
Static reason
One or more suspicious static signals were detected.
Trigger
A user invokes a CLI command; telemetry requires LOTICS_TELEMETRY=1.
Impact
No malicious effect was established from the inspected source.
Mechanism
The CLI sends authenticated API requests to its configured service and, when opted in, posts telemetry events there.
AI rationale
The scanner’s lifecycle and agent-configuration signals do not match the inspected source: the only lifecycle hook is prepublishOnly, and the flagged agent location catalogs documentation. Telemetry is opt-in and uses the configured API endpoint, which defaults to the package’s Lotics service; no concrete attack behavior was found.
Evidence
package.jsondist/src/cli.js
Network endpoints1
api.lotics.ai
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a CLI and SDK; its only lifecycle hook is prepublishOnly, which runs the build.
- The flagged AGENTS.md location is a CLI documentation catalog entry, not an agent configuration write.
- Telemetry is disabled unless LOTICS_TELEMETRY is set to 1.
- When enabled, telemetry posts events to the configured API base using its API key; the default host is api.lotics.ai.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
WildcardDependency
Source & flagged code
7 flaggeddist/src/cli.jsView file
46869// src/cli_dispatch.ts
L46870: import { spawn as spawn2 } from "node:child_process";
L46871:
High
Child Process
Package source references child process execution.
dist/src/cli.jsView on unpkg · L4686946890// docs/cli_reference.md
L46891: 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...
L46892:
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
7 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
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
LowEval
LowFilesystem
Affected versions and remediation
This report applies to @lotics/cli@0.315.9.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.315.9 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.