Back to Intelligence

ARTEX Autonomous Attack Framework + Storm-3358: BLOODALCHEMY, WISP, vshell & AdaptixC2 C2 Infrastructure — OTX Detection Pack

SA
Security Arsenal Team
November 16, 2026
9 min read

Intelligence Briefing — From The Dark Side Threat Level: HIGH | TLP: WHITE | Pulse Date: 2026-11-16


Threat Summary

AlienVault's OTX research team has published a threat overview of ARTEX, an open-source, large language model-driven autonomous penetration testing framework that has been weaponized by threat actors — attributed activity tracked as Storm-3358 — to automate full-kill-chain intrusions from reconnaissance through data exfiltration.

Since August 2026, ARTEX-driven campaigns have been observed globally across nine sectors: Finance, Government, Technology, Defense, Semiconductor, Energy, Healthcare, Manufacturing, and Telecommunications — with specific tags indicating targeting of South Korean financial institutions. The defining characteristic of this activity is velocity: the LLM agentic layer compresses intrusion timelines dramatically, with some attacks progressing from initial access to exfiltration in timeframes that defeat conventional dwell-time-based detection strategies.

The attack chain observed in this pulse:

  1. Initial Access / Recon — ARTEX's agentic planner automates target profiling, phishing content generation, and exploit selection.
  2. Execution & Persistence — Deployment of the BLOODALCHEMY backdoor (historically delivered via DLL side-loading against legitimate signed binaries) and vshell implants, with registry Run key and scheduled task persistence.
  3. Command & Control — Dual-framework C2 using WISP and AdaptixC2 beaconing to the IPv4 infrastructure listed below.
  4. Exfiltration — Automated collection staging and egress orchestrated by the ARTEX agentic loop.

The objective appears to be intelligence collection and financial-sector espionage, with supply chain compromise flagged as a delivery vector in pulse tags.


Threat Actor / Malware Profile

Storm-3358 + ARTEX Agentic Layer

Storm-3358 is leveraging ARTEX as a force multiplier: an LLM planner sits atop conventional offensive tooling, selecting payloads, mutating phishing lures, and driving post-exploitation playbooks with minimal human operator involvement. Detection teams should expect highly variable TTP sequencing between intrusions — the agent does not repeat playbooks deterministically — which breaks IOC-of-the-day defense and demands behavioral detection.

BLOODALCHEMY (Backdoor)

  • Distribution: DLL side-loading against legitimate signed executables; malicious DLL placed alongside a renamed legitimate binary in a writable directory (commonly %ProgramData% or user profile paths).
  • Payload Behavior: Staged loader that decrypts and injects the final backdoor payload into memory; communicates with operator tooling for shell access and payload retrieval.
  • Persistence: Registry Run keys and Windows services masquerading as legitimate vendor names.
  • Anti-Analysis: Parent process verification (refuses to run if launched outside the expected loader), encrypted configuration blobs, and sandbox-aware execution delays.

vshell (Implant)

  • Behavior: Fileless-leaning shell implant frequently launched via rundll32.exe or reflective injection; provides interactive command execution.
  • C2: Custom TCP/HTTPS beaconing with low-and-slow jitter intervals.

WISP + AdaptixC2 (C2 Frameworks)

  • AdaptixC2 is an extensible post-exploitation framework (functionally analogous to Cobalt Strike) with malleable beacon profiles. Beacons typically present as periodic outbound HTTPS to dedicated VPS infrastructure — exactly the profile of the 8 IPv4 indicators in this pulse.
  • WISP traffic is characterized by small, regular-interval encrypted payloads to hardcoded IP literals (no DNS resolution), a strong hunting signal.

IOC Analysis

This pulse contains 13 indicators, all IPv4 addresses — consistent with dedicated VPS C2 infrastructure rather than domain-fronted or CDN-backed comms. The 8 published samples:

IndicatorTypeAssessed Role
91.92.240.238IPv4AdaptixC2 / vshell C2
38.244.50.120IPv4AdaptixC2 C2
101.53.80.20IPv4BLOODALCHEMY C2
205.214.59.31IPv4C2 / staging
124.155.252.63IPv4WISP C2
23.248.249.90IPv4AdaptixC2 C2
23.158.220.98IPv4C2 / staging
103.248.148.84IPv4BLOODALCHEMY C2

Operationalization guidance for SOC teams:

  • Push all indicators to egress firewall, proxy, and DNS-sinkhole deny lists immediately. Because these are bare IPs (no domain layer), TLS SNI-based filtering will miss them — ensure IP-layer blocking.
  • Retrohunt NetFlow/proxy/firewall logs for 90 days of historical connections; agentic campaigns move fast and may have completed before detection.
  • Enrich against your threat intel platform (MISP, OpenCTI, Sentinel TI) and correlate with authentication anomalies — ARTEX intrusions often pair C2 access with stolen session tokens.
  • No file hashes or domains were published in this pulse sample; treat IP-only coverage as partial and prioritize the behavioral detections below.

Detection Engineering

YAML
---
title: ARTEX Campaign - Known C2 IPv4 Communication (Storm-3358 / BLOODALCHEMY / WISP / vshell / AdaptixC2)
id: 7a1f3c2e-9b44-4d6a-8e21-3f5a9c71d001
status: experimental
description: Detects outbound network connections to known C2 IPv4 infrastructure associated with the ARTEX autonomous attack framework campaign tracked as Storm-3358 (BLOODALCHEMY, WISP, vshell, AdaptixC2).
author: Security Arsenal Threat Intelligence
references:
    - https://www.ic3.gov/CSA/2026/261113.pdf
date: 2026/11/16
logsource:
    category: network_connection
    product: windows
detection:
    selection:
        DestinationIp:
            - 91.92.240.238
            - 38.244.50.120
            - 101.53.80.20
            - 205.214.59.31
            - 124.155.252.63
            - 23.248.249.90
            - 23.158.220.98
            - 103.248.148.84
    condition: selection
falsepositives:
    - Legitimate traffic to unrelated services hosted on the same VPS providers (unlikely but verify)
level: critical
tags:
    - attack.command_and_control
    - attack.t1071
---
title: BLOODALCHEMY DLL Side-Loading via Rundll32 or Signed Binary Masquerade
id: 8b2e4d3f-1c55-4e7b-9f32-4a6b0d82e002
status: experimental
description: Detects suspicious DLL execution patterns consistent with BLOODALCHEMY backdoor delivery, including rundll32 loading DLLs from user-writable paths and unsigned DLL loads from ProgramData.
author: Security Arsenal Threat Intelligence
references:
    - https://www.ic3.gov/CSA/2026/261113.pdf
date: 2026/11/16
logsource:
    category: process_creation
    product: windows
detection:
    selection_img:
        Image|endswith:
            - '\rundll32.exe'
            - '\regsvr32.exe'
    selection_path:
        CommandLine|contains:
            - '\AppData\Local\Temp\'
            - '\ProgramData\'
            - '\AppData\Roaming\'
            - '\Users\Public\'
    selection_ext:
        CommandLine|contains: '.dll'
    filter_known_good:
        CommandLine|contains:
            - '\ProgramData\Microsoft\'
            - 'SoftwareProtectionPlatform'
    condition: selection_img and selection_path and selection_ext and not filter_known_good
falsepositives:
    - Legitimate software updaters staging DLLs in ProgramData
level: high
tags:
    - attack.defense_evasion
    - attack.t1218.011
    - attack.t1574.002
---
title: Persistence via Registry Run Key or Scheduled Task - ARTEX Implant Families
id: 9c3f5e4a-2d66-4f8c-a043-5b7c1e93f003
status: experimental
description: Detects persistence establishment through registry Run keys or scheduled tasks pointing to executables in user-writable directories, consistent with BLOODALCHEMY and vshell persistence behavior observed in the Storm-3358 ARTEX campaign.
author: Security Arsenal Threat Intelligence
references:
    - https://www.ic3.gov/CSA/2026/261113.pdf
date: 2026/11/16
logsource:
    category: registry_set
    product: windows
detection:
    selection_key:
        TargetObject|contains:
            - '\Software\Microsoft\Windows\CurrentVersion\Run'
            - '\Software\Microsoft\Windows\CurrentVersion\RunOnce'
    selection_value:
        Details|contains:
            - '\AppData\'
            - '\ProgramData\'
            - '\Users\Public\'
            - 'rundll32'
    condition: selection_key and selection_value
falsepositives:
    - Legitimate user-space applications registering auto-start entries
level: high
tags:
    - attack.persistence
    - attack.t1060
    - attack.t1547.001
KQL — Microsoft Sentinel / Defender
// ARTEX / Storm-3358 C2 Infrastructure Hunt — Microsoft Sentinel
// Hunts for outbound connections to the 8 known C2 IPs published in OTX pulse (2026-11-16)
// plus surrounding process context for triage.
let C2IPs = dynamic([
    "91.92.240.238", "38.244.50.120", "101.53.80.20", "205.214.59.31",
    "124.155.252.63", "23.248.249.90", "23.158.220.98", "103.248.148.84"
]);
DeviceNetworkEvents
| where TimeGenerated > ago(90d)
| where RemoteIP in (C2IPs)
| join kind=leftouter (
    DeviceProcessEvents
    | where TimeGenerated > ago(90d)
    | project DeviceId, ProcessCreationTime=TimeGenerated, FileName, ProcessCommandLine, InitiatingProcessFileName, SHA256
) on DeviceId, $left.InitiatingProcessId == $right.ProcessId
| project TimeGenerated, DeviceName, RemoteIP, RemotePort, RemoteUrl,
          InitiatingProcessFileName, InitiatingProcessCommandLine,
          FileName, ProcessCommandLine, SHA256
| extend BeaconIntervalCheck = "Review: repeated connections at regular intervals indicate AdaptixC2/WISP beaconing"
| order by TimeGenerated desc
PowerShell
# ============================================================
# Security Arsenal — ARTEX / Storm-3358 IOC Hunt Script
# Checks: live C2 connections, Run-key persistence, suspicious
# scheduled tasks, and DLL staging in user-writable paths.
# Run elevated on suspect endpoints. Output: .
# ARTEX_Hunt_Report_<hostname>_<timestamp>.txt
# ============================================================

$C2IPs = @(
    "91.92.240.238","38.244.50.120","101.53.80.20","205.214.59.31",
    "124.155.252.63","23.248.249.90","23.158.220.98","103.248.148.84"
)

$Report = ".\ARTEX_Hunt_Report_$($env:COMPUTERNAME)_$(Get-Date -Format 'yyyyMMdd_HHmmss').txt"
"=== ARTEX / Storm-3358 IOC Hunt — $(Get-Date) ===" | Out-File $Report

Write-Host "[1/4] Checking active network connections against C2 list..." -ForegroundColor Cyan
"`n[1] ACTIVE C2 CONNECTIONS" | Out-File $Report -Append
$Hits = Get-NetTCPConnection | Where-Object { $C2IPs -contains $_.RemoteAddress }
if ($Hits) {
    $Hits | ForEach-Object {
        $Proc = Get-Process -Id $_.OwningProcess -ErrorAction SilentlyContinue
        "HIT: $($_.LocalAddress):$($_.LocalPort) -> $($_.RemoteAddress):$($_.RemotePort) | Process: $($Proc.ProcessName) (PID $($_.OwningProcess)) | Path: $($Proc.Path)" | Out-File $Report -Append
    }
    Write-Host "  !! C2 CONNECTIONS FOUND — see report" -ForegroundColor Red
} else { "  None." | Out-File $Report -Append; Write-Host "  Clean." -ForegroundColor Green }

Write-Host "[2/4] Auditing Run / RunOnce persistence keys..." -ForegroundColor Cyan
"`n[2] SUSPICIOUS RUN KEYS" | Out-File $Report -Append
$RunKeys = @(
    "HKLM:\Software\Microsoft\Windows\CurrentVersion\Run",
    "HKLM:\Software\Microsoft\Windows\CurrentVersion\RunOnce",
    "HKCU:\Software\Microsoft\Windows\CurrentVersion\Run",
    "HKCU:\Software\Microsoft\Windows\CurrentVersion\RunOnce"
)
foreach ($Key in $RunKeys) {
    if (Test-Path $Key) {
        (Get-ItemProperty $Key).PSObject.Properties | Where-Object {
            $_.Value -match "AppData|ProgramData|Public|rundll32|regsvr32"
        } | ForEach-Object {
            "SUSPECT: $Key :: $($_.Name) = $($_.Value)" | Out-File $Report -Append
        }
    }
}

Write-Host "[3/4] Scanning scheduled tasks for user-writable-path payloads..." -ForegroundColor Cyan
"`n[3] SUSPICIOUS SCHEDULED TASKS" | Out-File $Report -Append
Get-ScheduledTask | ForEach-Object {
    $Actions = $_.Actions | Where-Object { $_.Execute -match "AppData|ProgramData|Public|rundll32" }
    if ($Actions) {
        $Actions | ForEach-Object {
            "SUSPECT TASK: $($Task.TaskName) :: $($_.Execute) $($_.Arguments)" | Out-File $Report -Append
        }
    }
}

Write-Host "[4/4] Hunting recently modified DLLs in staging directories (BLOODALCHEMY side-load)..." -ForegroundColor Cyan
"`n[4] RECENT DLLs IN STAGING PATHS (last 30 days)" | Out-File $Report -Append
$StagingPaths = @("$env:ProgramData", "$env:PUBLIC", "$env:APPDATA", "$env:LOCALAPPDATA\Temp")
foreach ($Path in $StagingPaths) {
    Get-ChildItem -Path $Path -Recurse -Filter *.dll -ErrorAction SilentlyContinue |
        Where-Object { $_.LastWriteTime -gt (Get-Date).AddDays(-30) } |
        Select-Object -First 50 |
        ForEach-Object { "DLL: $($_.FullName) | Modified: $($_.LastWriteTime)" | Out-File $Report -Append }
}

Write-Host "`nHunt complete. Report: $Report" -ForegroundColor Yellow

Response Priorities

Immediate (0–4 hours)

  • Block all 8 C2 IPv4 addresses at the egress firewall, web proxy, and EDR network layer. Bare-IP infrastructure requires IP-layer blocking — DNS controls are insufficient.
  • Run the KQL hunt and PowerShell script across the estate; prioritize Finance, Government, and any South Korea-connected business units given documented targeting.
  • Isolate any endpoint with confirmed C2 connections and capture memory before remediation — BLOODALCHEMY's final-stage payload is memory-resident.

24 Hours

  • Credential and session reset: Although this pulse does not flag a dedicated stealer family, AdaptixC2 operators routinely harvest credentials and tokens post-exploitation. Force password resets and revoke active sessions/OAuth tokens for any user whose device touched the C2 list.
  • Retrohunt email gateways for agentic-generated phishing (ARTEX produces high-quality, low-error lures — traditional grammatical-error heuristics will fail).
  • Review supply chain and third-party remote access sessions; "supply chain compromise" is an explicit pulse tag.

1 Week

  • Architecture hardening against agentic-speed intrusions: Deploy application allowlisting to kill DLL side-loading paths, restrict rundll32/regsvr32 to signed DLL locations via WDAC or AppLocker, and segment crown-jewel segments (finance systems, semiconductor IP, defense data) so automated lateral movement hits hard boundaries.
  • Tune detections for beacon interval analysis rather than signature matching — agentic operators rotate infrastructure faster than TI feeds publish it.
  • Conduct a tabletop exercise simulating a sub-60-minute recon-to-exfil intrusion, the observed ARTEX tempo, and validate your SOC can detect and contain at machine speed (automated isolation playbooks strongly recommended).

Related Resources

Security Arsenal Incident Response Managed SOC & MDR Services AlertMonitor Threat Detection From The Dark Side Intel Hub

Is your security operations ready?

Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.