MITRE ATT&CK technique · T1496

Resource Hijacking

What is resource hijacking in the cloud? Adversaries use the victim’s compute, network or paid services for their own purposes — cryptocurrency mining, running their workloads, or consuming AI model capacity — at the victim’s expense.

ImpactPlatforms: Containers, IaaS, Linux, SaaS, Windows, macOSATT&CK v20.1 · source modified · View on MITRE ATT&CK

For leadership

Executive takeaway

Cost anomaly alerts and region restrictions are cheap controls that often catch this before the bill does.

How it works in AWS

  1. Launch large or GPU instances, often in unused regions.
  2. Request quota increases.
  3. Invoke paid AI models with stolen credentials.

What the attacker needs

  • Compute-launch or service-invoke permissions
  • Available quota

Relevant AWS API calls

AWS API calls relevant to T1496
API / eventWhy it matters
ec2:RunInstancesLaunch compute.
servicequotas:RequestServiceQuotaIncreaseRaise limits.
bedrock:InvokeModelConsume model capacity.

A risky permission is not an observed attack

Potential exposure

No region restrictions; long-lived keys with compute permissions; generous quotas.

Observed behavior

Launches in unused regions; spend anomalies; mining network findings.

Preventive and limiting controls

  • SCP denying unused regions and unapproved instance types
  • Realistic quotas
  • Short-lived credentials

Mapped cloud controls

  • detectiveCost and quota anomaly monitoring

    Unexpected compute, GPU or AI-service spend is often the first visible signal of hijacked resources.

  • restrictiveService control policy guardrails

    Region and instance-type restrictions limit where and how much compute an attacker can launch.

  • detectiveManaged threat detection across accounts and regions

    GuardDuty has findings for cryptocurrency-mining related network activity.

See assumptions and validation evidence in the Cloud Control Explorer →

Detection signals and telemetry

  • Spend anomalies — Cost Anomaly Detection
  • Mining-related activity — GuardDuty

MITRE detection strategies (official, cloud-relevant analytics)

  • DET0267 Resource Hijacking Detection Strategy
    • AN0744 (IaaS): Sudden spikes in cloud VM CPU usage with outbound traffic to mining pools and unauthorized instance creation.Log sources: AWS:CloudTrail — RunInstances; AWS:CloudWatch — Sustained EC2 CPU usage above normal baseline; AWS:VPCFlowLogs — Outbound flow logs to known mining pools
    • AN0745 (Containers): High CPU usage by unauthorized containers running mining binaries or public proxy tools.Log sources: containerd:events — New container with suspicious image name or high resource usage; prometheus:metrics — Container CPU/Memory usage exceeding threshold; container:cni — Outbound network traffic to mining proxies
    • AN0746 (SaaS): Abuse of cloud messaging platforms to send mass spam or consume quota-based resources.Log sources: m365:unified — SendMessage; saas:application — High-volume API calls or traffic via messaging or webhook service

Official MITRE description (excerpt)

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.

Common misconceptions

“If no data was taken, it is not a security incident.”
Resource hijacking proves an adversary had working credentials; investigate scope.

AI security

Related MITRE ATLAS techniques

ATLAS and ATT&CK are separate frameworks. These relationships are listed explicitly, with their basis.

    Model and AI service access management →

    Attack scenarios using this technique

    References

    MITRE ATT&CK® and ATT&CK® are registered trademarks of The MITRE Corporation. ATT&CK data © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation (ATT&CK v20.1). Securitain is not affiliated with or endorsed by MITRE. Explanations, scenarios and control mappings on this page are Securitain’s own analysis. Sources and licensing

    Stay in the loop

    Cloud security insights, early access & compliance updates

    Weekly InsightsEarly AccessExpert Content
    No spam, everUnsubscribe anytimeWeekly updates
    Chat with Securitain