Many companies stopped using the data platform Qubole long ago. But the access they gave it inside their AWS accounts often stayed behind. In October, an attacker used that leftover access to break into more than a dozen organizations.
Researchers at Sentra and Wiz say the attacker got hold of IAM credentials from an AWS account linked to Qubole. From there, they took over the cross-account roles that customers had set up so Qubole could reach their data. Many of those roles were stale, still active after customers had stopped using the service.
The main activity ran from October 14 to 26, after a separate key-testing campaign on October 8 to 11. The attacker copied data from S3 storage, pulled secrets and credentials, and tested what they found using the open source tool TruffleHog. Their sessions used names starting with "quiam-". Traffic came through an OVH server and the Mullvad VPN. Wiz found no sign of a state-backed group.
The lesson applies to every cloud customer. Each third-party integration you add usually comes with a trust relationship in your account. When you stop using the vendor, that trust does not remove itself.
Three steps worth taking this week:
- List every IAM role that trusts an outside AWS account.
- Remove roles for vendors you no longer use.
- Search CloudTrail for sessions named "quiam-" and for unusual S3 reads since early October.
