0x4m4/hexstrike-ai
Canonical URL: https://github.com/0x4m4/hexstrike-ai · Fetched from: https://raw.githubusercontent.com/0x4m4/hexstrike-ai/HEAD/README.md · Machine form: /v1/resource-scans/github-com-0x4m4-hexstrike-ai-0159e9e3e4 · Markdown
Latest receipt: 4 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: 362d1d09f5d454d8d77eb08d42f9306afe84c48bc46f99a93fd29796a5787fa1 · 31084 bytes · scanned 2026-10-27T12:22:05.204Z · scanner resource-scan-v1 · ledger entry 1570.
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: api.star-history.com, discord.gg, dl.google.com, github.com, img.shields.io, leak-check.net, overthetop.ae, star-history.com, www.0x4m4.com, www.hexstrike.com, www.linkedin.com, www.python.org, www.youtube.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: api.star-history.com; domain: discord.gg; domain: dl.google.com; domain: github.com; domain: img.shields.io; domain: leak-check.net; domain: overthetop.ae; domain: star-history.com; domain: www.0x4m4.com; domain: www.hexstrike.com; domain: www.linkedin.com; domain: www.python.org; domain: www.youtube.com
Credential and environment access — pass
No credential or environment access patterns were found in the scanned bytes.
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 — flag
The scanned bytes contain shell-out or download patterns: 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 command tools named in the bytes (curl, wget, powershell)
Permission declarations vs behavior — flag
The bytes show network behavior, and no permissions declaration was found in the scanned bytes to compare it against.
Evidence: behavior: network
Known-bad indicators — flag
The scanned bytes match these known-bad indicators from the scanner's published pattern list: token- or credential-taking vocabulary (stealer, grabber, exfiltrate). Each match is a reproducible pattern match on the bytes named by the hash; re-running the published check on the same bytes reaches the same finding.
Evidence: token- or credential-taking vocabulary (stealer, grabber, exfiltrate)
Provenance facts (weak signals) — pass
Provenance facts, labeled weak signals — they say where the bytes sit, not what the bytes do: source host: github.com; repository: 0x4m4/hexstrike-ai; bytes scanned: 31084; fetched from: https://raw.githubusercontent.com/0x4m4/hexstrike-ai/HEAD/README.md.
Evidence: source host: github.com; repository: 0x4m4/hexstrike-ai; bytes scanned: 31084; fetched from: https://raw.githubusercontent.com/0x4m4/hexstrike-ai/HEAD/README.md
History
Every receipt for this artifact so far names the same SHA-256: the bytes have not changed between scans.
- 2026-10-27 — 4 of 8 checks flagged · SHA-256 362d1d09f5d454d8… · 31084 bytes · scanner resource-scan-v1 · ledger entry 1570
