Malicious Uploads Detection
Inspect files locally on the WAF agent before your application receives them. Bloom screening narrows candidate hashes; an exact SHA-256 lookup is required before a known-malware verdict.
- File forwarded
- File blocked
- Hash list
What it provides
- Multipart file inspection and optional whole-body scanning for raw upload endpoints.
- Exact verification after Bloom screening, plus custom SHA-256 allowlists and blocklists.
- Block or Log only policies for confirmed matches; a separate policy for incomplete scans.
- A default 10 MiB budget shared across request files and fields, with complete-file hashing only.
How to use it
- Obtain an abuse.ch Auth-Key and save it under Administration › Security Data › MalwareBazaar.
- Choose Check access & update hashes, then verify database source, count, and synchronization on each WAF agent.
- Enable Malicious Uploads Detection in the project WAF settings. Start with Log only and Forward and log, then validate before blocking.
- Order of the steps
Configuration and operation
The provider key is encrypted on the control plane and is not distributed to agents. The control plane downloads hash lists and sends them through authenticated connections. Uploaded files are not submitted to MalwareBazaar. Updates from the settings screen run when requested.
Limits
Unknown or modified malware may not match; archives are not unpacked. Missing downloaded data can leave only the EICAR test signature, and this fallback is not currently classified as an incomplete scan. Verify the actual feed separately from EICAR tests. Incomplete scans default to forwarding with a log; other WAF policies still apply.