Case · DiggingBeagle record

Storm-3358 deployed remote-access tools through ARTEX-assisted financial-sector intrusions

Microsoft attributed an October financial-sector campaign to a Cambodia-based cluster using ARTEX alongside conventional exploitation and malware.

Public disclosure: Nov 6, 2026

Scope

Observed October 2026 ARTEX use by Microsoft-tracked Storm-3358 against financial organizations, disclosed November 6.

Assessment profile

Assessment method
Setting
production
Exploitation
confirmed in the wild
Evidence
Grade B
Remediation
mitigation available
AI role
WITH AI
Basis and provenance

Microsoft incident telemetry associates ARTEX with conventional exploitation and remote-access payload activity in Storm-3358 targets; no complete prompt attribution or victim-loss total. An impact band remains unassigned because the available evidence does not establish a comparable severity score or verified numerical loss for this assessment.

Assessed Nov 8, 2026 using diggingbeagle.assessment/1.

At a glance

Mechanism and trust boundary

  1. 01

    The actor scans externally reachable services with ARTEX and complementary utilities.

  2. 02

    An upload or SSRF weakness provides a foothold on a vulnerable target.

  3. 03

    ARTEX agents run tools including netcat or curl to fetch WISP, vshell or AdaptixC2 payloads.

  4. 04

    The malware supports persistence or follow-on access subject to the compromised host privileges.

Claims & evidence

CLM-STORM3358-ARTEX-FINANCIAL-RAT-01Microsoft reported that the actor it tracks as Storm-3358 used the ARTEX agentic offensive framework during an October 2026 campaign targeting financial-sector organizations in Southeast Asia and some global financial institutions.supported

Basis: reported finding

Link to claim
CLM-STORM3358-ARTEX-FINANCIAL-RAT-02Microsoft observed ARTEX agents use netcat and curl to obtain WISP, vshell and AdaptixC2 remote-access tools after exploitation involving anonymous file upload and server-side request forgery.supported

Basis: reported finding

Link to claim

Implications

The distinctive AI role is operational acceleration and orchestration rather than a new class of authorization bypass. Attribution must remain separate from the Microsoft GitHub-to-Key-Vault campaign unless shared infrastructure is independently demonstrated.

Controls and mitigations

  • Repair vulnerable applications, monitor command and download sequences, constrain agent action surfaces and validate remote-access payload persistence.

Unknowns and contradictions

  • The published account does not enumerate confirmed unique victims, stolen amounts, or every command selected autonomously by a model. Microsoft identifies the activity cluster as Cambodia-based; that description is not evidence of an individual operator nationality or government direction.

Sources and citation

Material revision history

  1. Nov 8, 2026 · Canonical change recorded · new in release · revision 229