Security

How Shark Scanner protects players, staff and evidence.

Security is part of the design, not a feature added later. This page explains what we do and — just as important — what we do not claim.

Updated 2026-11-19

Consent first

Nothing is read before the player approves a versioned consent text that lists what is checked and what is never accessed. The scanner sends back the hash of the exact text the player approved; it is stored in the audit log and the sealed report.

The scanner

A single executable that installs nothing: no service, driver, scheduled task or startup entry. Temporary files live in a private folder that is deleted on exit.

  • Single-use session codes (32⁸ ≈ 10¹² combinations) with rate limiting
  • TLS 1.2+ with certificate public-key pinning — proxies and traffic inspection are refused
  • 15-minute session token and a per-session HMAC key; uploads are signed and single-use
  • Debuggers or unsigned modules injected into the scanner are reported (SCANNER_TAMPERING)
  • The server only accepts official build hashes

Sealed reports

When a scan is uploaded the report is scored, written in canonical JSON, hashed with SHA-256 and signed with Ed25519. Public keys are published at /.well-known/poseidon-keys.json so anyone can verify a report — the public verification page never reveals contents. Staff review is stored next to the seal and never changes it.

Accounts and data isolation

Passwords use argon2id; two-factor authentication (TOTP) is available to everyone and mandatory for platform staff. Every database query runs under row-level security scoped to one account or team, so a missing filter fails closed. The audit log is append-only at the database level.

Honest limits

No tool offers 100% detection, and we do not claim it. A kernel-level cheat can make a running system lie. That is why Shark Scanner relies mainly on history — what ran, what was deleted and what was cleaned up — and why every finding shows its source, so your staff can judge it.

Reporting a vulnerability

Please report security issues to [email protected]. We do not take legal action against good-faith research.

Security · Shark Scanner