Datadog - ARTEX agents read anonymous S3, trawl CloudWatch, and self-sign-up to Cognito
Datadog Security Labs (Julie Agnes Sparks, Nov 9, 2026) saw ARTEX activity against several AWS environments in October 2026, focused on financial data. Every session opened with unauthenticated S3 reads…
What happened
Datadog Security Labs (Julie Agnes Sparks, Nov 9, 2026) saw ARTEX activity against several AWS environments in October 2026, focused on financial data. Every session opened with unauthenticated S3 reads (userIdentity.type AWSAccount, accountId anonymous, GetObject and ListObjects). The agent read front-end build manifests and runtime configs from S3-hosted web apps. Before each guessing burst it requested a placeholder key that should not exist (zzz_nonexistent_abc.txt, Notexist-xyz), the same habit Wiz described with /zzz-nonexistent-xyz123. With leaked long-term IAM keys, ARTEX ran repeated FilterLogEvents over CloudWatch, always with limit 1000, searching for crypto firms, hedge funds, and names like Fund, Invoice, Billing, and LLC. On October 20 a later session from 103.54.154.40 (zeofast.cn) searched for s3://, presigned, .pdf, .xlsx, .csv, rawData_, transformedData_, and the terms mongo, password, and AKIA. On October 26-27, from 154.64.252.77, ARTEX called Cognito SignUp with user agents such as Mozilla/5.0 ARTeX, iterated against a PreSignUp Lambda tenant-domain check (errors include artex-hqheizfk.invalid and custom:isAdmin), then ran InitiateAuth, RespondToAuthChallenge, GetUser, and GetTokensFromRefreshToken, swapped tokens for CognitoIdentityCredentials, and tried ListBuckets, ListSecrets, DescribeParameters, ListTopics, DescribeLogGroups, GetRestApis, DescribeRepositories, and ListFunctions20150331. Exposed consoles used titles ARTEX autonomous pentest console, ScopeWeaver Autonomous Penetration Testing Console, LUCK autonomous asset console, and Guanlan SEC pentest platform, with API routes including /tasks, /exploration, /llm/pool, /intercept, /mcp, /skills, and /agents, and a default blocklist of .gov, .gov.cn, .edu, and .edu.cn. 154.64.252.77 is also listed in the WorkOS bulletin. Hunting references named by Datadog: Stratus Red Team https://github.com/DataDog/stratus-red-team and TrailDiscover https://github.com/adanalvarez/TrailDiscover. ARTEX fork https://github.com/RuoJi6/ARTEX.
Datadog attributes October 2026 AWS financial-data hunting to ARTEX through user agents and IP addresses that also hosted ARTEX-family consoles
How it happened
Read the flow as text & sources
A catalog reconstruction of the supplied source account. Unknown steps remain explicit; an edge describes the reported relationship between steps.
- 01 · Anonymous S3 reads
Sessions start with unauthenticated GetObject and ListObjects, including placeholder keys zzz_nonexistent_abc.txt and Notexist-xyz.
Hunt: A service key or role is used from an unfamiliar origin, gains broader access or causes inference usage outside its established baseline.
Cloud control-plane logs alone may not include model prompts or inference calls. No endpoint policy is claimed to stop cloud-only key misuse.
Source for step 1 - 02 · CloudWatch log trawl
Leaked IAM keys run FilterLogEvents with limit 1000, searching for funds, invoices, file extensions, and AKIA.
Hunt: A service key or role is used from an unfamiliar origin, gains broader access or causes inference usage outside its established baseline.
Cloud control-plane logs alone may not include model prompts or inference calls. No endpoint policy is claimed to stop cloud-only key misuse.
Source for step 2 - 03 · Cognito self-sign-up
From 154.64.252.77 the agent calls SignUp, fights a PreSignUp Lambda, then exchanges tokens and lists AWS resources.
Hunt: Repeated credential attempts or a stolen session are followed by a successful login or resource access inconsistent with the owner.
Shared infrastructure and legitimate travel create noise. IoT, SharePoint and cloud identity require their own collectors and field mappings.
Source for step 3 - 04 · Cross-service enumeration
Cognito identity credentials are used for ListBuckets, ListSecrets, DescribeParameters, and related discovery calls.
Hunt: A service key or role is used from an unfamiliar origin, gains broader access or causes inference usage outside its established baseline.
Cloud control-plane logs alone may not include model prompts or inference calls. No endpoint policy is claimed to stop cloud-only key misuse.
Source for step 4
Why it matters
Reported entry point: Unauthenticated S3 reads, leaked long-term IAM keys, and public Cognito user pools that allow SignUp. Reported impact: Cognito identity credentials are used for ListBuckets, ListSecrets, DescribeParameters, and related discovery calls; reported targets include AWS environments holding financial data, including names consistent with funds, invoices, and billing; applicability to your setup has not been assessed, so verify affected versions, permissions, and configuration in the original report.
What you can do
Protection & prevention
Block public access on S3 buckets that hold front-end configs. Alert on anonymous GetObject and on placeholder keys such as zzz_nonexistent_abc.txt. Alert on high-volume FilterLogEvents with limit 1000. Disable self-sign-up on Cognito user pools that are not meant to be public, and review PreSignUp Lambda failures for artex and .invalid tenant domains. Tie the listed user agents and source IPs to CloudTrail.
Catalog defensive guidance based on the reported behavior. Confirm scope and current mitigations in the original source.
Detection queries
Draft query starters grouped by the attack stages where they apply.
Start with the logs you collect. Each hunt identifies its required visibility, field mapping and limits. Queries are catalog-authored drafts using reusable behavior profiles; test with known activity and your normal baseline before alerting.
01Anonymous S3 readsUnexpected cloud / inference identity useCustom schema · Draft
Sessions start with unauthenticated GetObject and ListObjects, including placeholder keys zzz_nonexistent_abc.txt and Notexist-xyz.
What to look for
A service key or role is used from an unfamiliar origin, gains broader access or causes inference usage outside its established baseline.
Visibility: Defender-side logs where collected
Required logs
- Cloud control-plane and identity audit
- AI-service invocation / diagnostic logs when enabled
- Usage, quotas, cost and key inventory
Coverage limit. Cloud control-plane logs alone may not include model prompts or inference calls. No endpoint policy is claimed to stop cloud-only key misuse.
Custom-schema candidates, not out-of-box detectors. Map your application / cloud / platform logs to EventType, Actor, Asset, Action, Target and CorrelationId. KQL uses a custom OpenAttacksAudit_CL table; SPL uses openattacks:audit. EventType values are proposed normalization names, not native vendor event names. Correlation and environment-specific alert logic remain to be built.
Sigma
title: Hunt - Unexpected cloud / inference identity use
id: afac2e65-c838-485b-a26f-7f175d422f61
status: experimental
description: A service key or role is used from an unfamiliar origin, gains
broader access or causes inference usage outside its established baseline.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: application
product: openattacks_audit
definition: Custom normalized audit schema; map EventType, Actor, Asset, Action,
Target and CorrelationId from the required source logs first.
detection:
selection:
EventType:
- cloud.credential.use
- cloud.role.change
- model.invoke
condition: selection
KQL
// SCHEMA TEMPLATE: create/map this custom table before use; not a built-in Sentinel table.
// OpenAttacksAudit_CL: TimeGenerated(datetime), EventType/Actor/Asset/Action/Target/CorrelationId(string).
// Selects candidates only. Apply the stage hypothesis and correlation steps before alerting.
OpenAttacksAudit_CL
| where TimeGenerated > ago(7d)
| where EventType in ("cloud.credential.use", "cloud.role.change", "model.invoke")
| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId
| order by TimeGenerated descSPL
sourcetype="openattacks:audit"
EventType IN ("cloud.credential.use", "cloud.role.change", "model.invoke")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _timeInvestigation steps
- Pivot on key ID / principal, source network and user agent, then inspect role changes, token minting and service pivots.
- Join inference usage and billing anomalies to the same principal; verify whether the behavior was authorized.
02CloudWatch log trawlUnexpected cloud / inference identity useCustom schema · Draft
Leaked IAM keys run FilterLogEvents with limit 1000, searching for funds, invoices, file extensions, and AKIA.
What to look for
A service key or role is used from an unfamiliar origin, gains broader access or causes inference usage outside its established baseline.
Visibility: Defender-side logs where collected
Required logs
- Cloud control-plane and identity audit
- AI-service invocation / diagnostic logs when enabled
- Usage, quotas, cost and key inventory
Coverage limit. Cloud control-plane logs alone may not include model prompts or inference calls. No endpoint policy is claimed to stop cloud-only key misuse.
Custom-schema candidates, not out-of-box detectors. Map your application / cloud / platform logs to EventType, Actor, Asset, Action, Target and CorrelationId. KQL uses a custom OpenAttacksAudit_CL table; SPL uses openattacks:audit. EventType values are proposed normalization names, not native vendor event names. Correlation and environment-specific alert logic remain to be built.
Sigma
title: Hunt - Unexpected cloud / inference identity use
id: afac2e65-c838-485b-a26f-7f175d422f61
status: experimental
description: A service key or role is used from an unfamiliar origin, gains
broader access or causes inference usage outside its established baseline.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: application
product: openattacks_audit
definition: Custom normalized audit schema; map EventType, Actor, Asset, Action,
Target and CorrelationId from the required source logs first.
detection:
selection:
EventType:
- cloud.credential.use
- cloud.role.change
- model.invoke
condition: selection
KQL
// SCHEMA TEMPLATE: create/map this custom table before use; not a built-in Sentinel table.
// OpenAttacksAudit_CL: TimeGenerated(datetime), EventType/Actor/Asset/Action/Target/CorrelationId(string).
// Selects candidates only. Apply the stage hypothesis and correlation steps before alerting.
OpenAttacksAudit_CL
| where TimeGenerated > ago(7d)
| where EventType in ("cloud.credential.use", "cloud.role.change", "model.invoke")
| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId
| order by TimeGenerated descSPL
sourcetype="openattacks:audit"
EventType IN ("cloud.credential.use", "cloud.role.change", "model.invoke")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _timeInvestigation steps
- Pivot on key ID / principal, source network and user agent, then inspect role changes, token minting and service pivots.
- Join inference usage and billing anomalies to the same principal; verify whether the behavior was authorized.
03Cognito self-sign-upCredential / session use outside baselineCustom schema · Draft
From 154.64.252.77 the agent calls SignUp, fights a PreSignUp Lambda, then exchanges tokens and lists AWS resources.
What to look for
Repeated credential attempts or a stolen session are followed by a successful login or resource access inconsistent with the owner.
Visibility: Defender-side logs where collected
Required logs
- Identity / service authentication logs
- Device, source-IP and session context
- Resource access and token issuance audit
Coverage limit. Shared infrastructure and legitimate travel create noise. IoT, SharePoint and cloud identity require their own collectors and field mappings.
Custom-schema candidates, not out-of-box detectors. Map your application / cloud / platform logs to EventType, Actor, Asset, Action, Target and CorrelationId. KQL uses a custom OpenAttacksAudit_CL table; SPL uses openattacks:audit. EventType values are proposed normalization names, not native vendor event names. Correlation and environment-specific alert logic remain to be built.
Sigma
title: Hunt - Credential / session use outside baseline
id: 7d73d919-e785-4d40-ab0b-f12949adfaf5
status: experimental
description: Repeated credential attempts or a stolen session are followed by a
successful login or resource access inconsistent with the owner.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: application
product: openattacks_audit
definition: Custom normalized audit schema; map EventType, Actor, Asset, Action,
Target and CorrelationId from the required source logs first.
detection:
selection:
EventType:
- identity.login
- identity.token.use
condition: selection
KQL
// SCHEMA TEMPLATE: create/map this custom table before use; not a built-in Sentinel table.
// OpenAttacksAudit_CL: TimeGenerated(datetime), EventType/Actor/Asset/Action/Target/CorrelationId(string).
// Selects candidates only. Apply the stage hypothesis and correlation steps before alerting.
OpenAttacksAudit_CL
| where TimeGenerated > ago(7d)
| where EventType in ("identity.login", "identity.token.use")
| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId
| order by TimeGenerated descSPL
sourcetype="openattacks:audit"
EventType IN ("identity.login", "identity.token.use")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _timeInvestigation steps
- Compare failures, successes and session reuse by account and source; inspect access to new resources.
- Check device registration, MFA and credential changes; do not equate travel anomalies with confirmed compromise.
04Cross-service enumerationUnexpected cloud / inference identity useCustom schema · Draft
Cognito identity credentials are used for ListBuckets, ListSecrets, DescribeParameters, and related discovery calls.
What to look for
A service key or role is used from an unfamiliar origin, gains broader access or causes inference usage outside its established baseline.
Visibility: Defender-side logs where collected
Required logs
- Cloud control-plane and identity audit
- AI-service invocation / diagnostic logs when enabled
- Usage, quotas, cost and key inventory
Coverage limit. Cloud control-plane logs alone may not include model prompts or inference calls. No endpoint policy is claimed to stop cloud-only key misuse.
Custom-schema candidates, not out-of-box detectors. Map your application / cloud / platform logs to EventType, Actor, Asset, Action, Target and CorrelationId. KQL uses a custom OpenAttacksAudit_CL table; SPL uses openattacks:audit. EventType values are proposed normalization names, not native vendor event names. Correlation and environment-specific alert logic remain to be built.
Sigma
title: Hunt - Unexpected cloud / inference identity use
id: afac2e65-c838-485b-a26f-7f175d422f61
status: experimental
description: A service key or role is used from an unfamiliar origin, gains
broader access or causes inference usage outside its established baseline.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: application
product: openattacks_audit
definition: Custom normalized audit schema; map EventType, Actor, Asset, Action,
Target and CorrelationId from the required source logs first.
detection:
selection:
EventType:
- cloud.credential.use
- cloud.role.change
- model.invoke
condition: selection
KQL
// SCHEMA TEMPLATE: create/map this custom table before use; not a built-in Sentinel table.
// OpenAttacksAudit_CL: TimeGenerated(datetime), EventType/Actor/Asset/Action/Target/CorrelationId(string).
// Selects candidates only. Apply the stage hypothesis and correlation steps before alerting.
OpenAttacksAudit_CL
| where TimeGenerated > ago(7d)
| where EventType in ("cloud.credential.use", "cloud.role.change", "model.invoke")
| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId
| order by TimeGenerated descSPL
sourcetype="openattacks:audit"
EventType IN ("cloud.credential.use", "cloud.role.change", "model.invoke")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _timeInvestigation steps
- Pivot on key ID / principal, source network and user agent, then inspect role changes, token minting and service pivots.
- Join inference usage and billing anomalies to the same principal; verify whether the behavior was authorized.
Technical detailsTooling, impact & MITRE ATLAS
Attack context
- AI's role
- AI as operator
- Offensive frameworks
- ARTEX
- Additional role
- AI credential theft
- Initial access
- Unauthenticated S3 reads, leaked long-term IAM keys, and public Cognito user pools that allow SignUp
Tooling as reported
AI products, models and artifacts
- ARTEX autonomous pentest console (https://github.com/RuoJi6/ARTEX)Community-maintained fork; the original repository is unavailable.
- Related console titles ScopeWeaver, LUCK, and Guanlan SEC
Other tooling
- AWS CloudTrail APIs: FilterLogEvents, Cognito SignUp, InitiateAuth, ListBuckets, ListSecrets
- Stratus Red Team (https://github.com/DataDog/stratus-red-team)
- TrailDiscover (https://github.com/adanalvarez/TrailDiscover)
Targets and reported impact
- Targets / sectors
- AWS environments holding financial data, including names consistent with funds, invoices, and billing
- Reported scale / exposure
- Several AWS environments in October 2026. Hundreds of exposed consoles under several titles.
- Target geography
- Multiple regions
Reported attribution
Unattributed ARTEX operators. Consoles are mostly in Mandarin and hosted with providers including locations in Singapore and Hong Kong. Datadog attributes the activity to ARTEX usage.
Structured attribution
- Actor
- Unattributed ARTEX operators
- Country
- Unknown
- Motivation
- financially-motivated
- Attributed by
- Datadog Security Labs
- Attribution confidence
- medium
Detection rules
- AWS S3 Unauthenticated Bucket Access by Rare SourceELASTICView rule
AWS CloudTrail. Matches anonymous GetObject and ListObjects, which opened every Datadog session (userIdentity accountId anonymous).
- AWS Repeated CloudWatch Logs Read OperationsSPLUNKView rule
AWS CloudTrail. Matches high-volume FilterLogEvents, GetLogEvents, and related reads. Datadog saw FilterLogEvents with limit 1000.
- AWS S3 Bucket Enumeration or Brute ForceELASTICView rule
AWS CloudTrail. High-rate S3 discovery. Use alongside the placeholder object names zzz_nonexistent_abc.txt and Notexist-xyz, which this rule does not name.
- Cognito SignUp and ARTEX user agentsGUIDANCE
The indexed rules do not alert on Cognito SignUp or PreSignUp Lambda errors. Hunt CloudTrail for SignUp, InitiateAuth, RespondToAuthChallenge, and GetTokensFromRefreshToken from 154.64.252.77, and for user agents artex-readonly/1.0, artex-pentest/1.0, artex-audit/1.0, Mozilla/5.0 ARTeX, artex-spawn/1, artex-verify/1.0, ARTeX-authorized-pentest, artex-i21861-canary, and ARTEX-worker/1.0. The Cognito unauthenticated-identity-pool rule does not match this user-pool SignUp path, so it is not cited.
Activity timeline
- First seen
- 2026-10-01
- Last updated
- 2026-11-09
Updates
- 2026-10-20 — Datadog Security Labs
Long-term IAM key from 103.54.154.40 (zeofast.cn) widens CloudWatch searches to s3://, presigned URLs, office files, and AKIA
- 2026-10-26 — Datadog Security Labs
154.64.252.77 runs Cognito SignUp with ARTEX user agents and iterates against a PreSignUp tenant-domain check through Oct 27
- 2026-11-09 — Datadog Security Labs
Julie Agnes Sparks publishes the AWS control-plane write-up, including console titles, user agents, and the anonymous S3 canary keys
Source defensive notes
Block public access on S3 buckets that hold front-end configs. Alert on anonymous GetObject and on placeholder keys such as zzz_nonexistent_abc.txt. Alert on high-volume FilterLogEvents with limit 1000. Disable self-sign-up on Cognito user pools that are not meant to be public, and review PreSignUp Lambda failures for artex and .invalid tenant domains. Tie the listed user agents and source IPs to CloudTrail.
MITRE ATLAS
AI-specific catalog annotations based on the reported behavior; these are not MITRE case-study assignments.
Leaked long-term IAM keys were used for CloudWatch and later API calls Source
ARTEX called Cognito SignUp and iterated against a PreSignUp tenant check Source
FilterLogEvents searches looked for AKIA keys, passwords, and financial file names Source
The activity is tied to the ARTEX agent framework and exposed operator consoles Source
Indicators of compromise
domains
zeofast.cnartex-hqheizfk.invalid
ips
169.128.55.214154.64.252.77154.36.136.197154.36.136.23102.216.154.10282.158.88.23388.229.22.232103.54.154.40103.54.154.3245.145.228.25
hashes
urls
Sources & research credit
1 sourceResearch by Julie Agnes Sparks · Datadog Security Labs
IPs, user agents, API names, placeholder keys, and console titles are from the Datadog article. GetSecretValue is not claimed here; the Cognito path tried ListSecrets and other List/Describe calls. 154.64.252.77 also appears in the WorkOS bulletin covered by workos-artex-unintended-agent-escape-2026-10. Link microsoft-artex-github-secrets-keyvault-2026-11, unit42-artex-api-recon-2026-10, crowdstrike-artex-sk-finance-2026-10, and the Check Point, S-RM, and Storm-3358 ARTEX entries.
Record & downloads
- Source record name
- Datadog - ARTEX agents read anonymous S3, trawl CloudWatch, and self-sign-up to Cognito
- Entry ID
- datadog-artex-aws-cognito-2026-11
- Catalog review
- November 12, 2026
- Category
- adversary-use-of-ai
- AI involvement confidence
- vendor-asserted