IBM QRadar · Actor indicator sweep
Whitefly file hash indicators (historical, hunt only)
- severity
- low
- confidence
- 75/100
- generated
- 14 Nov 2026
- Linked actors
- Whitefly
2 file hash indicators skopnix attributes to Whitefly, named in published reports without live feed evidence. Retro-hunt only.
False-positive notes
HISTORICAL, HUNT ONLY: do not block on this. These indicators come from published reports and do not meet the bar of the live sweep. 2 indicators. Evidence: 2 with no threat-feed evidence (named in published reports only). No feed sighting date exists for any of them. Screened against reserved space, public known-good lists (CDN / cloud / scanners / top sites), internet-noise reputation when enriched, and sinkhole address lists. Re-validate against last_seen before blocking: infrastructure is re-assigned.
References
SELECT sourceip, username, QIDNAME(qid) AS event, LOGSOURCENAME(logsourceid) AS log_source, "File Hash"FROM eventsWHERE REFERENCESETCONTAINS('Skopnix: Whitefly - file hashes (historical)', "File Hash")LAST 7 DAYSskopnix-qradar-actor-whitefly-hash-hist-5536db71.aql
2 elements · one per line for a bulk import ↓
How to deploy on IBM QRadar
- Step 1
- Create the reference set from its spec (Reference Data API, or Admin > Reference Set Management) and schedule the skopnix feed load.
- Step 2
- Paste the AQL into Log Activity > Advanced Search to hunt the last seven days.
- Step 3
- For alerting, build the CRE rule from the test stack shown and exclude your known-good building block.
- Check
- Custom properties ("URL Host", "URL", "File Hash", "Process CommandLine") come from your DSMs and content extensions; rename them if yours differ.