Cloud Resource Hijacking
Also called Cryptojacking, Cloud cryptomining.
Abusing compromised cloud compute to run attacker workloads like cryptomining.
What it is
The misuse of compromised cloud accounts or workloads to run the attacker's own compute-heavy tasks, most commonly cryptocurrency mining, at the victim's expense. The goal is the victim's resources rather than their data.
Why it matters
Beyond the surprise bill, resource hijacking is a reliable signal that credentials or workloads were compromised, so a cost or usage spike often becomes the first thread of an investigation.
In practice
A sudden surge in expensive instances across regions tips off the team to a stolen key being used to spin up miners.
What to look for
- Unexpected instances, GPU types or regions in billing.
- Spikes in compute usage with no matching deploy.
- Connections to mining pools from workloads.
Common mistake
Treating the bill as the incident. Someone had credentials or code execution, and that needs investigating.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Amazon GuardDuty Cloud service
AWS threat detection that analyzes CloudTrail, VPC flow logs and DNS logs.
-
Microsoft Defender for Cloud Commercial
Posture and threat protection for Azure, AWS and Google Cloud.
-
Wiz Commercial
Maps cloud resources, identities and exposures into one graph of risk.
-
Prowler Open source
An open source tool that checks cloud accounts against benchmarks such as CIS.
Read next
- Cloud Workload Protection Platform: Runtime protection and visibility for VMs, containers, and serverless workloads.
- Cloud Persistence: Techniques that let an attacker retain cloud access across sessions.
- Access Keys: Static, long-lived credential pairs used to authenticate to cloud APIs.