Try in Splunk Security Cloud


The following analytic identifies a process making a DNS query to Discord, excluding legitimate Discord application paths. It leverages Sysmon logs with Event ID 22 to detect DNS queries containing "discord" in the QueryName field. This activity is significant because Discord can be abused by adversaries to host and download malicious files, as seen in the WhisperGate campaign. If confirmed malicious, this could indicate malware attempting to download additional payloads from Discord, potentially leading to further code execution and compromise of the affected system.

  • Type: Anomaly
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud

  • Last Updated: 2024-05-16
  • Author: Teoderick Contreras, Mauricio Velazco, Splunk
  • ID: 4d4332ae-792c-11ec-89c1-acde48001122




ID Technique Tactic
T1059.005 Visual Basic Execution
T1059 Command and Scripting Interpreter Execution
Kill Chain Phase
  • Installation
  • DE.AE
  • CIS 10
`sysmon` EventCode=22 QueryName IN ("*discord*") Image != "*\\AppData\\Local\\Discord\\*" AND Image != "*\\Program Files*" AND Image != "discord.exe" 
| stats count min(_time) as firstTime max(_time) as lastTime by Image QueryName QueryStatus process_name QueryResults Computer 
| rename Computer as dest 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)` 
| `suspicious_process_with_discord_dns_query_filter`


The SPL above uses the following Macros:

:information_source: suspicious_process_with_discord_dns_query_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.

Required fields

List of fields required to use this analytic.

  • _time
  • Image
  • QueryName
  • QueryStatus
  • process_name
  • QueryResults
  • dest

How To Implement

his detection relies on sysmon logs with the Event ID 22, DNS Query.

Known False Positives

Noise and false positive can be seen if the following instant messaging is allowed to use within corporate network. In this case, a filter is needed.

Associated Analytic Story


Risk Score Impact Confidence Message
64.0 80 80 suspicious process $process_name$ has a dns query in $QueryName$ on $dest$

:information_source: The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.


Test Dataset

Replay any dataset to Splunk Enterprise by using our tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

source | version: 3