ARTEX AWS data hunt
ARTEX AWS Financial-Data Hunting
- Published
- 9 November 2026
- Added
- 12 November 2026, 09:50 UK
- Last updated
- 12 November 2026
Nothing to block10 to hunt4 behaviours to hunt
Hunt3 platforms
Run the hunt before you block, to find past activity. The same hunt is published for each platform. Preview and copy the queries in the dashboard.
- Defender XDRKQLDefender portal > Hunting > Advanced hunting. Paste and run over 30 days.Download hunt.kql
- SplunkSPLSearch & Reporting, last 30 days or more. Reads the CIM data models.Download hunt.spl
- Google SecOpsYARA-L 2.0Rules Editor. Paste, Retrohunt over 30 days, then turn on live mode.Download hunt.yaral
These queries can return false positives. Know your environment and confirm a hit before acting.
Summary
ARTEX operators in AWS hunting financial logs and Cognito, with hunt-only operator IPs. Datadog Security Labs documented ARTEX operators in the Storm-0940 cluster hunting financial data in AWS environments.
Do now
- Run the hunt.
- Check for the listed behaviours.
- Alert on the ten operator IP addresses in CloudTrail, VPC flow….
Indicators 10
| Value | Type | Action | Copy |
|---|---|---|---|
169[.]128[.]55[.]214 | IPv4 | alert | |
154[.]64[.]252[.]77 | IPv4 | alert | |
154[.]36[.]136[.]197 | IPv4 | alert | |
154[.]36[.]136[.]23 | IPv4 | alert | |
102[.]216[.]154[.]102 | IPv4 | alert | |
82[.]158[.]88[.]233 | IPv4 | alert | |
88[.]229[.]22[.]232 | IPv4 | alert | |
103[.]54[.]154[.]40 | IPv4 | alert | |
103[.]54[.]154[.]32 | IPv4 | alert | |
45[.]145[.]228[.]25 | IPv4 | alert |
Sources Datadog Security Labs · Sophos
More detail
What to do
- Alert on the ten operator IP addresses in CloudTrail, VPC flow, WAF and perimeter logs; do not block whole ASNs.
- Hunt CloudTrail for FilterLogEvents calls whose filter patterns include financial terms (card, payment, invoice, transaction) and a limit of 1,000, and for anonymous S3 access followed by Cognito SignUp or InitiateAuth.
- Hunt proxy, WAF and application logs for ARTEX user agents (artex-readonly/1.0, artex-pentest/1.0, artex-audit/1.0, artex-spawn/1, artex-verify/1.0, ARTEX-worker/1.0, ARTeX-authorized-pentest, Mozilla/5.0 ARTeX, artex-i21861-canary).
- Look for canary GetObject keys such as zzz_nonexistent_abc.txt immediately before real object reads, and review IAM and Cognito changes in the same window.
Behaviours to hunt 4
Behaviours are leads, not confirmed indicators, and can match legitimate activity. Compare any hit against your own baseline and environment before acting.
hunt CloudWatch FilterLogEvents for financial terms
Look forCloudWatch FilterLogEvents calls whose filter patterns include financial terms and a limit of 1,000
Why it mattersDatadog saw ARTEX agents search CloudWatch logs for card, payment and invoice terms with FilterLogEvents and a 1,000-event limit. Datadog Security Labs
Log sourceAWS CloudTrail
QueriesKQL · SPL
hunt Anonymous S3 then Cognito SignUp or InitiateAuth
Look forAnonymous S3 access followed by Cognito SignUp or InitiateAuth from the same identity or address
Why it mattersDatadog documented ARTEX operators probing S3 anonymously, then creating or authenticating Cognito users to reach further data. Datadog Security Labs
Log sourceAWS CloudTrail
QueriesKQL · SPL
alert ARTEX user agents in AWS or proxy logs
Look forHTTP or AWS API requests with ARTEX user agents such as artex-readonly/1.0, ARTeX-authorized-pentest or ARTEX-worker/1.0
Why it mattersDatadog published distinctive ARTEX user agents used during AWS financial-data hunting, including artex-readonly/1.0, artex-pentest/1.0, artex-audit/1.0, artex-spawn/1, artex-verify/1.0, ARTEX-worker/1.0, Mozilla/5.0 ARTeX, ARTeX-authorized-pentest and artex-i21861-canary. Datadog Security Labs
Log sourceAWS CloudTrail, WAF, proxy and application logs
QueriesKQL · SPL · YARA-L
hunt ARTEX canary S3 object keys
Look forS3 GetObject or HeadObject for canary keys such as zzz_nonexistent_abc.txt or Notexist-xyz immediately before real object reads
Why it mattersDatadog observed ARTEX agents probing non-existent canary object keys before reading real financial data. Datadog Security Labs
Log sourceAWS CloudTrail
QueriesKQL · SPL
Affected countries and sectors
- Targets
- Global
- Sectors
- Financial services
Background
Datadog Security Labs documented ARTEX operators in the Storm-0940 cluster hunting financial data in AWS environments. The agents call CloudWatch FilterLogEvents for card, payment and invoice terms with a 1,000-event limit, probe S3 anonymously then move into Amazon Cognito (SignUp and InitiateAuth), and send distinctive ARTEX user agents such as artex-readonly/1.0 and ARTeX-authorized-pentest. Ten operator IP addresses were published by Datadog only, so they are medium confidence and for hunt and alert only; do not block whole hosting ASNs or unrelated hosts on the same networks. This activity is distinct from the Cambodia-based Storm-3358 web-RAT campaign, which has its own entry. Sophos X-Ops has also described ARTEX tradecraft against financial organisations, without publishing these AWS addresses.