Skip to content
skopnix
← IBM QRadar detectionsIBM QRadar · Indicator

Outbound connection to known-malicious IP

AQLhighconfidence 77/100generated 2026-10-18

Hunt for any event whose Destination IP is in "Skopnix: Malicious IPs" (12 skopnix IP indicators).

ATT&CK
T1071 mitre ↗
Linked actors
APT19 · Callisto · Common Raven · GreenSpot · Operation C-Major · Tortoiseshell · UAT-9244 · Water Sigbin
False positives
Matches only members of the skopnix reference set (high-confidence, multi-source, warninglist-clean, time-to-live bounded). Add RFC1918 and your known-good destinations to the exclusion building block.

AQL search

skopnix-qradar-ioc-class-ip-0f1f9447.aqldownload .aql ↓
SELECT sourceip, destinationip, destinationport, QIDNAME(qid) AS event, "URL Host"
FROM events
WHERE REFERENCESETCONTAINS('Skopnix: Malicious IPs', destinationip)
LAST 7 DAYS

CRE rule (build in Offenses > Rules)

download .txt ↓
Rule name: "Skopnix: Outbound connection to known-malicious IP"
Rule type: Event
Test stack:
  - and when the event(s) were detected by one or more of [any]
  - and when any of Destination IP is contained in any of Reference Set - "Skopnix: Malicious IPs"
  - and NOT when an event matches any of the following BB:Skopnix Known-Good Exclusions
Response: dispatch new event / create offense indexed by Source IP; annotate "Skopnix C2 match".
FP-safety: BB:Skopnix Known-Good Exclusions = RFC1918 + the customer's known-good destinations; the set only ever holds skopnix high-confidence, multi-source, warninglist-clean indicators (time-to-live 30 days, timeout on last seen).

This search reads the reference set Skopnix: Malicious IPs; its spec and members are on the QRadar page.

How to deploy on IBM QRadar

  1. 1.Create the reference set from its spec (Reference Data API, or Admin > Reference Set Management) and schedule the skopnix feed load.
  2. 2.Paste the AQL into Log Activity > Advanced Search to hunt the last seven days.
  3. 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.

References