Resource-scan receipts

witness-in-a-box.mjs

Canonical URL: https://www.rightshold.com/cli/witness-in-a-box.mjs · Fetched from: https://www.rightshold.com/cli/witness-in-a-box.mjs · Machine form: /v1/resource-scans/rightshold-com-cli-witness-in-a-box-mjs-a4c8bc4024 · Markdown

Latest receipt: 6 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: a9c00774f5d58cdae4c2b852d73599f7bb87e3e530fb98660a1e47ad67273278 · 31007 bytes · scanned 2026-10-28T19:35:41.291Z · scanner resource-scan-v1 · ledger entry 2468.

Analysis is static only: the bytes were read as text and were never executed, installed or run. Nothing was fetched from behind a login.

Checks (latest receipt)

• Outbound network references — flag

  The scanned bytes reference outbound network activity to these domains: ethereum-rpc.publicnode.com, ethereum-sepolia-rpc.publicnode.com, mainnet.base.org, sepolia.base.org, www.rightshold.com. Any resource that reaches the network can send data out as well as bring data in; the findings name what the bytes reference, and the reader decides whether that fits the resource's stated purpose.

  Evidence: domain: ethereum-rpc.publicnode.com; domain: ethereum-sepolia-rpc.publicnode.com; domain: mainnet.base.org; domain: sepolia.base.org; domain: www.rightshold.com; fetch / XMLHttpRequest / WebSocket calls

• Credential and environment access — flag

  The scanned bytes contain credential or environment access patterns: environment variable reads (process.env / os.environ / getenv); credential file paths (.env, .ssh, credential stores). The receipt names the pattern kinds only; no credential value is reproduced here.

  Evidence: environment variable reads (process.env / os.environ / getenv); credential file paths (.env, .ssh, credential stores)

• Install and postinstall hooks — pass

  No install or postinstall hooks were found in the scanned bytes.

• Obfuscation and encoded payloads — flag

  The scanned bytes carry obfuscation or encoding signs: 3 encoded-payload decoder calls (atob, base64 decode, fromCharCode). Encoded content cannot be read from the bytes alone, so what it does cannot be checked from the bytes alone either.

  Evidence: 3 encoded-payload decoder calls (atob, base64 decode, fromCharCode)

• Shell-outs and download-and-execute — flag

  The scanned bytes contain shell-out or download patterns: child process execution (child_process, exec, spawn). Code that runs shell commands acts with the full permissions of whoever runs it.

  Evidence: child process execution (child_process, exec, spawn)

• Permission declarations vs behavior — flag

  The bytes show network, credentials, filesystem behavior, and no permissions declaration was found in the scanned bytes to compare it against.

  Evidence: behavior: network; behavior: credentials; behavior: filesystem

• Known-bad indicators — pass

  None of the scanner's published known-bad indicator patterns matched the scanned bytes.

• Provenance facts (weak signals) — flag

  Only partial provenance facts could be read from the URL — a weak signal, recorded as such: source host: www.rightshold.com; bytes scanned: 31007.

  Evidence: source host: www.rightshold.com; bytes scanned: 31007

History

Every receipt for this artifact so far names the same SHA-256: the bytes have not changed between scans.

• 2026-10-28 — 6 of 8 checks flagged · SHA-256 a9c00774f5d58cda… · 31007 bytes · scanner resource-scan-v1 · ledger entry 2468