On the hunt for ARTEX: understanding agentic attacks in AWS environments
Comments on “On the hunt for ARTEX: understanding agentic attacks in AWS environments”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Datadog Security Labs reports in-the-wild use of ARTEX, an AI-native penetration framework in which LLM agents plan and run attacks, against AWS environments in October. Observed paths were compromised long-term IAM keys, used to search CloudWatch logs for financial data and secrets, and public Cognito user pools, where the agent self-registered and tried to enumerate resources. Those discovery calls failed because the authenticated role lacked permissions. Datadog also found hundreds of exposed consoles. Defenders should rotate long-lived keys, restrict Cognito roles, and watch for AccessDenied bursts.
Why it ranked
No. 18 of 95 with a score of 0.71. The panel rated it highest on technical depth (0.86) and new information (0.86), lowest on significance (0.65). Placed No. 18, No. 6 by score alone: the seventh Security story of the day (−0.080), and close to “You Had Me at "Hello": A Chinese‑Language Framework Targeting AI Infrastructure”, No. 21 on Saturday 7 November 2026 (−0.006). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Detailed threat intelligence on an AI-driven pentest framework targeting AWS; well-evidenced with IOCs and detection guidance, but a vendor-published threat report with a promotional detection section.
- AI judgeJudge 3gpt-5.6-luna
- Detailed first-hand incident analysis provides AWS attack behaviors, Cognito and IAM abuse patterns, hunting guidance, and IOCs. It is highly actionable and timely, though the vendor-product section adds modest promotional content.
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.71total under rubric v2.3
- Significance0.65
- Reader interest0.82
- Audience breadth0.65
- Practical relevance0.79
- Substantiated0.84
- Technical depth0.86
- New information0.86
- Counts against: Promotional0.12
- Counts against: Overclaim0.18
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.61 | 0.55 | 0.78 | 0.65 | 0.23 | +0.24 | +0.155 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.75 | 0.80 | 0.90 | 0.82 | 0.15 | +0.26 | +0.212 |
| Audience breadthHow many people who build technology does it concern? | 0.62 | 0.60 | 0.72 | 0.65 | 0.12 | +0.13 | +0.084 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.77 | 0.75 | 0.86 | 0.79 | 0.11 | +0.22 | +0.174 |
| 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.83 | 0.80 | 0.88 | 0.84 | 0.08 | +0.05 | +0.042 |
| Technical depthHow technically substantive is it? | 0.95 | 0.80 | 0.84 | 0.86 | 0.15 | +0.05 | +0.043 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.89 | 0.75 | 0.93 | 0.86 | 0.18 | +0.05 | +0.043 |
| 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.09 | 0.10 | 0.18 | 0.12 | 0.09 | −0.19 | −0.023 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.19 | 0.20 | 0.14 | 0.18 | 0.06 | −0.11 | −0.019 |
| Sum of contributions | +0.711 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.711 | ||||||
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/18/"><img src="https://rubric.hrih.si/badge/2026-11-10/18.svg" alt="Ranked #18 on Rubric, 10 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 3 matches source · 5 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Matches sourceCausal conclusion
Microsoft tied ARTEX to Storm-0940, a China-aligned actor behind a recent supply-chain compromise.
The cited source says the same thing.
The article says “Microsoft tied it to Storm-0940, a China-aligned actor behind a recent supply-chain compromise”
The source says “Microsoft assesses that Storm-0940 was responsible for the recently disclosed ConnectWise supply chain compromise of a multi-tenant application”
Source cited by the article: microsoft.com/en-us/security/blog/2026/10/21/storm-0940-uses-artex-agentic-ai-connectwise-supply-chain-compromise
No source givenDate
A Chinese developer published ARTEX on GitHub in July 2026 and made it closed-source on October 8, after it had passed 12,000 forks.
The article gives no link or citation for it.
The article says “A Chinese developer published it on GitHub in July 2026 and made it closed-source on October 8, after it had passed 12,000 forks”
The source says No source to compare with.
Matches sourceQuote
Wiz noted that before each fuzzing run, ARTEX requested a nonexistent path (/zzz-nonexistent-xyz123) to learn what "not found" looks like.
The cited source says the same thing.
The article says “noted that before each fuzzing run, ARTEX requested a path that should not exist (/zzz-nonexistent-xyz123) to learn what "not found" looks like”
The source says “Before every fuzzing run, it checked what a baseline "not found" response looked like”
Source cited by the article: wiz.io/blog/artex-in-the-wild-storm-0940-expands-targeting-of-it-and-software-vendors
No source givenNumber
Datadog found hundreds of additional internet-exposed ARTEX consoles, often in Mandarin and hosted with providers in locations including Singapore and Hong Kong.
The article gives no link or citation for it.
The article says “found hundreds of additional internet-exposed ARTEX consoles, often in Mandarin and hosted with providers in locations including Singapore and Hong Kong”
The source says No source to compare with.
No source givenNumber
In one instance, every ARTEX FilterLogEvents call used a limit of 1000, below the API's 10,000-event maximum.
The article gives no link or citation for it.
The article says “Every FilterLogEvents call was set with a limit of 1000, below the API's 10,000-event maximum”
The source says No source to compare with.
No source givenDate
On October 20, the same long-term key was used again from IP 103.54.154[.]40, an address associated with zeofast[.]cn.
The article gives no link or citation for it.
The article says “On October 20, the same long-term key was used again from 103.54.154[.]40, an address associated with zeofast[.]cn”
The source says No source to compare with.
Matches sourceQuote
Wiz reported account-recovery abuse of Cognito through InitiateAuth, ForgotPassword and ResendConfirmationCode, and Datadog saw ARTEX go further by registering an account, collecting tokens, and trading them for AWS credentials.
The cited source says the same thing.
The article says “Wiz reported account-recovery abuse through InitiateAuth, ForgotPassword and ResendConfirmationCode”
The source says “This activity was reflected in events like InitiateAuth, ForgotPassword, and ResendConfirmationCode”
Source cited by the article: wiz.io/blog/artex-in-the-wild-storm-0940-expands-targeting-of-it-and-software-vendors
No source givenCausal conclusion
In the Cognito case, all discovery calls failed because the identity pool's authenticated role did not grant the required permissions.
The article gives no link or citation for it.
The article says “In this case, all of them failed because the identity pool's authenticated role did not grant the required permissions”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN —
Recorded for context only, checked 10 Nov 2026, 05:47 UTC. It played no part in the ranking.