Attackers backdoor trusted AWS integrations to steal secrets
Comments on “Attackers backdoor trusted AWS integrations to steal secrets”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Attackers used compromised AWS IAM credentials tied to Qubole's account to assume cross-account integration roles in customer environments, then stole secrets and data from S3 buckets. Wiz, working with Mandiant, called it a broad, opportunistic supply-chain campaign affecting multiple customers.
Why it ranked
No. 26 of 95 with a score of 0.69. The panel rated it highest on new information (0.87) and reader interest (0.82), lowest on substantiated (0.62). Placed No. 26, No. 11 by score alone: the ninth Security story of the day (−0.080), and close to “On the hunt for ARTEX: understanding agentic attacks in AWS environments”, No. 18 today (−0.021). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Supply-chain attack abusing cross-account IAM trust in a data platform; significant security news with detailed attacker activity, though excerpt is short and largely reports Wiz's findings.
- AI judgeJudge 3gpt-5.6-luna
- A significant cloud supply-chain compromise exploiting cross-account IAM trust, with concrete AWS identities, APIs, timeline, and affected-data details. The excerpt is news reporting rather than a reproducible technical analysis, and scope remains partly undisclosed.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.69total under rubric v2.3
- Significance0.65
- Reader interest0.82
- Audience breadth0.62
- Practical relevance0.75
- Substantiated0.62
- Technical depth0.62
- New information0.87
- Counts against: Promotional0.04
- Counts against: Overclaim0.20
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.69 | 0.55 | 0.72 | 0.65 | 0.17 | +0.24 | +0.157 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.77 | 0.80 | 0.90 | 0.82 | 0.13 | +0.26 | +0.214 |
| Audience breadthHow many people who build technology does it concern? | 0.56 | 0.60 | 0.70 | 0.62 | 0.14 | +0.13 | +0.081 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.69 | 0.75 | 0.80 | 0.75 | 0.10 | +0.22 | +0.165 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.55 | 0.60 | 0.70 | 0.62 | 0.15 | +0.05 | +0.031 |
| Technical depthHow technically substantive is it? | 0.70 | 0.60 | 0.55 | 0.62 | 0.15 | +0.05 | +0.031 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.81 | 0.85 | 0.95 | 0.87 | 0.14 | +0.05 | +0.044 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.06 | 0.03 | 0.02 | 0.04 | 0.04 | −0.19 | −0.007 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.32 | 0.20 | 0.08 | 0.20 | 0.24 | −0.11 | −0.022 |
| Sum of contributions | +0.692 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.692 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-10/26/"><img src="https://rubric.hrih.si/badge/2026-11-10/26.svg" alt="Ranked #26 on Rubric, 10 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 7 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenCausal conclusion
Unknown attackers used compromised IAM credentials associated with Qubole's AWS account to access customer AWS environments and steal secrets and other sensitive data from S3 buckets.
The article gives no link or citation for it.
The article says “Unknown attackers used compromised identity and access management (IAM) credentials associated with Qubole's AWS account to access customer AWS environments, stealing secrets and other sensitive data from S3 buckets”
The source says No source to compare with.
No source givenQuote
Wiz called the activity a "broad, opportunistic supply chain campaign" that hit "multiple" customer environments.
The article gives no link or citation for it.
The article says “called it a “broad, opportunistic supply chain campaign” that hit “multiple” customer environments”
The source says No source to compare with.
No source givenCausal conclusion
Wiz said the attacker succeeded because many organizations left trust policies active even after deprecating the Qubole platform.
The article gives no link or citation for it.
The article says “Because many organizations left trust policies active even after deprecating the platform, the attacker was able to successfully assume integration roles, enumerate cloud resources, harvest secrets, and siphon data”
The source says No source to compare with.
No source givenDate
Wiz, working with Mandiant after Sentra flagged suspicious activity, traced the malicious activity to October 14, when Qubole-associated credentials called sts:AssumeRole to obtain temporary credentials for customer-managed integration roles.
The article gives no link or citation for it.
The article says “traced the malicious activity back to October 14, when credentials associated with Qubole's AWS account were used to call the sts:AssumeRole API”
The source says No source to compare with.
No source givenNumber
The malicious calls originated from Qubole AWS account 805246085872 and used IAM user ID AIDA3W7DIFLYOLTK63SFS.
The article gives no link or citation for it.
The article says “The calls originated from Qubole AWS account 805246085872, and used IAM user ID AIDA3W7DIFLYOLTK63SFS”
The source says No source to compare with.
No source givenQuote
Wiz CIRT has not observed the IAM user in any activity other than that associated with this threat actor across the affected environments.
The article gives no link or citation for it.
The article says “Wiz CIRT has not observed this IAM user in any activity other than that associated with this threat actor”
The source says No source to compare with.
No source givenDate
The activity continued on October 15, and on October 18 the attackers began using a second IAM user from the same account.
The article gives no link or citation for it.
The article says “This activity continued on October 15, and on October 18, the digital intruders began using a second IAM user from the same account”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 3 pts, not on front page
Recorded for context only, checked 10 Nov 2026, 05:47 UTC. It played no part in the ranking.