T1496.001 Google Chronicle · YARA-L

Detect Compute Hijacking in Google Chronicle

Adversaries may leverage the compute resources of co-opted systems to mine cryptocurrency or perform other resource-intensive tasks, degrading system performance and hosted service availability. The most prevalent form is unauthorized cryptocurrency mining (cryptojacking), typically targeting Monero (XMR) via XMRig or derivative tools due to CPU-friendliness and transaction privacy. Threat actors including TeamTNT, Blue Mockingbird, Rocke, APT41, Kinsing, and Hildegard have deployed miners as follow-on payloads targeting Windows endpoints, Linux servers, and containerized environments. Miners connect to mining pools over stratum protocol (commonly ports 3333, 4444, 14444) and are often deployed alongside rootkits, cron-based persistence, and competing miner kill scripts.

MITRE ATT&CK

Tactic
Impact
Technique
T1496 Resource Hijacking
Sub-technique
T1496.001 Compute Hijacking
Canonical reference
https://attack.mitre.org/techniques/T1496/001/

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule t1496_001_compute_hijacking_cryptomining {
  meta:
    author = "Argus Detection Engineering"
    description = "Detects cryptocurrency mining (T1496.001) via known miner process names, mining CLI arguments, or outbound connections to mining pool ports."
    mitre_attack_tactic = "Impact"
    mitre_attack_technique = "T1496.001"
    severity = "HIGH"
    confidence = "HIGH"
    created = "2026-04-13"
    version = "1.0"

  events:
    (
      // Branch 1: Known miner process name
      $e.metadata.event_type = "PROCESS_LAUNCH" and
      (
        re.regex($e.principal.process.file.full_path, `(?i)(xmrig|xmrig-notls|xmrig-cuda|xmrig-amd|minerd|cpuminer|cpuminer-opt|ethminer|nbminer|t-rex|phoenixminer|nanominer|xmr-stak|xmrstak|rhminer|kdevtmpfsi|kinsing|sysupdate|networkservice|sysguard|kerberods)(\.exe)?$`) or
        re.regex($e.target.process.command_line, `(?i)(stratum\+tcp://|stratum\+ssl://|stratum2\+tcp://|--donate-level|--mining-threads|--coin\s+(monero|xmr)|pool\.minexmr|pool\.hashvault|supportxmr\.com|nanopool\.org|monerohash\.com|cryptonight|randomx|--max-cpu-usage|-o\s+stratum)`)
      )
    ) or
    (
      // Branch 2: Mining pool port connection
      $e.metadata.event_type = "NETWORK_CONNECTION" and
      $e.target.port in (3333, 4444, 5555, 7777, 14444, 45700, 3032, 8008, 9999, 14433, 45560) and
      not net.ip_in_range_cidr($e.target.ip, "10.0.0.0/8") and
      not net.ip_in_range_cidr($e.target.ip, "172.16.0.0/12") and
      not net.ip_in_range_cidr($e.target.ip, "192.168.0.0/16") and
      not net.ip_in_range_cidr($e.target.ip, "127.0.0.0/8")
    )

  condition:
    $e
}
high severity high confidence

Chronicle YARA-L 2.0 rule detecting T1496.001 Compute Hijacking via two branches: (1) process launch events matching known cryptocurrency miner binary names or mining-specific command-line arguments using UDM fields, and (2) network connection events to common stratum mining pool ports excluding RFC1918 and loopback ranges.

Data Sources

Google Chronicle UDMChronicle Forwarder (Windows endpoints)Chronicle Forwarder (Linux endpoints)Google Cloud Chronicle with Sysmon ingestion

Required Tables

UDM PROCESS_LAUNCH eventsUDM NETWORK_CONNECTION events

False Positives & Tuning

  • Authorized cryptocurrency treasury or finance tooling connecting to exchange APIs on common ports
  • Blockchain node software that communicates over stratum-adjacent ports for P2P consensus
  • Developer environments running local mining pool simulators for testing DeFi applications
Download portable Sigma rule (.yml)

Other platforms for T1496.001


Testing Methodology

Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1XMRig Miner Execution with Pool Arguments (Windows)

    Expected signal: Sysmon Event ID 1: Process Create with Image=xmrig.exe, CommandLine containing '--donate-level', 'stratum+tcp://', '--max-cpu-usage'. Sysmon Event ID 3: Network connection attempt to 127.0.0.1:3333 (will fail). Security Event ID 4688 if command line auditing enabled. High CPU utilization visible in performance counters immediately after launch.

  2. Test 2XMRig Miner Execution via PowerShell Download Cradle (Windows)

    Expected signal: Sysmon Event ID 1: Process Create for powershell.exe with '-ExecutionPolicy Bypass -WindowStyle Hidden'. Sysmon Event ID 3: Network connection attempt to 127.0.0.1:8080 from powershell.exe. PowerShell ScriptBlock Log Event ID 4104 with full download cradle content. If the download succeeded: second Sysmon Event ID 1 for svchost32.exe with mining arguments.

  3. Test 3Miner Persistence via Linux Cron Job

    Expected signal: Linux auditd: syscall=execve for crontab command. On next cron tick: process creation for bash/sh spawning curl with mining-related URL, then chmod +x on /tmp/kdevtmpfsi, then execution of /tmp/kdevtmpfsi. If MDE Linux agent enrolled: DeviceProcessEvents showing cron as initiating process spawning curl and the miner binary.

  4. Test 4Mining Pool Network Connection Simulation

    Expected signal: Sysmon Event ID 3: three network connection events from powershell.exe to 127.0.0.1 on ports 3333, 4444, and 14444. Connections will fail (no listener) but the event is generated on the SYN attempt. Windows Firewall log entries for outbound connection attempts on mining ports.

Unlock Pro Content

Get the full detection package for T1496.001 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections