The Mechanism
How Cloud Hopping relocates infrastructure state across providers, regions, and instances — faster than anyone can follow.
← Back to Cloud HoppingThe mechanism is simple.
A compute node materializes on a random provider in a random region. The full infrastructure state — config, secrets, data references — is redeployed to it. It becomes operational, issues commands to endpoints, and then destroys itself. Memory zeroed, disk wiped, instance terminated.
Before it dies, the next node is already spinning up somewhere else. Compute and data move independently, faster than any adversary can follow.
An adversary watching the network sees unrelated IPs appearing and disappearing across dozens of countries. There is no pattern to find because there is no pattern.
Node Lifecycle
Random region
at new location
to endpoints
for next location
Instance killed