@1sat/cli
CLI for 1Sat Ordinals SDK
This report shows the evidence for @1sat/cli@0.0.131. 1 of 34 known versions is blocked or flagged. The newest version, 0.1.1, is allowed. See all versions.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe package wires in a wallet flow that can spend funds automatically after a remote storage error, with consent defaulting to approval. The payment is conditional and tied to the configured storage service, but it still meets the automatic-spending rule.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user-run CLI operation calls a billable wallet method, an active remote storage provider returns HTTP 507, and its account status reports a deficit.
Impact
The wallet may spend funds on a storage payment without the user explicitly approving that payment.
Mechanism
The wallet dependency checks the remote's payment status and, without a configured consent hook, treats payment as approved and creates a transaction for the calculated satoshi amount.
Attack narrative
The CLI constructs a wallet using the user's key. Its wallet dependency wraps billable methods so a remote storage HTTP 507 can trigger a status check and an automatic storage payment. With no consent hook, the code defaults to approval and creates a transaction for the calculated satoshi amount, spending the user's funds without a separate payment confirmation.
AI rationale
The package wires in a wallet flow that can spend funds automatically after a remote storage error, with consent defaulting to approval. The payment is conditional and tied to the configured storage service, but it still meets the automatic-spending rule.
Evidence
dist/cli.js.lpm-dependency-evidence-e76e39fc-1482-4da5-adfa-8310a2f8a5ba/2/npm-linux/dist/factory.js.lpm-dependency-evidence-e76e39fc-1482-4da5-adfa-8310a2f8a5ba/2/npm-linux/dist/storagePaymentAutoRetry.js
Network endpoints1
Configured active remote: /account/status
Decision evidence
public snapshotAI called this Malicious at 95.0% confidence as Malware with low false-positive risk.
Evidence for block
- The package is a CLI for the 1Sat Ordinals SDK and creates a wallet from the user's private key.
- Its wallet dependency installs automatic payment retry on billable wallet methods when a remote storage provider is active.
- When a billable operation gets an HTTP 507, the retry flow checks the active remote for payment information.
- If no consent hook is configured, the retry flow defaults to approval and builds a payment transaction.
- The transaction sends the calculated satoshi amount for storage capacity.
Evidence against
- The package declares no install, preinstall, or postinstall lifecycle scripts.
- The automatic payment is conditional on a remote storage provider returning 507 for a billable operation.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggeddist/cli.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @1sat/cli@0.0.125
matchedIdentity = npm:QDFzYXQvY2xp:0.0.125
similarity = 0.848
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/cli.jsView on unpkg297// src/monitor-once.ts
L298: import { spawn } from "node:child_process";
L299: import { appendFileSync, closeSync, openSync } from "node:fs";
High
117const raw = readFileSync(CONFIG_FILE, "utf8");
L118: const parsed = JSON.parse(raw);
L119: return { ...DEFAULT_CONFIG, ...parsed };
...
L187: var init_config = __esm(() => {
L188: CONFIG_DIR = join(homedir(), ".1sat", "cli");
L189: CONFIG_FILE = join(CONFIG_DIR, "config.json");
...
L198: import { join as join2 } from "node:path";
L199: import { PrivateKey } from "@bsv/sdk";
L200: import { isCancel, password as promptPassword } from "@clack/prompts";
...
L205: function hasKey() {
L206: if (process.env.PRIVATE_KEY_WIF)
L207: return true;
High
Findings
1 Critical5 High2 Medium4 Low
CriticalPrevious Version Dangerous Deltadist/cli.js
HighChild Processdist/cli.js
HighCommand Output Exfiltrationdist/cli.js
HighAi Review Evidencepackage.json
HighAi Review Evidencedist/cli.js
HighSuspicious Dependency Evidence.lpm-dependency-evidence-e76e39fc-1482-4da5-adfa-8310a2f8a5ba/2/npm-linux/dist/factory.js
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @1sat/cli@0.0.131.
The versions list below shows the verdict for each recorded version.
- Avoid installing @1sat/cli@0.0.131. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.