← All hunts high TLP:CLEAR Part 2 of 2

Autonomous AI Retail Intrusions and Cloud Fraud

An adversary has compromised a retail employee account via social engineering and is now using an autonomous AI agent to conduct high-velocity reconnaissance and fraudulent gift card issuance within a sub-10-hour window.

Based on research by Unit 42 2026-10-29 11 steps · 3 queries T1041 T1059 T1110.004 T1486 T1566

Brief

Why This Hunt Matters

Retailers face an increased threat during peak seasons when transaction volumes rise and code freezes are in effect. A recent report by Unit 42, Unwrapping Retail Peak Season Cyber Threats, highlights how groups like Storm-0539 use social engineering and cloud-native techniques to conduct fraud. This hunt builds on those findings by focusing on the use of autonomous AI agents that compress the time from initial access to impact into a window of less than ten hours.

How the Hunt Flows

The first phase identifies suspicious authentication leads within identity provider logs. The query filters for logins involving known proxy services, accounts flagged as at-risk by the provider, or sessions exhibiting negative behavioral signals. This provides a focused list of users and hosts to investigate without sifting through the noise of legitimate seasonal employee logins.

Once an analyst establishes a credible identity lead, the hunt branches into two parallel investigations. On the endpoint, we search for the execution of autonomous penetration testing agents or AI harnesses using specific keywords observed in retail intrusions. This looks for the process itself, identifying the tool the adversary uses for automation.

Simultaneously, the hunt examines cloud audit logs for high-velocity API operations. We look for a specific pattern: a single user performing more than ten sensitive operations—such as creating access keys or issuing gift cards—within a sub-10-hour window. This temporal compression indicates automated activity rather than manual administrative tasks.

The final phase correlates these findings. An analyst or agent confirms if the suspicious login, the AI agent process, and the cloud API burst involve the same account or host. This correlation confirms an autonomous intrusion and triggers session revocation and fraud remediation.

What the Hunt Cannot See

Defenders face several blind spots with this design. If an adversary uses smishing on an employee's personal device before the enterprise login, we lack the telemetry to see that initial hook. We also cannot see the specific prompts given to an AI agent if it communicates with an LLM via encrypted channels. Finally, if the intrusion occurred outside of your cloud provider's audit retention window, the evidence of gift card issuance is lost.

How to Run the Hunt

This hunt is provided as an open hunt.md playbook. This format allows you to import the logic directly into Huntbase or any other hunt.md-aware runtime. It uses a gated design to ensure that expensive endpoint and cloud queries only run when a credible identity lead is found. To start, configure your lookback window and review the default list of AI-related keywords and fraud-specific API operations.

In this series

Steps

  1. Identify suspicious authentication leads

    Query · scoping

    Find employee logins that exhibit markers of compromise, such as proxy usage or negative risk behaviors, as a lead for an identity-based intrusion.

    reads hb_auth_signinsql
    SELECT actor_user_name, src_endpoint_ip, src_location_country, is_proxy, risk_state, debug_behaviors, device_hostname, time FROM hb_auth_signin WHERE (is_proxy = 'true' OR risk_state IN ('atRisk', 'confirmedCompromised') OR LOWER(debug_behaviors) LIKE '%negative%') AND time >= datetime('now', '-{{lookback_days}} days')

    What a hit looks like. A list of users and hosts associated with atypical or high-risk authentication. Silence suggests no such logins were logged by the provider.

  2. Evaluate logon leads

    Agent triage

    Assess whether the suspicious logins justify a deeper investigation into subsequent attacker actions.

  3. Gate: Proceed to investigation?

    Decision

    Only open the expensive investigation queries if the initial identity lead is credible.

  4. Search for autonomous agent execution

    Query · detection candidate

    Detect the execution of autonomous penetration testing agents or AI-harness processes on the identified hosts.

    reads hb_process_activitysql
    SELECT device_hostname, process_name, process_cmd_line, user_name, time FROM hb_process_activity WHERE ('{{scope_hosts}}' = '' OR instr(',' || '{{scope_hosts}}' || ',', ',' || device_hostname || ',') > 0) AND (instr(',' || '{{agent_keywords}}' || ',', ',' || LOWER(process_name) || ',') > 0 OR instr(',' || '{{agent_keywords}}' || ',', ',' || LOWER(process_original_file_name) || ',') > 0) AND time >= datetime('now', '-{{lookback_days}} days')

    What a hit looks like. Process events where the image name or original file name matches an AI agent keyword. Silence suggests no such processes were active on the scoped hosts.

  5. Detect high-velocity cloud API bursts

    Query · baseline

    Identify the compressed timeline of an autonomous intrusion by looking for actors performing dozens of sensitive operations in a sub-10-hour window.

    reads hb_cloud_api_activitysql
    SELECT actor_user_name, COUNT(*) as op_count, MIN(time) as first_seen, MAX(time) as last_seen FROM hb_cloud_api_activity WHERE (instr(',' || '{{fraud_api_ops}}' || ',', ',' || api_operation || ',') > 0 OR api_category = 'GiftCardManagement') AND time >= datetime('now', '-{{lookback_days}} days') GROUP BY actor_user_name HAVING op_count > 10 AND (julianday(last_seen) - julianday(first_seen)) * 24 <= 10

    What a hit looks like. A single user account performing high volumes of sensitive API operations in a very short timeframe. Silence proves no such high-velocity bursts occurred in the audit log.

  6. Correlate intrusion evidence

    Agent triage

    Correlate the suspicious logins, AI agent execution, and rapid cloud activity to confirm an autonomous intrusion.

  7. Route on verdict

    Decision

    Select the response path based on the confirmed threat.

  8. Revoke compromised sessions

    Response action

    Immediately halt the intrusion by revoking the identity context.

  9. Remediate fraud impact

    Analyst task

    Determine the financial and data impact of the intrusion.

  10. Close out

    Analyst task

    Document findings and negative results.

Coverage

Scenario coverage

StageCoveredHow, or why not
Employee Phishing and Smishing
T1566
Yes suspicious-logon-leads
Autonomous AI Agent Activity
T1059
Yes autonomous-agent-processes, high-velocity-api-activity
Cloud Gift Card Fraud and Data Theft
T1486 · T1041
Yes high-velocity-api-activity
Adobe Commerce XXE Exploitation
T1190
Out of scope Belongs to another part of the 'Unwrapping Retail Peak Season Cyber Threats' series.
Automated Credential Stuffing
T1110.004
Out of scope Belongs to another part of the 'Unwrapping Retail Peak Season Cyber Threats' series.
Digital Skimming and Backdoor Installation
T1505.003 · T1195
Out of scope Belongs to another part of the 'Unwrapping Retail Peak Season Cyber Threats' series.

Blind spots

  • Needs detailed IdP risk logs and behavioral context. A smishing attack may look like a legitimate remote login if risk signals from the IdP are delayed or incomplete. It would answer whether a smishing attempt occurred on a personal mobile device before the enterprise login.
  • Needs long-term cloud data event auditing. If the 10-hour intrusion window occurred just outside the standard retention period, the evidence of gift card issuance or data theft is lost. It would answer whether sensitive data was exfiltrated before the lookback window.
  • Needs local LLM interaction logging or HTTPS decryption. Defenders can see the agent process but not the exact objective it was given if interactions occur over encrypted channels to remote model APIs. It would answer what specific instructions were given to the autonomous agent.

Parameters & data

Parameters

ParameterTypeDefaultWhat it is
agent_keywordslist[string]cairn, harness, claude, gpt-4, autonomousKeywords associated with autonomous agents or AI harnesses identified in retail intrusions.
fraud_api_opslist[string]CreateAccessKey, PutUserPolicy, AttachUserPolicy, UpdateAccessKey, CreateUser, IssueGiftCardCloud API operations linked to Storm-0539 fraud and persistence.
lookback_daysnumber14Days of history to examine.
scope_hostslist[host]—Hostnames identified as suspicious in the lead step to focus the endpoint investigation.

Telemetry

SourceCategoryTelemetry
Endpoint telemetry (hb_ surfaces)endpointendpoint
Identity / sign-in telemetryidentityidentity

Source

Download hunt.md Definition (JSON) An open hunt.md file; it runs anywhere that reads the format.
---
analysis: "A rule might alert on a single proxy login, but this hunt correlates the\
  \ identity lead with sub-10-hour cloud velocity and AI agent execution patterns\u2014\
  the 'compressed timeline' that signifies an autonomous threat."
blind_spots:
- id: limited-idp-telemetry
  question: whether a smishing attempt occurred on a personal mobile device before
    the enterprise login
  requires: detailed IdP risk logs and behavioral context
  risk: A smishing attack may look like a legitimate remote login if risk signals
    from the IdP are delayed or incomplete.
  stage: initial-access-employee-social-engineering
- id: insufficient-cloud-audit-retention
  question: whether sensitive data was exfiltrated before the lookback window
  requires: long-term cloud data event auditing
  risk: If the 10-hour intrusion window occurred just outside the standard retention
    period, the evidence of gift card issuance or data theft is lost.
  stage: impact-cloud-fraud-exfiltration
- id: obfuscated-ai-prompts
  question: what specific instructions were given to the autonomous agent
  requires: local LLM interaction logging or HTTPS decryption
  risk: Defenders can see the agent process but not the exact objective it was given
    if interactions occur over encrypted channels to remote model APIs.
  stage: execution-autonomous-agent
coverage:
- stage: initial-access-employee-social-engineering
  status: covered
  steps:
  - suspicious-logon-leads
- stage: execution-autonomous-agent
  status: covered
  steps:
  - autonomous-agent-processes
  - high-velocity-api-activity
- stage: impact-cloud-fraud-exfiltration
  status: covered
  steps:
  - high-velocity-api-activity
- reason: Belongs to another part of the 'Unwrapping Retail Peak Season Cyber Threats'
    series.
  stage: initial-access-commerce-exploit
  status: out_of_scope
- reason: Belongs to another part of the 'Unwrapping Retail Peak Season Cyber Threats'
    series.
  stage: credential-access-api-stuffing
  status: out_of_scope
- reason: Belongs to another part of the 'Unwrapping Retail Peak Season Cyber Threats'
    series.
  stage: persistence-digital-skimmer-injection
  status: out_of_scope
guardrails:
  claims: no_unsupported
  evidence: citation_required
  missing_data: not_benign
  telemetry: untrusted
hunt:
  applicability: campaign-specific
  handoff: promote-to-detection
  justification: Peak retail season involves high transaction volumes and code freezes
    that attackers exploit. Autonomous AI agents can compress intrusion timelines
    to hours, making it impossible for standard manual reviews to intervene before
    impact.
  methodology: model-assisted
  trigger: intel-report
hypothesis: An adversary has compromised a retail employee account via social engineering
  and is now using an autonomous AI agent to conduct high-velocity reconnaissance
  and fraudulent gift card issuance within a sub-10-hour window.
labels:
- hunt
- attack.t1566
- attack.t1059
- attack.t1041
- attack.t1486
- attack.t1110.004
- credential access
- execution
- impact
- initial access
- persistence
name: Autonomous AI Retail Intrusions and Cloud Fraud
parameters:
  agent_keywords:
    default:
    - cairn
    - harness
    - claude
    - gpt-4
    - autonomous
    description: Keywords associated with autonomous agents or AI harnesses identified
      in retail intrusions.
    from:
      kind: article
      observed: '2026-10-28'
      ref: unit42-retail-threats-2026
    type: list[string]
  fraud_api_ops:
    default:
    - CreateAccessKey
    - PutUserPolicy
    - AttachUserPolicy
    - UpdateAccessKey
    - CreateUser
    - IssueGiftCard
    description: Cloud API operations linked to Storm-0539 fraud and persistence.
    from:
      kind: article
      observed: '2026-10-28'
      ref: unit42-retail-threats-2026
    type: list[string]
  lookback_days:
    default: '14'
    description: Days of history to examine.
    type: number
  scope_hosts:
    default: []
    description: Hostnames identified as suspicious in the lead step to focus the
      endpoint investigation.
    type: list[host]
provenance:
  authors:
  - name: Huntbase hunt generation
    org: huntbase.io
  generated:
    by: huntbase-hunt-generation
    from: https://unit42.paloaltonetworks.com/unwrapping-retail-cyber-threats/
    gates:
    - dry-run
    - lint
    - critic
    model: hb_google/gemini-3-flash-preview
rationale: Focus on administrative accounts and retail employees with access to gift
  card management or e-commerce control panels.
references:
- name: "Unit 42 \u2014 Unwrapping Retail Peak Season Cyber Threats"
  url: https://unit42.paloaltonetworks.com/unwrapping-retail-cyber-threats/
related:
- hunt: retail-commerce-exploit-skimmer
  reason: Digital skimming and server-side e-commerce exploits are handled in a separate
    hunt focused on web-facing infrastructure.
  relation: out-of-scope-alternative
- hunt: ecommerce-edge-exploitation-api-abuse
  relation: follows
scenario:
  stages:
  - name: Adobe Commerce XXE Exploitation
    observables:
    - CVE-2024-34102
    - CosmicSting
    - Adobe Commerce
    - XML External Entity (XXE) crafted documents
    - unpatched e-commerce servers
    slug: initial-access-commerce-exploit
    tactic: initial-access
    techniques:
    - T1190
  - name: Employee Phishing and Smishing
    observables:
    - Storm-0539
    - phishing messages
    - smishing messages
    - social engineering of retail employees
    slug: initial-access-employee-social-engineering
    tactic: initial-access
    techniques:
    - T1566
  - name: Automated Credential Stuffing
    observables:
    - automated scripts targeting mobile app APIs
    - web login API traffic spikes
    - stolen credential databases
    - login failures followed by success
    slug: credential-access-api-stuffing
    tactic: credential-access
    techniques:
    - T1110.004
  - name: Digital Skimming and Backdoor Installation
    observables:
    - JavaScript payment skimming scripts
    - checkout flow modification
    - persistent server backdoors
    - unauthorized client-side script manipulation
    slug: persistence-digital-skimmer-injection
    tactic: persistence
    techniques:
    - T1505.003
    - T1195
  - name: Autonomous AI Agent Activity
    observables:
    - Cairn autonomous penetration testing agent
    - Bling Libra AI reconnaissance
    - Claude AI accelerated exfiltration
    - autonomous penetration testing harnesses
    slug: execution-autonomous-agent
    tactic: execution
    techniques:
    - T1059
  - name: Cloud Gift Card Fraud and Data Theft
    observables:
    - unauthorized gift card issuance
    - loyalty account balance draining
    - Storm-0539 cloud infrastructure exploitation
    - exfiltration of payment card records
    - ALPHV inventory replenishment disruption
    slug: impact-cloud-fraud-exfiltration
    tactic: impact
    techniques:
    - T1486
    - T1041
  summary: Retailers during peak shopping season face a diverse threat landscape including
    digital skimming via CVE-2024-34102, AI-accelerated autonomous intrusions, and
    cloud-based gift card fraud following employee phishing. These campaigns prioritize
    operational disruption through ransomware or direct financial gain via credential
    stuffing and payment record exfiltration.
series:
  index: 2
  slug: unwrapping-retail-peak-season-cyber-threats
  title: Unwrapping Retail Peak Season Cyber Threats
  total: 2
severity: high
targets:
  analyst:
    name: Tier-2 analyst
    role: analyst
  endpoint:
    category: endpoint
    name: Endpoint telemetry (hb_ surfaces)
    telemetry:
    - endpoint
  hunter:
    agent: true
    name: Hunt agent
  identity:
    category: identity
    name: Identity / sign-in telemetry
    telemetry:
    - identity
tlp: clear
type: investigation
---


# Autonomous AI Retail Intrusions and Cloud Fraud

This hunt focuses on the internal and cloud control plane impact of AI-powered retail intrusions. We identify suspicious authentication leads—such as proxy-based logins or risk-flagged sessions—and use them as a gate to trigger deeper investigation into endpoint and cloud telemetry. The hunt specifically looks for the execution of autonomous penetration testing agents like Cairn and high-velocity cloud API operations used by groups like Storm-0539 for gift card fraud and data theft.

## suspicious-logon-leads
<!-- Identify suspicious authentication leads -->
Find employee logins that exhibit markers of compromise, such as proxy usage or negative risk behaviors, as a lead for an identity-based intrusion.

```sqlite target=identity role=scoping params=(lookback_days=lookback_days)
~~~yaml
expected: A list of users and hosts associated with atypical or high-risk authentication.
  Silence suggests no such logins were logged by the provider.
reads:
- actor_user_name
- src_endpoint_ip
- src_location_country
- is_proxy
- risk_state
- debug_behaviors
- device_hostname
- time
silence: not_evidence_of_absence
source: hb_auth_signin
verified: dry-run
verified_at: '2026-10-29'
~~~
SELECT actor_user_name, src_endpoint_ip, src_location_country, is_proxy, risk_state, debug_behaviors, device_hostname, time FROM hb_auth_signin WHERE (is_proxy = 'true' OR risk_state IN ('atRisk', 'confirmedCompromised') OR LOWER(debug_behaviors) LIKE '%negative%') AND time >= datetime('now', '-{{lookback_days}} days')
```

## evaluate-logon-lead
<!-- Evaluate logon leads -->
```agent target=hunter
cite: required
context:
- suspicious-logon-leads
max_iterations: 3
objective: Examine the suspicious-logon-leads rows and determine if any accounts show
  patterns of takeover, such as successful logins from a proxy immediately followed
  by a risk detection.
success_criteria: A verdict on the likelihood of account compromise.
tools:
- endpoint
- identity
```

## gate-to-investigation
<!-- Gate: Proceed to investigation? -->
if~: "the evaluate-logon-lead verdict suggests a high probability of account compromise for at least one user" (confidence: medium, judge=hunter)
then: → investigate-autonomous-traces
indeterminate: → analyst-review
unavailable: → analyst-review (blind_spot: limited-idp-telemetry)
else: → close-out

## investigate-autonomous-traces
<!-- Investigate autonomous traces -->
parallel:
- → autonomous-agent-processes
- → high-velocity-api-activity
join: → triage-intrusion

## autonomous-agent-processes
<!-- Search for autonomous agent execution -->
Detect the execution of autonomous penetration testing agents or AI-harness processes on the identified hosts.

```sqlite target=endpoint role=detection-candidate params=(lookback_days=lookback_days, agent_keywords=agent_keywords, scope_hosts=scope_hosts)
~~~yaml
expected: Process events where the image name or original file name matches an AI
  agent keyword. Silence suggests no such processes were active on the scoped hosts.
reads:
- device_hostname
- process_name
- process_cmd_line
- user_name
- time
silence: not_evidence_of_absence
source: hb_process_activity
verified: dry-run
verified_at: '2026-10-29'
~~~
SELECT device_hostname, process_name, process_cmd_line, user_name, time FROM hb_process_activity WHERE ('{{scope_hosts}}' = '' OR instr(',' || '{{scope_hosts}}' || ',', ',' || device_hostname || ',') > 0) AND (instr(',' || '{{agent_keywords}}' || ',', ',' || LOWER(process_name) || ',') > 0 OR instr(',' || '{{agent_keywords}}' || ',', ',' || LOWER(process_original_file_name) || ',') > 0) AND time >= datetime('now', '-{{lookback_days}} days')
```

## high-velocity-api-activity
<!-- Detect high-velocity cloud API bursts -->
Identify the compressed timeline of an autonomous intrusion by looking for actors performing dozens of sensitive operations in a sub-10-hour window.

```sqlite target=endpoint role=baseline params=(lookback_days=lookback_days, fraud_api_ops=fraud_api_ops)
~~~yaml
baseline:
  compare: new_this_window
  window: '{{lookback_days}}d'
expected: A single user account performing high volumes of sensitive API operations
  in a very short timeframe. Silence proves no such high-velocity bursts occurred
  in the audit log.
prevalence:
  by: api_operation
  key:
  - actor_user_name
  rare_below: 3
reads:
- actor_user_name
- api_operation
- api_category
- time
silence: not_evidence_of_absence
source: hb_cloud_api_activity
verified: dry-run
verified_at: '2026-10-29'
~~~
SELECT actor_user_name, COUNT(*) as op_count, MIN(time) as first_seen, MAX(time) as last_seen FROM hb_cloud_api_activity WHERE (instr(',' || '{{fraud_api_ops}}' || ',', ',' || api_operation || ',') > 0 OR api_category = 'GiftCardManagement') AND time >= datetime('now', '-{{lookback_days}} days') GROUP BY actor_user_name HAVING op_count > 10 AND (julianday(last_seen) - julianday(first_seen)) * 24 <= 10
```

## triage-intrusion
<!-- Correlate intrusion evidence -->
```agent target=hunter
cite: required
context:
- evaluate-logon-lead
- autonomous-agent-processes
- high-velocity-api-activity
max_iterations: 5
objective: Determine if the combined evidence from all queries indicates a coordinated,
  AI-driven retail intrusion aimed at fraud or data theft.
success_criteria: A verdict of malicious or suspicious for at least one entity.
tools:
- endpoint
- identity
```

## route-on-verdict
<!-- Route on verdict -->
if~: "the triage-intrusion verdict is malicious for an account involving fraudulent API activity or AI agent execution" (confidence: high, judge=hunter)
then: → revoke-compromised-sessions
indeterminate: → analyst-review
unavailable: → analyst-review (blind_spot: insufficient-cloud-audit-retention)
else: → close-out

## revoke-compromised-sessions
<!-- Revoke compromised sessions -->
```action target=identity
~~~yaml
approval: required
~~~
Revoke all active sessions and rotate credentials for the users identified in triage-intrusion.
```
→ analyst-review

## analyst-review
<!-- Remediate fraud impact -->
```manual target=analyst
Examine the high-velocity API logs for specific gift card IDs issued or customer files downloaded. Coordinate with fraud teams to invalidate fraudulent currency.
```
→ close-out

## close-out
<!-- Close out -->
```manual target=analyst
Log the examined accounts and hosts; record any false positives from legitimate cloud automation harnesses.
```
→ end

Run it

Take this hunt into your environment.

Open it in Huntbase to run every step against your own connections, with Scout weighing the evidence and your analysts in command. Or take the open hunt.md file anywhere that reads the format.

Machine-drafted by huntbase-hunt-generation using hb_google/gemini-3-flash-preview, gated by dry-run, lint, critic, then reviewed by a person.

Locked pack

Sign up to unlock

Pack contents are available to Huntbase users.