Upload handling
Size limits are enforced while streaming, content is identified from magic bytes, and files are written with random names outside any served directory. Files are never executed on the API host.
Short version: samples are stored only to analyse them, reports keep technical findings, and public reports do not reveal who submitted them.
Sample files are removed by the maintenance job after the configured window (48 hours by default). Reports keep their technical results so a hash can be re-checked later. Password reset tokens expire after 30 minutes and are stored only as a hash.
Anonymous scans produce unlisted reports: anyone who has the report ID can open the report, but it is not listed anywhere and its owner is shown as anonymous. Scans created while signed in are visible only to their owner and to administrators. Sample bytes are never downloadable through a report.
Size limits are enforced while streaming, content is identified from magic bytes, and files are written with random names outside any served directory. Files are never executed on the API host.
Loopback, private, link-local, reserved and cloud metadata addresses are blocked. Resolved IPs are pinned, redirects are re-validated, proxy environment variables are ignored, and responses are size-capped.
Provider API keys live in server-side environment variables and are never sent to the browser. The browser only receives public provider availability flags.
Parameterised database queries, strict response security headers, rate limits on scans and authentication, no cookie-based sessions (bearer tokens only, stored by the client), and escaped output in the report renderer.
When an operator configures a provider, hashes, URLs or file content may be sent to that provider for analysis, subject to that provider's own terms and privacy policy. Providers used by default are only called when configured: VirusTotal, MetaDefender Cloud, Google Safe Browsing, URLhaus, PhishTank and RDAP. Local analysis (static inspection, YARA, ClamAV) stays on your infrastructure.
This page describes the reference deployment. Operators may change limits, retention and provider configuration; the values above reflect the defaults in the repository.