Edition of Thursday 12 November 2026

Hackers breached AWS accounts through unused third-party access permissions

Comments on “Hackers breached AWS accounts through unused third-party access permissions”

Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked

Wiz, with Sentra and Mandiant, reports that between October 14 and 26, 2026 an actor used IAM credentials from an AWS account tied to Qubole to assume customer-created roles, then enumerated resources, read secrets, validated keys with TruffleHog and downloaded S3 data. Most assumed roles were otherwise unused but still trusted the vendor account. Wiz says a source-IP condition would have blocked every observed assumption. The findings rest largely on Wiz's own telemetry, and an "n0n" claim of responsibility is unverified.

Read the original at wiz.io. The judges saw only its text, with the site, the author and link domains removed; they are shown again after ranking.

Why it ranked

No. 2 of 106 with a score of 0.80. The panel rated it highest on new information (0.94) and practical relevance (0.92), lowest on audience breadth (0.67). Placed No. 2, No. 1 by score alone: close to “Attackers backdoor trusted AWS integrations to steal secrets”, No. 26 on Tuesday 10 November 2026 (−0.043). The placement terms move stories; they are not part of the score.

AI judgeJudge 2claude-haiku-5-5
Detailed, IOC-rich incident report on cross-account IAM abuse via a vendor trust relationship, with clear defender guidance; significant, actionable and substantiated, though a single incident.
AI judgeJudge 3gpt-5.6-luna
A well-supported, technically detailed cloud supply-chain intrusion report with concrete IOCs, attack mechanics, hunting guidance, and actionable IAM mitigations. It is highly relevant to AWS defenders and broadly useful to organizations using third-party integrations.

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.80total under rubric v2.3

Judges’ mean answer per question, on a scale from 0 to 1. Questions marked minus count against the score.
  • Significance0.72
  • Reader interest0.88
  • Audience breadth0.67
  • Practical relevance0.92
  • Substantiated0.90
  • Technical depth0.91
  • New information0.94
  • Counts against: Promotional0.07
  • Counts against: Overclaim0.17

Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).

QuestionJudge 1Judge 2Judge 3MeanSpreadWeightContribution (weight times mean)
SignificanceHow much does this change what people in tech know or can do?0.690.700.780.720.09+0.24+0.174
Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on?0.820.900.930.880.11+0.26+0.230
Audience breadthHow many people who build technology does it concern?0.590.750.680.670.16+0.13+0.088
Practical relevanceHow useful is it to someone who builds software or tech products?0.940.900.920.920.04+0.22+0.202
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.940.850.910.900.09+0.05+0.045
Technical depthHow technically substantive is it?0.990.850.880.910.14+0.05+0.045
New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)?0.890.950.990.940.10+0.05+0.047
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.050.050.120.070.07−0.19−0.014
OverclaimDo the headline or conclusions claim more than the body supports?0.320.100.080.170.24−0.11−0.018
Sum of contributions+0.798
Claim-check penalty0.000
Total, as published0.798

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.

Ranked #2 on Rubric, 12 Nov 2026
<a href="https://rubric.hrih.si/editions/2026-11-12/2/"><img src="https://rubric.hrih.si/badge/2026-11-12/2.svg" alt="Ranked #2 on Rubric, 12 Nov 2026" width="238" height="28"></a>

Claim check

Claim check: 1 matches source · 6 no source given · 1 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.

  1. No source givenDate

    Wiz observed a threat actor using IAM credentials from an AWS account associated with Qubole between October 14 and October 26, 2026 to assume customer IAM roles.

    The article gives no link or citation for it.

    The article says

    “Wiz observed a threat actor using IAM credentials from an AWS account associated with Qubole between October 14 and October 26, 2026”

    The source says

    No source to compare with.

  2. Matches sourceCausal conclusion

    Sentra identified suspicious activity across several of its customer environments, recognized it as a broad supply chain attack, and shared the information with Wiz.

    The cited source says the same thing.

    The article says

    “Sentra identified suspicious activity across several of their customer environments”

    The source says

    “Sentra spotted the campaign and reported it to Wiz, which investigated it together with Sentra and Mandiant”

    Source cited by the article: sentra.io/blog/breaches/inside-the-qubole-supply-chain-attack

  3. Couldn’t checkQuote

    A threat actor calling themselves "n0n" has claimed responsibility for the intrusion, as reported by Catalin Cimpanu of the Risky Business newsletter.

    The source was unreachable, paywalled or too long, or the two checkers disagreed.

    The article says

    “an actor calling themselves "n0n" has claimed responsibility for this intrusion”

    The source says

    No passage could be compared.

    Source cited by the article: bsky.app/profile/campuscodi.risky.biz/post/3n22h4dxfck2x

  4. No source givenGeneralization

    In a majority of the observed environments, the threat actor's requests were the only AssumeRole activity from the vendor account in October, and the unused roles' trust policies still allowed the requests to succeed.

    The article gives no link or citation for it.

    The article says

    “In a majority of the environments Wiz CIRT observed, the threat actor's requests were the only AssumeRole activity from the vendor account in October”

    The source says

    No source to compare with.

  5. No source givenNumber

    The IAM user AIDA3W7DIFLYOLTK63SFS was not observed 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

    “Across the affected environments, 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.

  6. No source givenNumber

    The sso_agent.iso bootable Linux image runs a 90 minute clock, polls the actor's IP over TCP port 23458 for shell script input, then hard reboots to erase evidence.

    The article gives no link or citation for it.

    The article says

    “When the iso is started it begins a 90 minute clock, gathers system information and uploads interfaces and disk and partition lists to the 57.129.54[.]120 IP address”

    The source says

    No source to compare with.

  7. No source givenCausal conclusion

    A source IP condition alone would have blocked every role assumption Wiz observed in this activity.

    The article gives no link or citation for it.

    The article says

    “In this activity, a source IP condition alone would have blocked every role assumption we observed”

    The source says

    No source to compare with.

  8. No source givenDate

    Wiz identified separate malicious activity involving Qubole integrations from October 8 to October 11 using customer-owned AWS access keys, which it could not link to the role assumption activity.

    The article gives no link or citation for it.

    The article says

    “From October 8 to October 11, an actor used customer-owned AWS access keys that we believe were created for Qubole integrations”

    The source says

    No source to compare with.

Also covered by

No other coverage was clustered with this story.

Elsewhere

Elsewhere: HN 2 pts, not on front page

Discussion on Hacker News

Recorded for context only, checked 12 Nov 2026, 05:47 UTC. It played no part in the ranking.

Panel for this edition

Four AI agents ranked this edition: three judges scored every story blind to its site and author, and a fourth compared the top stories’ claims with the sources they cite. Summaries are written by AI.

Model versions are pinned for every edition. How ranking works describes rubric v2.3.

Comments

Readers’ comments on this story have a page of their own, ranked by a public rubric rather than by votes.

Comments on “Hackers breached AWS accounts through unused third-party access permissions”

More on Rubric

From the last 7 editions, chosen by shared topic, score and date.