PIVTR-D
ROracle Cloud playbook · Compute and containers

Resource hijacking and cryptomining

The attacker launches large or GPU instances, instance pools or Kubernetes node pools with stolen credentials, often in a region the tenancy does not use or has recently subscribed to. Back up one attacker boot volume as evidence, then stop the pools and instances and block launches in unused regions.

Look here

LogSearch for
Audit, every subscribed regionLaunches, pools, clusters and new region subscriptions: LaunchInstance, CreateInstanceConfiguration, CreateInstancePool, CreateCluster, CreateNodePool, UpdateInstance, CreateRegionSubscription
Audit export per regionInstance launches with time, principal and resource name: oci audit event list -c <compartment-ocid> --region <region> --start-time <utc> --end-time <utc> --all | jq '.data[] | select(.data."event-name" == "LaunchInstance") | [."event-time", .data.identity."principal-name", .data."resource-name"]'
Region subscriptionsRegions the business does not use, in the output of oci iam region-subscription list
Running computeLarge or GPU shapes and recent creation times, in shape and time-created: oci compute instance list -c <compartment-ocid> --region <region> --lifecycle-state RUNNING --all
EventsAlerts on new instances, from rules on com.oraclecloud.computeapi.launchinstance.end

Contain

#Item
1Back up the boot volume of one attacker instance for evidence: oci bv boot-volume-backup create --boot-volume-id <ocid> --display-name <case-id>
2Stop attacker instance pools as a whole. A pool relaunches instances you stop one by one: oci compute-management instance-pool stop --instance-pool-id <ocid>
3Stop the remaining instances: oci compute instance action --instance-id <ocid> --action STOP
4Set compute quotas to zero in regions you do not use: oci limits quota create -c <tenancy-ocid> --name <name> --description <text> --statements '["zero compute-core quotas in tenancy where request.region = <region>"]'
5Block the credentials that launched them, as in credential leak

Eradicate and recover

#Item
1After evidence is taken, terminate the attacker instances destructive: oci compute instance terminate --instance-id <ocid> --preserve-boot-volume true
2Delete the instance pools, instance configurations, clusters and node pools the attacker created destructive
3Check the metadata of legitimate instances for changed user data or startup scripts
4Review limit increase requests raised in the window
5Keep region quotas in place and set budget alerts on the tenancy
Watch out
  • A zero quota blocks new launches. It does not stop instances that are already running.
  • Stopping pauses billing for standard shapes only. Dense I/O, HPC and some GPU shapes keep billing while stopped, so delete the pool or terminate the instances once evidence is saved.
  • A region subscription cannot be removed. Keep a zero quota on regions you do not use.

OCI CLI 3.94.2 help for audit event list, iam region-subscription list, compute instance, compute-management instance-pool, bv boot-volume-backup create and limits quota create. Checked October 2026.

Adapts material from Dynamic Incident Response: A Framework for Security Teams by Joshua Wright, © 2026 The Escal Institute of Advanced Technologies, Inc. d/b/a SANS Institute, licensed under CC BY 4.0. Figures reproduced under that license. Changes were made. Not published by, endorsed by, or affiliated with the SANS Institute.