Security & compliance analyst view of the incident
A vendor role can remain usable long after the vendor stops being used. That was the uncomfortable lesson in the Qubole cloud incident: investigators observed a threat actor using credentials associated with Qubole’s AWS account to assume customer-created integration roles, then enumerate resources, collect secrets and access S3 data. Wiz said the observed activity ran from October 14 through October 26, 2026, in work with Sentra and Mandiant. This account describes the observed activity, not proof that every Qubole customer or every connected service was affected. Wiz’s incident analysis
BleepingComputer likewise reported compromised IAM credentials from Qubole’s big-data platform AWS account being used to access multiple cloud environments. Its report is useful context, but the technical detail and indicators below come from the investigation published by Wiz. BleepingComputer’s report
What is identity and access management (IAM)?
Identity and access management (IAM) is the system of identities, permissions and rules that determines who—or what service—can access a resource and what actions it may perform. In AWS, IAM policies assign permissions, while role trust policies determine which identities may assume a role. In a cross-account integration, a customer can create a role that trusts a vendor’s AWS account; a vendor identity then requests temporary access to that customer role. The trust relationship is deliberate, but it is still an access path that needs review. Wiz explains the cross-account model
Put simply, what is IAM identity access management? It is the control plane for identities and permissions—not just a login screen. For analysts, the practical question is whether the trusted principal, network, role permissions and business need still match. A valid credential can still be used from an unexpected place, and a dormant role can still accept it.
How the Qubole access path worked
Customers had created integration roles in their own AWS accounts whose trust policies allowed Qubole’s account to assume them. Wiz identified source AWS account 805246085872 in observed role assumptions. The report describes two IAM principal IDs: AIDA3W7DIFLYOLTK63SFS, which investigators saw only in threat-actor activity, and AIDAJYRRH5Y3A7AAJM2HW, which also generated legitimate platform traffic from AWS infrastructure. That distinction matters: account ID alone does not establish malicious activity. Wiz’s technical findings
Once a role was assumed, the actor enumerated customer resources and collected configuration and secrets. Investigators reported access involving Secrets Manager, Systems Manager Parameter Store, Lambda configuration and S3. They also observed credential validation activity, including AWS GetCallerIdentity calls using a TruffleHog user agent and Entra ID sign-ins. These are reported investigation details; the article does not establish that every account exposed all of those services or that every discovered credential was successfully used. Wiz’s technical findings
TruffleHog and the unfinished secret trail
TruffleHog appeared in the investigation as a credential-validation signal, not as proof by itself of compromise. Wiz says the tool was used to validate credentials through AWS GetCallerIdentity and Entra ID sign-ins, and warns that security teams also use TruffleHog legitimately. Treat the user agent as a clue to correlate with source IPs, principal IDs, role sessions and identity-provider sign-in logs—not as a standalone verdict. Wiz’s detection guidance
The reason this signal deserves attention is what exposed credentials can lead to: onward access to other cloud services or identities. The available reporting identifies credentials and secrets as material collected, but does not establish a complete inventory of what the actor recovered or prove that any particular downstream account was entered. Do not overstate the chain. Investigate the actual permissions of each assumed role and the subsequent audit events, then rotate every secret, parameter and Lambda environment variable the role could read if the role was used maliciously. Wiz’s response recommendations
Detecting activity in AWS CloudTrail
Wiz recommends reviewing CloudTrail from October 1, 2026 onward in each account that has a Qubole integration role. Search AssumeRole events where the caller account is 805246085872 and the source IP is not AWS infrastructure; Wiz says the legitimate platform traffic it observed came from AWS infrastructure. Also investigate principal AIDA3W7DIFLYOLTK63SFS; for AIDAJYRRH5Y3A7AAJM2HW, distinguish unexpected non-AWS source addresses from ordinary platform traffic. These are incident-specific hunting leads, not universal detection rules for all vendors. Wiz’s hunting guidance
Correlate the role session with subsequent Secrets Manager, SSM Parameter Store, Lambda and S3 activity. Wiz calls out quiam-* session names and several IP addresses and user agents, but cautions that common tooling such as AWS CLI, Boto3 and TruffleHog can be legitimate. A VPN exit-node match alone is not conclusive either. Use multiple indicators and examine what the session actually did. Wiz’s indicators and response guidance
For every suspicious session, revoke active sessions for the role as appropriate and rotate accessible secrets. Rotation does not terminate temporary sessions already issued, so session revocation is a separate response step. Check identity-provider sign-in records for the TruffleHog user agent and connect any matching activity to the AWS timeline. Wiz’s incident response guidance
Reduce third-party IAM exposure
Start with an inventory. Find roles whose trust policies allow external AWS accounts, identify their owners and permissions, and confirm that each integration remains in use. Remove trust relationships for retired services. Wiz reported that some affected environments had no legitimate vendor traffic during the activity, yet their roles still accepted assumptions. Dormant access is not harmless access. Wiz’s recommendations
Where the vendor supports it, narrow trust from a broad account-level principal to the specific principal it uses. Add aws:SourceIp or aws:SourceVpce conditions matching documented vendor network ranges. Wiz says a source-IP condition alone would have blocked every role assumption it observed. External IDs can help address cross-account confusion, but they are logged in plaintext in CloudTrail and may be stored in vendor systems and infrastructure-as-code; do not treat them as secrets or as the only safeguard. Wiz’s trust-policy recommendations
Least privilege matters just as much. Limit vendor roles’ access to secrets, Lambda configuration, parameters and broad S3 reads to what the integration needs. Alert when a vendor role is assumed from an unfamiliar network, and ensure organization-wide logging covers accounts and regions. Wiz also recommends enabling S3 data events or server access logging for sensitive buckets; in some investigated environments, missing logs prevented responders from determining which S3 objects had been read. Wiz’s logging and least-privilege recommendations
A practical incident-response sequence
For a security & compliance analyst, response should be evidence-led: identify every account with the integration role; preserve and query CloudTrail; match caller account, principal, source address and session; then trace each session’s service calls. Determine which secrets and data the role could reach, not merely which services were named in a report. If evidence supports malicious role use, contain the trust path, revoke sessions, rotate exposed credentials, and review identity-provider events for reuse. Record logging gaps explicitly rather than inferring that no access occurred. The specific hunting and containment steps are consistent with Wiz’s published guidance. Wiz’s incident response guidance
Conclusion: trust should be narrow and current
The Qubole incident was not simply a story about a stolen key. It showed how a vendor identity can inherit reach into customer environments through trust policies customers created earlier—and may have forgotten. Analysts should treat third-party IAM access as a live dependency: document it, constrain it, monitor it and remove it when the business need ends. That is a defensible control whether the integration is Qubole or another cloud service. The investigation supports the value of scoped principals, network conditions, least privilege and complete audit coverage; it does not justify assuming every customer was affected. Wiz’s findings and recommendations