This repository provides threat hunting resources, including Nexthink advanced hunting queries, Azure Sentinel rules, and EDR block rules to detect potential malware downloads, credential theft, and exploitation of vulnerabilities like Exchange ProxyShell and PaperCut CVEs across Windows environments.
Find a file
Kevin Beaumont 236e0da0db
Add KQL queries for CVE-2026-66804 detection
Added KQL queries for detecting CVE-2026-66804 exploitation through DLL drops and loads.
2026-08-14 09:46:10 +01:00
AdvancedHuntingQueries Add KQL queries for CVE-2026-66804 detection 2026-08-14 09:46:10 +01:00
AzureSentinel Create Successful-AITM-Phishing-Login 2023-04-24 13:07:41 +01:00
EDR-BlockRules Create CVE-2021-36934-HiveNightmare-Mcafee 2021-07-22 11:03:55 +01:00
YARA Create DragonForce-Payload.YAR 2025-04-30 22:18:25 +01:00
LICENSE Initial commit 2017-12-07 20:51:41 +00:00
porg.jpg Add files via upload 2021-07-26 15:54:16 +01:00
README.md Update README.md 2018-02-16 14:38:02 +00:00
Threat hunting - Potential malware downloads v1.0.xml Add files via upload 2018-02-16 14:37:31 +00:00

ThreatHunting

I am publishing GPL v3 tools for hunting for threats in your organisations.

Nexthink modules

Threat hunting - Potential malware downloads v1.0.xml

This is a report which shows all calls to internet domains from common malware document techniques. Most endpoint malware - such as macros, Office exploits etc - use the same set of methods to download their payloads.

The methods currently monitored include:

  • rundll32
  • mshta
  • PowerShell
  • wscript/cscript
  • wmic
  • sct remote calls
  • InfDefaultInstall (Inf remote calls)
  • certutil

The report will show domains. You can change the report to show users, executables instead if you want, or investigate each domain

In terms of false positives, you will very likely want to add a rule to filter out traffic destined for your internal IP ranges, or whitelist domains inside your environment. For example, when adding a Printer it will call rundll32, and hit the printer for web traffic - which triggers in the report - just whitelist it.