Resource-scan receipts

treg.to

Canonical URL: https://treg.to · Fetched from: https://treg.to · Machine form: /v1/resource-scans/treg-to-ee07509144 · Markdown

Latest receipt: 4 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 7525b850bc0fb6f620eb82d43118422af523a78848c4d898ff08fb6c40930808 · 97671 bytes · scanned 2026-11-02T19:56:26.156Z · scanner resource-scan-v1 · ledger entry 5846.

The rightshold on https://treg.to — scanned 2026-11-02 · 4 of 8 checks flagged · receipt rsc_28b071c26d681bd07a1a8cae, verify at rightshold.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: cdn.jsdelivr.net, discord.gg, fonts.googleapis.com, fonts.gstatic.com, github.com, schema.org, treg.to, widget.intercom.io, www.google.com, www.gstatic.com, x.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: cdn.jsdelivr.net; domain: discord.gg; domain: fonts.googleapis.com; domain: fonts.gstatic.com; domain: github.com; domain: schema.org; domain: treg.to; domain: widget.intercom.io; domain: www.google.com; domain: www.gstatic.com; domain: x.com; fetch / XMLHttpRequest / WebSocket calls

• 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). 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)

• Install and postinstall hooks — pass

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

• Obfuscation and encoded payloads — pass

  No obfuscation or encoded-payload signs were found in the scanned bytes.

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

  No shell-out or download-and-execute patterns were found in the scanned bytes.

• 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: treg.to; bytes scanned: 97671.

  Evidence: source host: treg.to; bytes scanned: 97671

History

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

• 2026-11-02 — 4 of 8 checks flagged · SHA-256 7525b850bc0fb6f6… · 97671 bytes · scanner resource-scan-v1 · ledger entry 5846