Resource-scan receipts

www.rightshold.com

Canonical URL: https://www.rightshold.com · Fetched from: https://www.rightshold.com · Machine form: /v1/resource-scans/rightshold-com-8d9f42e606 · Markdown

Latest receipt: 6 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 71a512f51b5ff934fecd1b25afa9e96ff26559070c1c2fa1c4ec2892f7244266 · 167655 bytes · scanned 2026-11-08T15:37:13.689Z · scanner resource-scan-v1 · ledger entry 1296.

The a2ally on https://www.rightshold.com — scanned 2026-11-08 · 6 of 8 checks flagged · receipt rsc_4a4673c441dd543094534f99, verify at a2ally.com/verify.

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: 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: www.rightshold.com

• Credential and environment access — flag

  The scanned bytes contain credential or environment access patterns: secret-named variables (API_KEY, SECRET, TOKEN, PASSWORD and similar names); credential file paths (.env, .ssh, credential stores); authorization headers and bearer values. The receipt names the pattern kinds only; no credential value is reproduced here.

  Evidence: secret-named variables (API_KEY, SECRET, TOKEN, PASSWORD and similar names); credential file paths (.env, .ssh, credential stores); authorization headers and bearer values

• 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: eval or Function-constructor evaluation of text as code. Encoded content cannot be read from the bytes alone, so what it does cannot be checked from the bytes alone either.

  Evidence: eval or Function-constructor evaluation of text as code

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

  The scanned bytes contain shell-out or download patterns: shell invocation from Python (subprocess, os.system, Popen); shell command tools named in the bytes (curl, wget, powershell). Code that runs shell commands acts with the full permissions of whoever runs it.

  Evidence: shell invocation from Python (subprocess, os.system, Popen); shell command tools named in the bytes (curl, wget, powershell)

• Permission declarations vs behavior — flag

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

  Evidence: behavior: network; behavior: credentials

• 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: 167655.

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

History

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

• 2026-11-08 — 6 of 8 checks flagged · SHA-256 71a512f51b5ff934… · 167655 bytes · scanner resource-scan-v1 · ledger entry 1296
• 2026-11-08 — 6 of 8 checks flagged · SHA-256 71a512f51b5ff934… · 167655 bytes · scanner resource-scan-v1 · ledger entry 1295
• 2026-11-08 — 6 of 8 checks flagged · SHA-256 71a512f51b5ff934… · 167655 bytes · scanner resource-scan-v1 · ledger entry 1294