Skip to content
skopnix
← IBM QRadar detections

IBM QRadar · Actor indicator sweep

Tortoiseshell file hash indicators (historical, hunt only)

severity
low
confidence
75/100
generated
14 Nov 2026
Linked actors
Tortoiseshell

4 file hash indicators skopnix attributes to Tortoiseshell, 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. 4 indicators. Evidence: 4 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: Tortoiseshell - file hashes (historical)', "File Hash")LAST 7 DAYS

skopnix-qradar-actor-tortoiseshell-hash-hist-003c7a4b.aql

4 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.