Back to Intelligence

Weaponized ARTEX Penetration Testing Framework Targeting Healthcare: Detection, Containment, and Hardening Guide

SA
Security Arsenal Team
November 16, 2026
15 min read

Security researchers and incident responders have identified an active campaign in which threat actors are deploying a weaponized variant of ARTEX — an open-source penetration testing framework — against healthcare organizations. This is not a hypothetical risk. Healthcare entities across the United States are being actively targeted, and the attackers are leveraging the legitimacy and functional depth of a recognized offensive security tool to blend into environments that already run sanctioned penetration testing tools.

This campaign represents a continuation of one of the most dangerous trends in modern threat operations: the abuse of legitimate, dual-use security tools to conduct attacks under the cover of authorized-looking activity. We've seen this playbook before with Cobalt Strike, Metasploit, PsExec, and BloodHound. ARTEX is the latest framework to be pulled from the red team toolkit and pointed at organizations whose security stacks may not be tuned to flag it.

For healthcare organizations, the stakes are amplified. Protected health information (PHI) remains among the most valuable data classes on criminal markets. Ransomware operators, initial access brokers, and nation-state-aligned actors all recognize that healthcare environments often run legacy systems, maintain complex vendor integrations, and face operational pressure to prioritize uptime over security hardening. When an attacker gains a foothold using a tool that looks like it belongs, the window for detection before lateral movement and data exfiltration narrows dramatically.


Technical Analysis: How Weaponized ARTEX Operates

What Is ARTEX?

ARTEX is an open-source penetration testing framework designed to automate post-exploitation tasks, privilege escalation, lateral movement, and data collection during authorized security assessments. Like many offensive tools, it is modular, scriptable, and capable of operating across Windows and Linux environments. Its capabilities include:

  • Credential harvesting from memory, registry hives, and configuration files
  • Network reconnaissance and service enumeration
  • Remote command execution via built-in C2 (command-and-control) channels
  • Persistence mechanism deployment (scheduled tasks, service creation, registry run keys)
  • Data staging and exfiltration over encrypted channels

When operated by a legitimate red team under a signed rules-of-engagement agreement, ARTEX is a valuable assessment tool. When dropped into a healthcare network by an unauthorized actor, it is a fully functional attack platform.

The Weaponization Angle

The weaponized variant of ARTEX observed in these campaigns has been modified in several key ways:

  1. Stripped attribution markers — Known tool signatures, default strings, and metadata that would flag ARTEX as a recognized pen testing framework have been altered or removed to evade hash-based and YARA-based detection.
  2. Custom C2 infrastructure — Default callback addresses and communication ports have been reconfigured to point to attacker-controlled infrastructure, often using compromised legitimate services or domain fronting to mask traffic.
  3. Packed or obfuscated payloads — The ARTEX binaries and scripts have been repacked using commercial or custom packers to defeat static analysis and antivirus signature matching.
  4. Droppers and loaders — Initial delivery typically occurs through phishing emails targeting healthcare staff, exploiting the sector's heavy reliance on email-based communication with patients, insurers, and vendors. The dropper retrieves the ARTEX payload from a staging server, often hosted on compromised WordPress sites or cloud storage buckets.

Attack Chain in Healthcare Environments

Based on reported incidents, the typical attack chain follows this pattern:

  1. Initial Access — Spear-phishing email with a malicious attachment (macro-enabled document, ISO/IMG container, or HTML smuggling payload) or a link to a credential harvesting page mimicking a healthcare portal (e.g., Epic, Cerner, or a regional HIE login page).
  2. Execution and Staging — The dropper writes the ARTEX payload to a temporary or user-profile directory (commonly %TEMP%, %APPDATA%, or C:\ProgramData\) and executes it, sometimes with process injection into a legitimate Windows binary to evade process-based detection.
  3. Discovery and Credential Access — ARTEX modules enumerate the local system, query Active Directory, harvest cached credentials, and map network shares — with particular attention to systems hosting EHR databases, PACS imaging servers, and file shares containing PHI.
  4. Lateral Movement — Using harvested credentials, the attacker moves laterally via SMB, WinRM, or RDP to additional systems, often targeting domain controllers, backup servers, and medical device management workstations.
  5. Data Staging and Exfiltration — PHI, financial records, and employee PII are staged in compressed archives and exfiltrated over HTTPS to cloud storage services or attacker-controlled infrastructure.
  6. Persistence and Follow-On Operations — In several observed cases, the ARTEX deployment was a precursor to ransomware deployment, with the framework providing the reconnaissance and access needed for maximal-impact encryption.

Why Healthcare?

Healthcare organizations are disproportionately targeted for reasons that any seasoned IR professional will recognize:

  • Legacy infrastructure — Hospital networks frequently run outdated operating systems, unpatched medical device management platforms, and flat network architectures that facilitate lateral movement.
  • High-value data — A single health record can fetch $250 or more on dark web markets, compared to $5 for a credit card number. PHI enables insurance fraud, identity theft, and extortion.
  • Operational pressure — Healthcare organizations face intense pressure to restore operations quickly, making them more likely to pay ransoms.
  • Regulatory exposure — HIPAA breach notification requirements create public accountability that attackers exploit as leverage.

Detection and Threat Hunting

The following detection content is designed for SOC teams operating in healthcare environments. Every rule and query targets observable behaviors associated with weaponized ARTEX deployment based on the campaign reporting. These are behavioral detections — they look for what the tool does, not just what it is — which makes them resilient to the packing and obfuscation techniques described above.

Sigma Rules

YAML
---
title: ARTEX Framework Dropper Execution from User-Writable Directories
id: a1b2c3d4-5e6f-7890-abcd-ef1234567890
status: experimental
description: Detects execution of binaries or scripts from user-writable directories commonly used by ARTEX droppers to stage payloads. Weaponized ARTEX has been observed writing to TEMP, APPDATA, and ProgramData before executing post-exploitation modules.
references:
  - https://www.hipaajournal.com/weaponized-artex-pen-testing-framework-attacks-healthcare/
  - https://attack.mitre.org/techniques/T1059/
author: Security Arsenal
date: 2026/04/07
tags:
  - attack.execution
  - attack.t1059
logsource:
  category: process_creation
  product: windows
detection:
  selection_paths:
    Image|contains:
      - '\AppData\Local\Temp\'
      - '\AppData\Roaming\'
      - 'C:\ProgramData\'
  selection_executables:
    Image|endswith:
      - '.exe'
      - '.dll'
      - '.ps1'
      - '.bat'
  filter_known_good:
    Image|contains:
      - '\AppData\Local\Microsoft\'
      - '\AppData\Local\Google\'
      - '\AppData\Local\Mozilla\'
      - '\AppData\Roaming\Microsoft\'
      - 'C:\ProgramData\Microsoft\'
  condition: selection_paths and selection_executables and not filter_known_good
falsepositives:
  - Legitimate software installations or updates running from ProgramData
  - Portable applications executed from user directories
level: medium
---
title: ARTEX Post-Exploitation Credential Harvesting Behavior
id: b2c3d4e5-6f78-90ab-cdef-123456789abc
status: experimental
description: Detects process behavior consistent with ARTEX credential harvesting modules, including access to LSASS memory, SAM/SECURITY registry hives, and cached credential stores. Weaponized ARTEX performs automated credential dumping shortly after initial execution.
references:
  - https://www.hipaajournal.com/weaponized-artex-pen-testing-framework-attacks-healthcare/
  - https://attack.mitre.org/techniques/T1003/
author: Security Arsenal
date: 2026/04/07
tags:
  - attack.credential_access
  - attack.t1003.001
  - attack.t1003.002
logsource:
  category: process_creation
  product: windows
detection:
  selection_comsvcs:
    CommandLine|contains:
      - 'comsvcs.dll'
      - 'MiniDump'
      - 'lsass'
  selection_registry_hives:
    CommandLine|contains:
      - 'reg save HKLM\SAM'
      - 'reg save HKLM\SECURITY'
      - 'reg save HKLM\SYSTEM'
  selection_vault:
    CommandLine|contains:
      - 'vaultcmd'
      - '/listcreds'
  condition: 1 of selection_*
falsepositives:
  - Authorized red team or penetration testing engagements
  - Legitimate backup or forensic collection tools accessing registry hives
level: high
---
title: ARTEX Lateral Movement via SMB Admin Share or WinRM
id: c3d4e5f6-7890-abcd-ef12-3456789abcde
status: experimental
description: Detects network connections to SMB administrative shares or WinRM from processes running outside expected administrative tool paths. ARTEX uses harvested credentials to move laterally, typically connecting to ADMIN$, C$, or IPC$ shares or establishing WinRM sessions.
references:
  - https://www.hipaajournal.com/weaponized-artex-pen-testing-framework-attacks-healthcare/
  - https://attack.mitre.org/techniques/T1021/
author: Security Arsenal
date: 2026/04/07
tags:
  - attack.lateral_movement
  - attack.t1021.001
  - attack.t1021.002
  - attack.t1021.006
logsource:
  category: network_connection
  product: windows
detection:
  selection_ports:
    DestinationPort:
      - 445
      - 5985
      - 5986
  selection_suspicious_source:
    Image|contains:
      - '\AppData\'
      - '\ProgramData\'
      - '\Temp\'
      - '\Users\Public\'
  filter_admin_tools:
    Image|endswith:
      - '\psexec.exe'
      - '\psexesvc.exe'
      - '\mmc.exe'
      - '\ServerManager.exe'
      - '\svchost.exe'
      - '\wmiprvse.exe'
      - '\wsmprovhost.exe'
  condition: selection_ports and selection_suspicious_source and not filter_admin_tools
falsepositives:
  - Legitimate administrative scripts running from non-standard paths
  - IT management tools deployed to ProgramData
level: high

KQL Hunt Query — Microsoft Sentinel / Defender

KQL — Microsoft Sentinel / Defender
// Hunt for ARTEX framework indicators: suspicious process execution from user-writable
// directories combined with credential access and lateral movement behavior.
// Recommended lookback: 7 days. Adjust the timerange based on your IR timeline.
let lookback = 7d;
// Stage 1: Identify suspicious process execution from staging directories
let SuspiciousExecution = DeviceProcessEvents
    | where Timestamp >= ago(lookback)
    | where FolderPath has_any ("\\AppData\\Local\\Temp\\", "\\AppData\\Roaming\\", "\\ProgramData\\", "\\Users\\Public\\")
    | where FileName endswith ".exe" or FileName endswith ".ps1" or FileName endswith ".bat"
    | where not(FolderPath has_any ("\\Microsoft\\", "\\Google\\", "\\Mozilla\\", "\\Adobe\\"))
    | project DeviceId, DeviceName, ProcessId, FileName, FolderPath, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessCommandLine, Timestamp, AccountName;
// Stage 2: Correlate with credential access behavior
let CredentialAccess = DeviceProcessEvents
    | where Timestamp >= ago(lookback)
    | where ProcessCommandLine has_any ("comsvcs.dll", "MiniDump", "lsass", "reg save HKLM\\SAM", "reg save HKLM\\SECURITY", "vaultcmd", "/listcreds")
    | project DeviceId, DeviceName, FileName, ProcessCommandLine, Timestamp, AccountName;
// Stage 3: Correlate with lateral movement indicators
let LateralMovement = DeviceNetworkEvents
    | where Timestamp >= ago(lookback)
    | where RemotePort in (445, 5985, 5986)
    | where InitiatingProcessFolderPath has_any ("\\AppData\\", "\\ProgramData\\", "\\Temp\\", "\\Users\\Public\\")
    | project DeviceId, DeviceName, InitiatingProcessFileName, InitiatingProcessFolderPath, InitiatingProcessCommandLine, RemoteIP, RemotePort, Timestamp;
// Join: Surface devices with two or more correlated behaviors
SuspiciousExecution
| join kind=inner (CredentialAccess) on DeviceId
| project DeviceName, ExecutionFile=FileName, ExecutionPath=FolderPath, ExecutionCmd=ProcessCommandLine, CredAccessCmd=ProcessCommandLine1, CredAccessTime=Timestamp1, Account=AccountName
| join kind=inner (LateralMovement) on DeviceId
| project DeviceName, Account, ExecutionFile, ExecutionPath, ExecutionCmd, CredAccessCmd, CredAccessTime, LateralProcess=InitiatingProcessFileName, LateralCmd=InitiatingProcessCommandLine, RemoteTarget=RemoteIP, RemotePort, LateralTime=Timestamp
| sort by LateralTime desc

Velociraptor VQL Hunt

VQL — Velociraptor
-- Hunt for ARTEX framework indicators across endpoints
-- Targets: suspicious process execution, credential access artifacts, and
-- persistence mechanisms consistent with weaponized pen testing tool deployment

-- Part 1: Active processes running from suspicious directories
SELECT Pid, Name, Exe, CommandLine, Username, CreateTime
FROM pslist()
WHERE Exe =~ '(?i)(\\\\AppData\\\\(Local|Roaming)\\\\|\\\\ProgramData\\\\|\\\\Users\\\\Public\\\\)'
  AND NOT Exe =~ '(?i)(Microsoft|Google|Mozilla|Adobe|Teams|Zoom|Slack|Spotify)'
  AND Name =~ '(?i)\\.(exe|ps1|bat|dll)$'

-- Part 2: Check for recently created scheduled tasks (persistence)
SELECT Name, Command, UserId, Enabled, LastRunTime, NextRunTime
FROM glob(glob='C:/Windows/System32/Tasks/**')
WHERE NOT Name =~ '(?i)(Microsoft|Google|Adobe|Intel|NVIDIA|Dell|HP)'
ORDER BY LastRunTime DESC

-- Part 3: Network connections from non-standard processes on admin ports
SELECT Pid, Name, Path, LocalAddr, LocalPort, RemoteAddr, RemotePort, State, Username
FROM netstat()
WHERE RemotePort in (445, 5985, 5986, 3389)
  AND Path =~ '(?i)(\\\\AppData\\\\|\\\\ProgramData\\\\|\\\\Temp\\\\|\\\\Users\\\\Public\\\\)'
  AND State =~ 'ESTABLISHED'

PowerShell Remediation and Verification Script

PowerShell
# ============================================================
# ARTEX Weaponized Framework — Detection and Hardening Script
# Security Arsenal | 2026-04-07
# Run with elevated privileges on all healthcare endpoints
# and servers. Review output before taking automated actions.
# ============================================================

# --- 1. Identify suspicious processes running from staging directories ---
Write-Host "[*] Checking for suspicious processes in user-writable directories..." -ForegroundColor Cyan
$suspiciousPaths = @(
    "$env:TEMP",
    "$env:APPDATA",
    "$env:LOCALAPPDATA\Temp",
    "C:\ProgramData",
    "C:\Users\Public"
)
$suspiciousProcesses = Get-Process | Where-Object {
    $_.Path -and ($suspiciousPaths | Where-Object { $_.Path -like "$_*" }) -and
    $_.Path -notmatch "Microsoft|Google|Mozilla|Adobe|Teams|Zoom|Slack"
} | Select-Object Name, Id, Path, StartTime

if ($suspiciousProcesses) {
    Write-Host "[!] ALERT: Suspicious processes detected:" -ForegroundColor Red
    $suspiciousProcesses | Format-Table -AutoSize
} else {
    Write-Host "[+] No suspicious processes found in staging directories." -ForegroundColor Green
}

# --- 2. Check for LSASS access by non-system processes ---
Write-Host "`n[*] Checking for recent LSASS memory access attempts..." -ForegroundColor Cyan
$lsassEvents = Get-WinEvent -FilterHashtable @{
    LogName   = 'Security'
    Id        = 4656
    StartTime = (Get-Date).AddDays(-3)
} -MaxEvents 5000 -ErrorAction SilentlyContinue | Where-Object {
    $_.Message -match 'lsass\.exe' -and $_.Message -notmatch 'SYSTEM|MsMpEng|wininit|csrss|svchost'
}

if ($lsassEvents) {
    Write-Host "[!] ALERT: Non-standard processes accessed LSASS:" -ForegroundColor Red
    $lsassEvents | Select-Object TimeCreated, @{N='Message';E={$_.Message.Substring(0, [Math]::Min(300, $_.Message.Length))}} | Format-List
} else {
    Write-Host "[+] No unauthorized LSASS access detected in the last 72 hours." -ForegroundColor Green
}

# --- 3. Audit scheduled tasks for persistence ---
Write-Host "`n[*] Auditing scheduled tasks for unauthorized persistence..." -ForegroundColor Cyan
$suspiciousTasks = Get-ScheduledTask | Where-Object {
    $_.TaskPath -notmatch '\\Microsoft\\' -and
    $_.Actions.Execute -and
    $_.Actions.Execute -notmatch 'C:\\Windows|C:\\Program Files'
} | Select-Object TaskName, TaskPath, @{N='Action';E={$_.Actions.Execute}}, State

if ($suspiciousTasks) {
    Write-Host "[!] REVIEW: Non-standard scheduled tasks found:" -ForegroundColor Yellow
    $suspiciousTasks | Format-Table -AutoSize
} else {
    Write-Host "[+] No suspicious scheduled tasks detected." -ForegroundColor Green
}

# --- 4. Check for unauthorized WinRM and SMB configuration changes ---
Write-Host "`n[*] Checking WinRM service status..." -ForegroundColor Cyan
$winrm = Get-Service -Name WinRM -ErrorAction SilentlyContinue
if ($winrm.Status -eq 'Running') {
    Write-Host "[!] WinRM is running. Verify this is authorized in your environment." -ForegroundColor Yellow
    $winrmListeners = winrm enumerate winrm/config/listener 2>$null
    Write-Host $winrmListeners
} else {
    Write-Host "[+] WinRM is not running." -ForegroundColor Green
}

# --- 5. Harden: Restrict PowerShell execution policy ---
Write-Host "`n[*] Current PowerShell execution policies:" -ForegroundColor Cyan
Get-ExecutionPolicy -List | Format-Table -AutoSize

Write-Host "[*] Setting PowerShell execution policy to RemoteSigned for LocalMachine..." -ForegroundColor Cyan
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope LocalMachine -Force
Write-Host "[+] Execution policy set to RemoteSigned." -ForegroundColor Green

# --- 6. Enable Windows Defender Attack Surface Reduction rules ---
Write-Host "`n[*] Enabling ASR rules to block common attack techniques..." -ForegroundColor Cyan
# Block executable content from email client and webmail
Set-MpPreference -AttackSurfaceReductionRules_Ids "BE9BA2D9-53EA-4CDC-84E5-9B1EEEE46550" -AttackSurfaceReductionRules_Actions Enabled
# Block credential stealing from LSASS
Set-MpPreference -AttackSurfaceReductionRules_Ids "9E6C4E1F-7D60-472F-BA1A-A39EF669E4B2" -AttackSurfaceReductionRules_Actions Enabled
# Block process injection
Set-MpPreference -AttackSurfaceReductionRules_Ids "C1DB55AB-C21A-4637-BB3F-A12568109D35" -AttackSurfaceReductionRules_Actions Enabled
# Block Office from creating child processes
Set-MpPreference -AttackSurfaceReductionRules_Ids "D4F940AB-401B-4EFC-AADC-AD5F3C50688A" -AttackSurfaceReductionRules_Actions Enabled
Write-Host "[+] ASR rules enabled." -ForegroundColor Green

# --- 7. Summary ---
Write-Host "`n=========================================" -ForegroundColor Cyan
Write-Host " ARTEX Detection and Hardening Complete" -ForegroundColor Cyan
Write-Host " Review any [!] ALERT or REVIEW items" -ForegroundColor Cyan
Write-Host " Escalate findings to your IR team" -ForegroundColor Cyan
Write-Host "=========================================" -ForegroundColor Cyan

Remediation and Hardening for Healthcare Environments

The detection content above will help you identify active compromise. The following steps address prevention and hardening specifically for healthcare environments facing weaponized offensive tool abuse.

1. Application Control and Allowlisting

The single most effective control against weaponized pen testing frameworks is application allowlisting. Tools like ARTEX, Cobalt Strike, and Metasploit succeed because endpoints will execute arbitrary binaries. Deploy Windows Defender Application Control (WDAC) or AppLocker policies that:

  • Block execution from user-writable directories (%TEMP%, %APPDATA%, %LOCALAPPDATA%, C:\ProgramData\, C:\Users\Public\)
  • Permit only signed, organizationally approved executables
  • Maintain an exception process for authorized penetration testing engagements (with time-bound, scope-limited rules)

2. Network Segmentation for Medical and EHR Systems

Lateral movement is the force multiplier in these campaigns. Segment your network to ensure that:

  • EHR database servers are accessible only from authorized application servers
  • Medical device management VLANs are isolated from general corporate networks
  • SMB, WinRM, and RDP are restricted between workstation VLANs
  • All east-west traffic passes through internal firewalls with logging enabled

3. Credential Hygiene and Privileged Access Management

ARTEX's credential harvesting modules are effective because cached credentials and over-privileged service accounts are endemic in healthcare environments. Implement:

  • LAPS (Local Administrator Password Solution) on all endpoints to eliminate shared local admin credentials
  • Tiered administration — domain admin credentials should never be used on workstations or member servers
  • Credential Guard on Windows 10/11 and Server 2019+ to protect LSASS memory
  • SMB signing enforcement to mitigate relay attacks

4. Phishing-Resistant Authentication

The initial access vector in this campaign is spear phishing. Reduce your exposure:

  • Deploy FIDO2 hardware keys or certificate-based authentication for remote access and privileged accounts
  • Enable Office 365 / Google Workspace anti-phishing policies with strict attachment filtering (block macros, ISO/IMG containers, and HTML attachments from external senders)
  • Conduct regular phishing simulation exercises targeted at clinical staff, not just IT

5. Authorized Tool Governance

If your organization conducts penetration testing — and it should — establish clear governance:

  • Maintain a whitelist of approved pen testing tools and their expected hashes
  • Require advance notification to the SOC before any authorized test begins
  • Configure SIEM correlation rules to suppress alerts for authorized tool executions during approved windows
  • This allows your SOC to immediately flag any ARTEX, Cobalt Strike, or Metasploit execution that does not correspond to an authorized engagement

6. HIPAA-Specific Actions

If your organization has been affected by this campaign:

  • Initiate a forensic investigation to determine the scope of PHI access or exfiltration
  • Consult HIPAA breach notification requirements — if PHI was accessed, the 60-day notification clock is running
  • Notify HHS Office for Civil Rights (OCR) if 500 or more individuals are affected
  • Engage counsel experienced in healthcare data breach response
  • Document all remediation actions for potential regulatory review

The Broader Lesson

The weaponization of ARTEX is not an anomaly — it is a pattern. Threat actors have systematically adopted legitimate security tools because they work, they blend in, and they complicate attribution. Your detection strategy cannot rely on blocking known-bad signatures. It must be built on behavioral detection, application control, network segmentation, and a clear understanding of what authorized tool usage looks like in your environment — so that unauthorized usage stands out immediately.

For healthcare organizations, the urgency is compounded by regulatory obligations and patient safety considerations. A breach that disrupts EHR availability or exposes PHI is not just a security incident — it is a clinical and compliance emergency.

Act now. Run the hunt queries. Validate your segmentation. Confirm your application control policies. And if you need help, reach out to a team that has been in the trenches.


Related Resources

Security Arsenal Healthcare Cybersecurity AlertMonitor Platform Book a SOC Assessment healthcare Intel Hub

Is your security operations ready?

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