T1496_resource-hijacking

T1496 Resource Hijacking

High-Level Description

Adversaries may leverage the resources of co-opted systems to complete resource-intensive tasks, which may impact system and/or hosted service availability.

Resource hijacking may take a number of different forms. For example, adversaries may:

• Leverage compute resources in order to mine cryptocurrency
• Sell network bandwidth to proxy networks
• Generate SMS traffic for profit
• Abuse cloud-based messaging services to send large quantities of spam messages

In some cases, adversaries may leverage multiple types of Resource Hijacking at once.

Kill Chain Phase

• Impact (TA0040)

Platforms: Windows, IaaS, Linux, macOS, Containers, SaaS

What to Check

• Identify if Resource Hijacking technique is applicable to target environment
• Check Windows systems for indicators of Resource Hijacking
• Check IaaS systems for indicators of Resource Hijacking
• Check Linux systems for indicators of Resource Hijacking
• Assess detection coverage (1 detection strategies)

How to Test

Atomic Red Team Tests

The following tests are from Atomic Red Team and provide actionable ways to test this technique:

Atomic Test 1: FreeBSD/macOS/Linux - Simulate CPU Load with Yes

This test simulates a high CPU load as you might observe during cryptojacking attacks. End the test by using CTRL/CMD+C to break.

Supported Platforms: linux, macos

yes > /dev/null

Atomic Test 2: Windows - Simulate CPU Load with PowerShell

This test simulates high CPU load using PowerShell, commonly seen in resource hijacking. Spawns background jobs to stress CPU cores for a specified duration.

Supported Platforms: windows

$end = (Get-Date).AddSeconds(#{duration_seconds})
1..#{cpu_threads} | ForEach-Object { Start-Job { param($t) while((Get-Date) -lt $t) { $i=0; while($i -lt 200000){$i++} } } -ArgumentList $end }
Get-Job | Wait-Job | Remove-Job

Manual Testing

If Atomic Red Team tests are not applicable, manually verify the technique by:

1. Identify Attack Surface: Determine if the target environment is susceptible to Resource Hijacking by examining the target platforms (Windows, IaaS, Linux).

2. Assess Existing Defenses: Review whether mitigations for T1496 are in place. If defenses are absent or misconfigured, this technique may be exploitable.

3. Execute Test: Use tools and methods described in the MITRE ATT&CK page and external references below.

Remediation Guide

No specific mitigations documented for this technique.

Detection

Resource Hijacking Detection Strategy

Risk Assessment

CWE Categories

References

• Sysdig Cryptojacking Proxyjacking 2023
• Atomic Red Team - T1496
• MITRE ATT&CK - T1496