Resource Hijacking T1496
Tactic: Impact
Adversaries may leverage the resources of co-opted systems to complete resource-intensive tasks, which may impact system and/or hosted service availability.
Events covered
7 catalog events are tagged with this technique by at least one rule.
| Provider | Event | Title |
|---|---|---|
| Sysmon | Event ID 1 | Process creation |
| Sysmon | Event ID 3 | Network connection |
| Sysmon | Event ID 22 | DNSEvent (DNS query) |
| Security-Auditing | Event ID 4688 | A new process has been created. |
| PowerShell | Event ID 4104 | Creating Scriptblock text (MessageNumber of MessageTotal). |
| Sysmon-for-Linux | Event ID 1 | Process Create |
| Sysmon-for-Linux | Event ID 3 | Network connection |
Authoring guide
Patterns shared across the 52 rules above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.
Fields filtered most (66 distinct)
The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.
Top indicator values (817 distinct)
Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique. Click a value to expand the rules under this technique that use it.
Exclusions (58 distinct)
Field/operator/value combinations excluded by rules under this technique (top-level not() clauses), sorted by how many rules exclude each. These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths. Click a value to expand the rules under this technique that exclude it.
Rules under this technique
Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.
Sigma 13 rules
- Azure Container Registry Created or Deleted
- Azure Kubernetes Cluster Created or Deleted
- Azure Kubernetes Network Policy Change
- Azure Kubernetes RoleBinding/ClusterRoleBinding Modified and Deleted
- Azure Kubernetes Secret or Config Object Access
- Azure Kubernetes Sensitive Role Access
- Azure Kubernetes Service Account Modified or Deleted
- DNS Events Related To Mining Pools
- Linux Crypto Mining Indicators
- Linux Crypto Mining Pool Connections
- Monero Crypto Coin Mining Pool Lookup
- Network Communication With Crypto Mining Pool
- Potential Crypto Mining Activity
Elastic 8 rules
- AWS Bedrock Provisioned Model Throughput Tampering
- AWS SNS Rare Protocol Subscription by User
- AWS SNS Topic Created by Rare User
- AWS SNS Topic Message Publish by Rare User
- Memory Swap Modification
- Newly Observed Process Exhibiting High CPU Usage
- Potential Malware-Driven SSH Brute Force Attempt
- Suspicious Mining Process Creation Event
Splunk 3 rules
- Potential Cryptomining Commands (PowerShell)
- Potential Cryptomining Commands (Sysmon)
- Potential Cryptomining Commands (Windows Event Log)
Kusto 19 rules
- A host is potentially running a crypto miner (ASIM Web Session schema)
- AWSCloudTrail - Suspicious AWS EC2 Compute Resource Deployments
- Azure DevOps Personal Access Token (PAT) misuse
- Azure DevOps Service Connection Abuse
- Azure DevOps Service Connection Addition/Abuse - Historic allow list
- Azure Machine Learning Write Operations
- Chia_Crypto_Mining IOC - June 2021
- Cisco Cloud Security - Crypto Miner User-Agent Detected
- Detect CoreBackUp Deletion Activity from related Security Alerts
- DNS events related to mining pools
- DNS events related to mining pools (ASIM DNS Schema)
- F&O - Reverted bank account number modifications
- Medium severity malicious activity detected
- NRT DNS events related to mining pools
- OCI - Multiple instances launched
- Subscription moved to another tenant
- Suspicious number of resource creation or deployment activities
- Suspicious Resource deployment
- VMware ESXi - Unexpected disk image