registry / @lotics/cli / 0.316.25
@lotics/cli@0.316.25
Lotics SDK and CLI for AI agents
AI Security Review
scanned 11d ago · by lpm-firewall-aiSource inspection found no concrete attack behavior supporting the scanner's exfiltration claims. Credential use follows the configured Lotics API endpoint, and telemetry is explicitly gated.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user invokes the CLI; telemetry additionally requires LOTICS_TELEMETRY=1.
Impact
No confirmed malicious effect or unauthorized credential transfer was established.
Mechanism
The CLI sends API requests to its configured API base, defaulting to the Lotics API. The package manifest's publish hook runs the build.
AI rationale
Source inspection found no concrete attack behavior supporting the scanner's exfiltration claims. Credential use follows the configured Lotics API endpoint, and telemetry is explicitly gated.
Evidence
package.jsondist/src/cli.js
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 the CLI and client entrypoints; its only publish lifecycle hook runs the build.
- The CLI defaults to the Lotics API and uses LOTICS_API_URL as an explicit endpoint override for API requests.
- The API key is sent as a bearer credential in requests to the configured API base; setup checks the key against that same base before saving it.
- Telemetry is disabled unless LOTICS_TELEMETRY is set to 1.
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.24
matchedIdentity = npm:QGxvdGljcy9jbGk:0.316.24
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.316.25.
See all versions of @lotics/cli for other recorded verdicts.
- Review the evidence and your use of @lotics/cli@0.316.25 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.