Financially motivated intrusion / cloudMediumTLP:CLEAR

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

  1. Run the hunt.
  2. Check for the listed behaviours.
  3. Alert on the ten operator IP addresses in CloudTrail, VPC flow….

Indicators 10

ValueTypeActionCopy
169[.]128[.]55[.]214IPv4alert
154[.]64[.]252[.]77IPv4alert
154[.]36[.]136[.]197IPv4alert
154[.]36[.]136[.]23IPv4alert
102[.]216[.]154[.]102IPv4alert
82[.]158[.]88[.]233IPv4alert
88[.]229[.]22[.]232IPv4alert
103[.]54[.]154[.]40IPv4alert
103[.]54[.]154[.]32IPv4alert
45[.]145[.]228[.]25IPv4alert

Sources Datadog Security Labs · Sophos

More detail
Note Single-source network indicators (Datadog). Alert and hunt only; do not block entire ASNs or shared hosting ranges. Distinct from Storm-3358.

What to do

  1. Alert on the ten operator IP addresses in CloudTrail, VPC flow, WAF and perimeter logs; do not block whole ASNs.
  2. 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.
  3. 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).
  4. 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.

  1. 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

  2. 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

  3. 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

  4. 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.

Downloads

View folder in repository

MITRE ATT&CK7

Open in the live dashboard Get the blocklist