hunting-for-living-off-the-land-binaries

Detect adversary abuse of legitimate Windows binaries using EDR and SIEM telemetry.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Attackers abuse trusted, Microsoft-signed binaries like certutil, mshta, and rundll32 to execute malicious payloads while evading antivirus and signature-based detection, leaving defenders with blind spots that standard reputation-based tools cannot close.

Core Features & Use Cases

  • Hypothesis-Driven Hunting: Guides a structured workflow from threat-intel hypothesis through telemetry collection, baselining, anomaly detection, and reporting.
  • Detection Gap Coverage: Addresses renamed LOLBins via OriginalFileName and hash matching, obfuscated command lines, and long-tail binaries like msdt.exe and mavinject.exe.
  • Validation & Tuning: Includes Atomic Red Team test cases (T1218.010, T1218.011, T1140) and false-positive tuning guidance by parent process, path, and signer.
  • Use Case: After threat intel reports certutil download cradles in active campaigns, hunt Sysmon Event ID 1 and network logs for certutil executions with outbound connections, then produce a structured hunt report with IOCs and new detection rules.

Quick Start

Hunt my environment for malicious use of LOLBins such as certutil, mshta, rundll32, and regsvr32 over the past 30 days using Sysmon and EDR telemetry.

Frequently Asked Questions about hunting-for-living-off-the-land-binaries

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

FAQPage Schema
How do I detect LOLBin abuse in Windows environments?

Detect LOLBin abuse by hunting process creation telemetry (Sysmon Event ID 1, Windows 4688) for binaries like certutil, mshta, rundll32, and regsvr32 with unusual command-line arguments, parent processes, or network connections. Match on OriginalFileName and hashes rather than on-disk filenames to catch renamed copies.

What is the LOLBAS project and how is it used in threat hunting?

The LOLBAS Project (lolbas-project.github.io) is a community-curated database of Windows binaries, libraries, and scripts that attackers can abuse for malicious purposes. Hunters use it to select target binaries and understand each binary's legitimate versus suspicious execution patterns.

Why do LOLBin detections based on image filename fail?

Attackers rename or copy binaries like certutil.exe to evade Image-name rules, making filename matching the biggest false-negative source. Detection should match Sysmon OriginalFileName and file hashes, and rely on behavioral signals like arguments, parent process, and network activity.

How do I validate that my LOLBin detection rules actually fire?

Run Atomic Red Team tests T1218.010 (regsvr32 Squiblydoo), T1218.011 (rundll32), and T1140 (certutil download), then confirm Sysmon Event ID 1 command lines and Event ID 3 outbound connections appear and that your detection rule matches the generated telemetry.

How do I reduce false positives when hunting for LOLBins?

Baseline legitimate usage by parent process, execution path, and signer before alerting. Common false positives include certutil for certificate operations, rundll32 spawned by installers, and msbuild on developer machines, which should be excluded through environment-specific tuning.