detecting-living-off-the-land-attacks

Detect LOLBin abuse in Windows environments using Sysmon telemetry, Sigma rules, and parent-child process analysis.

954|172|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/xalgord/xalgorix --skill detecting-living-off-the-land-attacks
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: detecting-living-off-the-land-attacks
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/threat-detection/detecting-living-off-the-land-attacks
Command: npx skills add https://github.com/xalgord/xalgorix --skill detecting-living-off-the-land-attacks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires evtx, pandas.

What problem does it solve?

Attackers increasingly abuse legitimate Windows binaries like certutil, mshta, rundll32, and regsvr32 to execute payloads, download malware, and bypass application whitelisting without dropping obvious malicious files. Traditional signature-based detection misses these living-off-the-land techniques because the binaries themselves are trusted system tools, leaving security teams blind to fileless attacks.

Core Features & Use Cases

  • Sysmon Configuration for LOLBin Telemetry: Deploy a tuned Sysmon config capturing process creation and network connection events for over 25 known LOLBins.
  • Sigma Detection Rules: Ready-to-convert Sigma rules for certutil downloads, mshta remote script execution, and regsvr32 Squiblydoo attacks, translatable to any SIEM.
  • Behavioral Analysis Scripts: Python analyzers that flag suspicious command-line patterns, LOLBin outbound network connections, and anomalous parent-child relationships such as Office applications spawning script interpreters.
  • Use Case: A SOC analyst investigating an alert where winword.exe spawned certutil.exe can use the parent-child anomaly detection and command-line pattern matching to confirm a macro-based payload download, then validate coverage with Atomic Red Team tests for T1218.

Quick Start

Ask the AI to build Sigma detection rules and a Sysmon configuration that catch certutil, mshta, and rundll32 abuse on your Windows endpoints.

Frequently Asked Questions about detecting-living-off-the-land-attacks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect LOLBin abuse on Windows endpoints?

Deploy Sysmon with a configuration capturing process creation (Event ID 1) and network connections (Event ID 3) for known LOLBins like certutil, mshta, and rundll32. Then apply Sigma rules or Python analysis matching suspicious command-line patterns such as certutil -urlcache or regsvr32 with scrobj.dll.

What Sigma rules detect certutil and mshta attacks?

Certutil detection matches Image ending in certutil.exe with command lines containing urlcache, -f, and http. Mshta detection covers remote URL execution, inline vbscript or javascript payloads, and execution spawned by Office applications like winword.exe or outlook.exe.

Why do LOLBin detection rules miss renamed binaries?

Rules matching on Image path fail when attackers rename rundll32.exe to something else. Pivot to Sysmon's OriginalFileName field in Event ID 1, since Windows Security Event 4688 does not carry OriginalFileName and is trivially defeated by renaming.

How do I reduce false positives in LOLBin detection?

Baseline legitimate callers such as software installers, SCCM, and Intune, which commonly invoke rundll32, regsvr32, and msiexec. Scope alerts by parent process and outbound network activity from the LOLBin rather than triggering on execution alone.

Can I validate LOLBin detection rules before production deployment?

Yes, use Atomic Red Team tests T1218.010 for regsvr32 Squiblydoo, T1218.011 for rundll32, T1218.005 for mshta, and T1105 for certutil downloads. Run the renamed-binary case to confirm detection survives on OriginalFileName, and test against seven days of baseline telemetry.