registry / @lotics/cli / 0.316.21
@lotics/cli@0.316.21
Lotics SDK and CLI for AI agents
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe manifest and inspected entrypoint support normal CLI and client functionality. Scanner signals for host collection, credential redirection, and command-output exfiltration were not substantiated by the inspected source; the observed telemetry is opt-in and Lotics-directed.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Telemetry requires LOTICS_TELEMETRY=1; app setup or build commands invoke the inspected npm processes.
Impact
No confirmed malicious effect or attack surface was established.
Mechanism
Telemetry sends events to the Lotics API, while the observed child processes check npm or run npm commands.
AI rationale
The manifest and inspected entrypoint support normal CLI and client functionality. Scanner signals for host collection, credential redirection, and command-output exfiltration were not substantiated by the inspected source; the observed telemetry is opt-in and Lotics-directed.
Evidence
package.jsondist/src/cli.js
Network endpoints1
api.lotics.ai
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes the CLI and client entrypoints; its only publish lifecycle hook runs a build.
- dist/src/cli.js enables telemetry only when LOTICS_TELEMETRY is set to "1" and posts events to the configured Lotics API.
- The inspected child-process calls run npm version checks or npm commands for app setup and builds.
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.20
matchedIdentity = npm:QGxvdGljcy9jbGk:0.316.20
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 unpkg1746// src/cli_dispatch.ts
L1747: import { spawn as spawn2 } from "node:child_process";
L1748:
High
1779// docs/cli_reference.md
L1780: 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...
L1781:
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.316.21.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.316.21 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.