registry / @lotics/cli / 0.312.18
@lotics/cli@0.312.18
Lotics SDK and CLI for AI agents
AI Security Review
scanned 24d ago · by lpm-firewall-aiThe manifest's publish hook only builds the package, and the inspected CLI telemetry requires explicit opt-in and posts to its configured Lotics API. The scanner hints do not establish a concrete attack surface in the inspected source.
Static reason
One or more suspicious static signals were detected.
Trigger
Telemetry runs only when LOTICS_TELEMETRY is set to 1.
Impact
No malicious impact was established from the inspected source.
Mechanism
The CLI sends telemetry events to the configured API URL's CLI telemetry endpoint.
AI rationale
The manifest's publish hook only builds the package, and the inspected CLI telemetry requires explicit opt-in and posts to its configured Lotics API. The scanner hints do not establish a concrete attack surface in the inspected source.
Network endpoints1
api.lotics.ai
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI entry point; its only publish lifecycle hook builds the package.
- dist/src/cli.js identifies the CLI documentation index, not an agent configuration mutation.
- Telemetry collection requires LOTICS_TELEMETRY=1 and sends events to the configured Lotics API URL.
- The telemetry request posts to the CLI telemetry endpoint using the API key for that API instance.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
WildcardDependency
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.18.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.312.18 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.