Detection queries Not classifiedCyberStrikeAI

Elastic CyberStrikeAI server reads AWS user data, secrets, and sends an SSM command

Elastic Security Labs (Samir Bousseaden, Bryan Porras Blanch, Terrance DeJesus; Nov 13, 2026) describes one CyberStrikeAI server, 43.240.29.11 (AS133199, SonderCloud Limited, Hong Kong), using stolen…

What happened

Elastic Security Labs (Samir Bousseaden, Bryan Porras Blanch, Terrance DeJesus; Nov 13, 2026) describes one CyberStrikeAI server, 43.240.29.11 (AS133199, SonderCloud Limited, Hong Kong), using stolen credentials for eight identities across four AWS accounts from Sep 30 to Oct 16, 2026. Five were IAM users and three were EC2 instance roles. The role sessions were named after instance IDs, and using them from an outside IP means the credentials were taken off the instances. Activity fell on four days and produced 78 alerts, all medium or low, which Elastic says only cohered once correlated by source IP. On Sep 30 the server called GetCallerIdentity on four IAM users across three accounts within 51 minutes, three of those calls in the same second, plus GetSessionToken. The same day app-role read Secrets Manager and then issued 56 DescribeInstanceAttribute userData calls in 141 milliseconds (about 2.5 ms per call), part of 57 user-data reads from one assumed-role session that day and 58 user-data alerts overall. On Oct 1 it revalidated credentials, read more secrets with app-role, and used nonprod-role for two GetSecretValue calls. On Oct 2 container-role called GetParameter with decryption on an SSM SecureString and SendCommand 29 seconds later. CloudTrail does not show the command text or whether it succeeded. After 14 quiet days, on Oct 16 the server called GetSessionToken for a previously unseen user in a fourth account and rechecked two earlier users. Internet scan data showed 43.240.29.11 serving a CyberStrikeAI page on port 8080, with a self-signed certificate (CN CyberStrikeAI, serial 3356730520974368630, issued 2026-09-15), one day before the first alert. 43.240.29.28 and 43.240.29.33 served the same page, FOFA fid, and certificate but were not in this AWS telemetry. Elastic says none of the three was still serving that interface as of November 2026. Six Elastic rules fired: AWS EC2 User Data Retrieval for EC2 Instance (58, medium), AWS STS GetCallerIdentity API Called for the First Time (11, medium), First Time Seen AWS Secret Value Accessed in Secrets Manager (4, medium), AWS STS GetSessionToken Usage (3, low), AWS SSM SendCommand Execution by Rare User (1, low), and AWS Systems Manager SecureString Parameter Request with Decryption Flag (1, medium). Elastic added two high-severity rules: AWS EC2 Bulk User Data Enumeration (more than 20 distinct instances in 10 minutes) and AWS STS GetCallerIdentity Bulk Account Enumeration (three or more distinct non-role identities from the same external IP and ASN in 10 minutes). Elastic, citing Will Thomas at Team Cymru, says 21 CyberStrikeAI IPs were counted in early 2026, aimed at Fortinet edge devices, and that this is the first Elastic case of the same tooling turned on AWS. The repository contains 24 SKILL.md files, including skills/unlimited-attack-scope/SKILL.md and skills/cloud-attack-methods/SKILL.md. Elastic cites https://github.com/Ed1s0nZ/CyberStrikeAI, which redirects to https://github.com/AIPentest/CyberStrikeAI. Link kaspersky-cyberstrikeai-schools-2026 and trendai-chinese-language-operators-used-cyberstrikeais-2026-10.

Elastic attributes the AWS calls to a CyberStrikeAI server from scan data and machine-speed CloudTrail. Elastic says it cannot prove an LLM agent made the decisions and does not know how the credentials were stolen.

Read the original sourceAdditional source: CyberStrikeAI

How it happened

Select a stage to explore its defenses
Detect this stage
Detect this stage
Detect this stage
Detect this stage
Select a stage · Drag to explore · + / − to zoom · Dashed edges are loopsSelect a stage · Arrows show reported connectionsReported sequence
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.

  1. 01 · GetCallerIdentity sweeps

    On Sep 30 the server validates four IAM users across three accounts, with three GetCallerIdentity calls in one second, and requests GetSessionToken.

    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 1
  2. 02 · 56 userData reads in 141 ms

    app-role calls DescribeInstanceAttribute for userData 56 times in 141 milliseconds after an earlier GetSecretValue.

    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
  3. 03 · Decrypt a parameter, then SendCommand

    On Oct 2 container-role reads an SSM SecureString and issues SendCommand 29 seconds later. The command text is not in the audit log.

    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 3
  4. 04 · Recheck after 14 days

    On Oct 16 the same server calls GetSessionToken in a fourth account and revalidates two earlier users.

    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 4

Why it matters

Reported entry point: Stolen AWS credentials for five IAM users and three EC2 instance roles, used from an external IP. Elastic does not know how the credentials were obtained. Reported impact: On Oct 16 the same server calls GetSessionToken in a fourth account and revalidates two earlier users; reported targets include Four AWS accounts. Account and identity names were replaced with aliases. No sector was named; applicability to your setup has not been assessed, so verify affected versions, permissions, and configuration in the original report.

Read the original report

What you can do

Protection & prevention

Rotate every identity that touched 43.240.29.11 and revoke active sessions. Replace instance profiles whose role credentials were used off-instance. Treat secrets in EC2 user data as exposed. Review SSM command history for the Oct 2 SendCommand. Restrict ec2:DescribeInstanceAttribute for userData. Correlate medium and low CloudTrail alerts by source IP across multi-day gaps.

Catalog defensive guidance based on the reported behavior. Confirm scope and current mitigations in the original source.

Review the original guidance Additional source 2
Investigate each phase

Detection queries

Draft query starters grouped by the attack stages where they apply.

Download stage pack

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.

01GetCallerIdentity sweepsCredential / session use outside baselineCustom schema · Draft

On Sep 30 the server validates four IAM users across three accounts, with three GetCallerIdentity calls in one second, and requests GetSessionToken.

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
Draft SigmaDownload 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
Draft KQLDownload 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 desc
SPL
Draft SPLDownload SPL
sourcetype="openattacks:audit"
EventType IN ("identity.login", "identity.token.use")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _time
Investigation steps
  1. Compare failures, successes and session reuse by account and source; inspect access to new resources.
  2. Check device registration, MFA and credential changes; do not equate travel anomalies with confirmed compromise.
0256 userData reads in 141 msUnexpected cloud / inference identity useCustom schema · Draft

app-role calls DescribeInstanceAttribute for userData 56 times in 141 milliseconds after an earlier GetSecretValue.

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
Draft SigmaDownload 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
Draft KQLDownload 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 desc
SPL
Draft SPLDownload SPL
sourcetype="openattacks:audit"
EventType IN ("cloud.credential.use", "cloud.role.change", "model.invoke")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _time
Investigation steps
  1. Pivot on key ID / principal, source network and user agent, then inspect role changes, token minting and service pivots.
  2. Join inference usage and billing anomalies to the same principal; verify whether the behavior was authorized.
03Decrypt a parameter, then SendCommandUnexpected cloud / inference identity useCustom schema · Draft

On Oct 2 container-role reads an SSM SecureString and issues SendCommand 29 seconds later. The command text is not in the audit log.

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
Draft SigmaDownload 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
Draft KQLDownload 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 desc
SPL
Draft SPLDownload SPL
sourcetype="openattacks:audit"
EventType IN ("cloud.credential.use", "cloud.role.change", "model.invoke")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _time
Investigation steps
  1. Pivot on key ID / principal, source network and user agent, then inspect role changes, token minting and service pivots.
  2. Join inference usage and billing anomalies to the same principal; verify whether the behavior was authorized.
04Recheck after 14 daysCredential / session use outside baselineCustom schema · Draft

On Oct 16 the same server calls GetSessionToken in a fourth account and revalidates two earlier users.

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
Draft SigmaDownload 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
Draft KQLDownload 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 desc
SPL
Draft SPLDownload SPL
sourcetype="openattacks:audit"
EventType IN ("identity.login", "identity.token.use")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _time
Investigation steps
  1. Compare failures, successes and session reuse by account and source; inspect access to new resources.
  2. Check device registration, MFA and credential changes; do not equate travel anomalies with confirmed compromise.
Technical detailsTooling, impact & MITRE ATLAS

Attack context

AI's role
AI as operator
Offensive frameworks
CyberStrikeAI
Additional role
AI credential theft
Initial access
Stolen AWS credentials for five IAM users and three EC2 instance roles, used from an external IP. Elastic does not know how the credentials were obtained.

Tooling as reported

AI products, models and artifacts

  • CyberStrikeAI (https://github.com/AIPentest/CyberStrikeAI), web interface on TCP 8080
  • 24 SKILL.md files in the repository, including unlimited-attack-scope and cloud-attack-methods

Other tooling

  • AWS APIs GetCallerIdentity, GetSessionToken, GetSecretValue, DescribeInstanceAttribute, GetParameter, SendCommand

Targets and reported impact

Targets / sectors
Four AWS accounts. Account and identity names were replaced with aliases. No sector was named.
Reported scale / exposure
One server, eight identities, four accounts, 78 alerts, four active days from Sep 30 to Oct 16, 2026. Fifty-six userData calls in 141 milliseconds. Sixty-five of 78 alerts fell on Sep 30.

No victim country is stated. Hong Kong and AS133199 are the server's hosting location and are not recorded as a target region.

Reported attribution

Unnamed operator. Elastic confirms the source IP served CyberStrikeAI. No country or motivation is stated. Hong Kong is the hosting location.

Structured attribution

Actor
Unnamed CyberStrikeAI operator
Country
Unknown
Motivation
unknown
Attributed by
Elastic Security Labs
Attribution confidence
medium

Detection rules

  • AWS EC2 User Data Retrieval for EC2 InstanceELASTICView rule

    AWS CloudTrail. DescribeInstanceAttribute for userData. Elastic says this rule fired 58 times.

  • AWS EC2 Bulk User Data EnumerationELASTICView rule

    AWS CloudTrail. Elastic added this high-severity rule for more than 20 distinct userData reads by one principal and source IP in 10 minutes. The intrusion had 56 calls in 141 milliseconds.

  • AWS STS GetCallerIdentity API Called for the First TimeELASTICView rule

    AWS CloudTrail. First GetCallerIdentity for an identity. Elastic says this rule fired 11 times.

  • AWS STS GetCallerIdentity Bulk Account EnumerationELASTICView rule

    AWS CloudTrail. Elastic added this high-severity rule for three or more distinct non-role identities calling GetCallerIdentity from the same external IP and ASN in 10 minutes.

  • First Time Seen AWS Secret Value Accessed in Secrets ManagerELASTICView rule

    AWS CloudTrail. First GetSecretValue. Elastic says this rule fired 4 times, including app-role and nonprod-role.

  • AWS Systems Manager SecureString Parameter Request with Decryption FlagELASTICView rule

    AWS CloudTrail. GetParameter with decryption. Matches the Oct 2 container-role read.

  • AWS SSM `SendCommand` Execution by Rare UserELASTICView rule

    AWS CloudTrail. Rare SendCommand. Matches the command issued 29 seconds after the SecureString read. The article's low-severity rule name is AWS SSM SendCommand Execution by Rare User.

  • GetSessionToken and off-instance role useGUIDANCE

    The article also names AWS STS GetSessionToken Usage (3 low alerts). The public rule titled AWS IAM API Calls via Temporary Session Tokens describes later IAM calls that use a temporary token, not the GetSessionToken API itself, so it is not cited. Also hunt instance-role credentials whose source IP is not the instance or the organization's NAT, and the certificate serial 3356730520974368630.

Activity timeline

First seen
2026-09-30
Last updated
2026-11-15

Updates

  • 2026-09-30 — Elastic Security Labs

    43.240.29.11 validates IAM users, reads Secrets Manager, and issues 56 userData calls in 141 milliseconds

  • 2026-10-02 — Elastic Security Labs

    container-role reads a decrypted SSM parameter and calls SendCommand 29 seconds later

  • 2026-10-16 — Elastic Security Labs

    The same server returns after 14 days and revalidates credentials, including a fourth account

  • 2026-11-13 — Elastic Security Labs

    Elastic publishes the CloudTrail write-up and two high-severity bulk enumeration rules

  • 2026-11-15 — OpenAttacks

    Tagged CyberStrikeAI. Country is Unknown because Elastic states no country.

Linked tools

Source defensive notes

Rotate every identity that touched 43.240.29.11 and revoke active sessions. Replace instance profiles whose role credentials were used off-instance. Treat secrets in EC2 user data as exposed. Review SSM command history for the Oct 2 SendCommand. Restrict ec2:DescribeInstanceAttribute for userData. Correlate medium and low CloudTrail alerts by source IP across multi-day gaps.

MITRE ATLAS

AI-specific catalog annotations based on the reported behavior; these are not MITRE case-study assignments.

AML.T0016.001Software Tools

Elastic ties the calls to a host that was serving the CyberStrikeAI console Source

AML.T0012Valid Accounts

Stolen IAM user and EC2 instance-role credentials were used from an external IP Source

AML.T0055Unsecured Credentials

The server read Secrets Manager values, EC2 user data, and a decrypted SSM SecureString Source

Indicators of compromise

domains

    ips

    • 43.240.29.11
    • 43.240.29.28
    • 43.240.29.33

    hashes

      urls

        Sources & research credit

        2 sources

        Research by Samir Bousseaden, Bryan Porras Blanch, Terrance DeJesus · Elastic Security Labs

        1. 56 AWS API calls in 141 milliseconds: Inside an AI-run intrusion www.elastic.co
        2. CyberStrikeAI github.com

        API sequence, alert counts, rule names, certificate serial 3356730520974368630, and the three IPs are from the Elastic article. Only 43.240.29.11 appeared in the AWS alerts. The 24 SKILL.md count was checked on the repository default branch on 2026-11-15. Elastic cites https://github.com/Ed1s0nZ/CyberStrikeAI; that URL redirected to https://github.com/AIPentest/CyberStrikeAI. Link kaspersky-cyberstrikeai-schools-2026 and trendai-chinese-language-operators-used-cyberstrikeais-2026-10.

        Record & downloads
        Source record name
        Elastic CyberStrikeAI server reads AWS user data, secrets, and sends an SSM command
        Entry ID
        elastic-cyberstrikeai-aws-cloudtrail-2026-11
        Catalog review
        November 15, 2026
        Category
        adversary-use-of-ai
        AI involvement confidence
        vendor-asserted