Back to Intelligence

Head Mare APT Exploits TrueConf Video Conferencing Servers to Deliver PhantomCore Malware: OTX Pulse Analysis — Supply Chain Detection Pack

SA
Security Arsenal Team
September 20, 2026
10 min read

AlienVault OTX pulse data confirms an active supply chain campaign attributed to the Head Mare APT group targeting organizations through TrueConf video conferencing infrastructure. Rather than attacking endpoints directly, the adversary exploited two vulnerabilities in unpatched TrueConf servers to gain arbitrary code execution on the conferencing server itself. From that beachhead, Head Mare executed three mutually reinforcing actions:

  1. Replaced legitimate TrueConf client installers hosted on the compromised server with trojanized versions carrying the PhantomCore malware family.
  2. Deployed web shells on the server for persistent access and on-demand payload manipulation.
  3. Weaponized the trust relationship between the conferencing server and meeting participants — every user who downloaded or updated the client from a compromised server received an infected installer, turning a routine software download into an APT intrusion vector.

The campaign also references PhantomGraph, a companion malware family consistent with Head Mare's established tooling. This is a classic downstream software supply chain compromise (MITRE ATT&CK T1195.002) combined with external service exploitation (T1190) and server-side web shell persistence (T1505.003). The strategic objective is espionage-grade access into organizations that rely on TrueConf for internal and cross-organizational video conferencing — a platform with significant deployment in government, defense, and industrial sectors in its primary markets. Kaspersky ICS CERT reporting indicates the campaign targeted conference participants as the actual victims, making the conferencing server a force multiplier: one server compromise yields dozens or hundreds of victim endpoints.

Urgency: CRITICAL. Any organization operating TrueConf servers — or whose partners, suppliers, or meeting counterparties operate them — must assume exposure until proven otherwise.

Threat Actor / Malware Profile

Head Mare (APT Group)

Head Mare is an intrusion set documented since 2023 targeting organizations primarily through exploitation of internet-facing services, with a demonstrated pattern of opportunistic-n-day exploitation combined with custom backdoor deployment. Their tradecraft emphasizes:

  • Initial access via public-facing application exploitation — in this campaign, two distinct TrueConf server vulnerabilities enabling arbitrary code execution.
  • Infrastructure pre-staging — web shells placed on compromised servers to maintain durable access even if the original vulnerability is patched.
  • Trust-chain weaponization — modifying vendor-signed software distribution paths rather than relying on phishing, dramatically increasing infection rates while reducing per-target effort.

PhantomCore (Backdoor)

PhantomCore is Head Mare's primary remote access backdoor:

  • Distribution method: Bundled into trojanized TrueConf client installers downloaded from compromised conferencing servers. The installer retains legitimate functionality — the video conferencing client installs and operates normally — masking the malicious payload.
  • Payload behavior: Establishes a persistent foothold on the endpoint, collects host profiling data (OS version, hostname, domain membership, running processes), and retrieves secondary commands or payloads from operator-controlled C2.
  • C2 communication: Beaconing over HTTP/S to attacker-controlled infrastructure, with configurable intervals and jitter to blend with normal conferencing traffic — particularly effective since the host legitimately communicates with conferencing services.
  • Persistence mechanism: Registry Run-key entries and/or scheduled task creation masquerading as conferencing client updaters (e.g., update/service tasks referencing TrueConf-adjacent names).
  • Anti-analysis: Obfuscated strings, delayed execution to evade sandbox detonation, and payload staging that only activates when a real user environment is detected (checking for domain join, user activity, conferencing software artifacts).

PhantomGraph

A secondary implant family associated with the same actor, used for follow-on operations: lateral movement support, data staging, and additional loader functionality on higher-value victims. Its presence in the pulse indicates the campaign is multi-stage, not smash-and-grab.

IOC Analysis

The pulse contains 40 indicators, with the sample set showing MD5 file hashes — these represent the trojanized TrueConf installers, PhantomCore/PhantomGraph payloads, and web shell components. Operationalization guidance for SOC teams:

  • File hashes (MD5): Immediately ingest into your EDR blocklist and threat intel platform. MD5 hashes are brittle — a single byte change defeats them — so treat these as point-in-time artifacts and prioritize behavioral detections (below) for durable coverage. Cross-reference hashes against VirusTotal, MalwareBazaar, and the Kaspersky ICS CERT report, which may publish SHA-256 equivalents preferable for long-term tracking.
  • Retro-hunting: Because trojanized installers retain legitimate functionality, endpoint posture alone won't reveal compromise. Hunt historically: query EDR telemetry for any host that executed TrueConf client installers during the campaign window, then compare installer hashes against the blocklist.
  • Tooling: Use THOR or Velociraptor for fleet-wide hash sweeps; YARA rules from the vendor report for memory-resident detection; your SIEM lookup tables for network IoCs from the full pulse (domains/IPs beyond the hash sample shown here).
  • Supply chain scoping: Enumerate every TrueConf server your organization connects to — including partner-hosted servers. A clean internal server does not protect you from a compromised counterparty's server pushing a malicious client during a joint meeting.

Detection Engineering

YAML
---
title: Head Mare PhantomCore - Trojanized TrueConf Installer Execution
id: 9c4f2a1e-7b3d-4e8f-a2c1-6d5e8f9a0b11
status: experimental
description: Detects execution of TrueConf client installer that spawns unexpected child processes, indicative of the Head Mare trojanized installer delivering PhantomCore.
author: Security Arsenal Threat Intel
references:
    - https://ics-cert.kaspersky.com/publications/reports/2026/08/12/head-mare-exploits-vulnerabilities-in-trueconf-server-to-deliver-phantomcore-malware
date: 2026/09/20
logsource:
    category: process_creation
    product: windows
level: high
detection:
    selection_parent:
        ParentImage|contains:
            - '\trueconf'
        ParentImage|endswith:
            - 'setup.exe'
            - 'installer.exe'
            - '.msi'
    selection_suspicious_children:
        Image|endswith:
            - '\powershell.exe'
            - '\pwsh.exe'
            - '\cmd.exe'
            - '\rundll32.exe'
            - '\regsvr32.exe'
            - '\wscript.exe'
            - '\cscript.exe'
            - '\mshta.exe'
            - '\schtasks.exe'
            - '\reg.exe'
    condition: selection_parent and selection_suspicious_children
falsepositives:
    - Legitimate TrueConf installation scripts in managed enterprise deployments
tags:
    - attack.t1195.002
    - attack.t1059
---
title: Head Mare PhantomCore - Persistence via Fake Conferencing Updater
id: 2a8b3c4d-5e6f-4a1b-9c2d-8e7f0a1b2c33
status: experimental
description: Detects registry Run key or scheduled task persistence referencing video conferencing or updater naming conventions used by PhantomCore.
author: Security Arsenal Threat Intel
references:
    - https://ics-cert.kaspersky.com/publications/reports/2026/08/12/head-mare-exploits-vulnerabilities-in-trueconf-server-to-deliver-phantomcore-malware
date: 2026/09/20
logsource:
    category: registry_set
    product: windows
level: high
detection:
    selection_reg:
        TargetObject|contains:
            - '\CurrentVersion\Run'
            - '\CurrentVersion\RunOnce'
    selection_value:
        Details|contains:
            - 'trueconf'
            - 'confupdate'
            - 'confsvc'
            - 'meeting'
    filter_legit:
        Image|endswith:
            - '\TrueConf\Client\TrueConf.exe'
            - '\TrueConf.exe'
    condition: selection_reg and selection_value and not filter_legit
falsepositives:
    - Legitimate TrueConf autoupdate mechanisms (verify signed binary path)
tags:
    - attack.t1060
    - attack.t1547.001
---
title: Head Mare - Web Shell on TrueConf Server via Suspicious Child of Server Process
id: 7f1e2d3c-4b5a-4c6d-8e9f-0a1b2c3d4e55
status: experimental
description: Detects TrueConf server process spawning shells or scripting interpreters, consistent with post-exploitation and web shell deployment observed in the Head Mare campaign.
author: Security Arsenal Threat Intel
references:
    - https://ics-cert.kaspersky.com/publications/reports/2026/08/12/head-mare-exploits-vulnerabilities-in-trueconf-server-to-deliver-phantomcore-malware
date: 2026/09/20
logsource:
    category: process_creation
    product: windows
level: critical
detection:
    selection_parent:
        ParentImage|contains:
            - 'trueconf'
            - 'tcserver'
            - 'tc_'
    selection_child:
        Image|endswith:
            - '\cmd.exe'
            - '\powershell.exe'
            - '\pwsh.exe'
            - '\whoami.exe'
            - '\net.exe'
            - '\nltest.exe'
            - '\certutil.exe'
            - '\bitsadmin.exe'
    condition: selection_parent and selection_child
falsepositives:
    - Administrative maintenance scripts executed in server context (rare; investigate all hits)
tags:
    - attack.t1190
    - attack.t1505.003
    - attack.t1059
KQL — Microsoft Sentinel / Defender
// Head Mare PhantomCore hunt: trojanized TrueConf installer activity + persistence artifacts
let Lookback = 30d;
let IoCHashes = dynamic([
    "0e4541c3153ec5ed01497f19cf4f63d0",
    "0e79996d9483d1e44fea32b0a48c2c19",
    "129462164a7d52e9ea8560b60f0412c5",
    "12d4e8f5295f2ef7e0f9bfc0f4830939",
    "2bb75c20e778eb5c416965bd4d4259b1",
    "43f435c3c437bc879a2d7d4634f43494",
    "489f43be558b2679284ceabed7adc4f3",
    "4d27b4eb1c5dbb3d8160f29b8119523e"
]);
// Part 1: Any host that executed TrueConf installers, joined with IoC hash matches and suspicious child processes
let InstallerExec = DeviceProcessEvents
    | where TimeGenerated > ago(Lookback)
    | where FileName has_any ("trueconf", "setup.exe", "installer.exe") or ProcessCommandLine has "trueconf"
    | where MD5 in~ (IoCHashes) or SHA1 in~ (IoCHashes) or InitiatingProcessMD5 in~ (IoCHashes)
    | project TimeGenerated, DeviceName, FileName, ProcessCommandLine, MD5, SHA256, AccountName, InitiatingProcessFileName;
// Part 2: Suspicious child processes spawned by conferencing software
let SuspiciousChildren = DeviceProcessEvents
    | where TimeGenerated > ago(Lookback)
    | where InitiatingProcessFileName has_any ("trueconf", "tcserver")
    | where FileName in~ ("powershell.exe","pwsh.exe","cmd.exe","rundll32.exe","regsvr32.exe","wscript.exe","mshta.exe","schtasks.exe","reg.exe","certutil.exe")
    | project TimeGenerated, DeviceName, FileName, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessCommandLine, AccountName;
// Part 3: Network connections from TrueConf binaries to non-standard destinations
let SuspiciousNet = DeviceNetworkEvents
    | where TimeGenerated > ago(Lookback)
    | where InitiatingProcessFileName has_any ("trueconf", "phantom")
    | where RemoteIPType == "Public"
    | where not(RemoteUrl has_any ("trueconf.com", "trueconf.ru"))
    | project TimeGenerated, DeviceName, InitiatingProcessFileName, RemoteIP, RemotePort, RemoteUrl;
union InstallerExec, SuspiciousChildren, SuspiciousNet
| sort by TimeGenerated desc
PowerShell
# Head Mare / PhantomCore endpoint hunt — run fleet-wide via EDR/Intune/GPO scheduled task
# Checks persistence, trojanized installer hashes, and suspicious network state
$ErrorActionPreference = 'SilentlyContinue'
$iocMD5 = @(
    '0e4541c3153ec5ed01497f19cf4f63d0','0e79996d9483d1e44fea32b0a48c2c19',
    '129462164a7d52e9ea8560b60f0412c5','12d4e8f5295f2ef7e0f9bfc0f4830939',
    '2bb75c20e778eb5c416965bd4d4259b1','43f435c3c437bc879a2d7d4634f43494',
    '489f43be558b2679284ceabed7adc4f3','4d27b4eb1c5dbb3d8160f29b8119523e'
)
$findings = @()

# 1) Hash sweep of TrueConf install/download locations
$paths = @("$env:ProgramFiles\TrueConf","${env:ProgramFiles(x86)}\TrueConf",
           "$env:LOCALAPPDATA\TrueConf","$env:TEMP","$env:USERPROFILE\Downloads")
foreach ($p in $paths) {
    if (Test-Path $p) {
        Get-ChildItem $p -Recurse -Include *.exe,*.msi,*.dll -ErrorAction SilentlyContinue |
            ForEach-Object {
                $h = (Get-FileHash $_.FullName -Algorithm MD5).Hash.ToLower()
                if ($iocMD5 -contains $h) {
                    $findings += [PSCustomObject]@{Type='IOC_HASH_MATCH'; Path=$_.FullName; MD5=$h}
                }
            }
    }
}

# 2) Persistence: Run keys referencing conferencing/updater naming
$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 ($k in $runKeys) {
    if (Test-Path $k) {
        (Get-Item $k).Property | ForEach-Object {
            $v = (Get-ItemProperty $k -Name $_).$_
            if ($v -match 'trueconf|confupdate|confsvc|meeting' -and $v -notmatch 'TrueConf\\Client\\TrueConf.exe') {
                $findings += [PSCustomObject]@{Type='PERSISTENCE_RUNKEY'; Path="$k\$_"; MD5=$v}
            }
        }
    }
}

# 3) Scheduled tasks masquerading as conferencing updaters
Get-ScheduledTask | Where-Object {
    $_.TaskName -match 'conf|meeting|trueconf' -and
    ($_.Actions.Execute -notmatch 'TrueConf\\Client' ) -and
    $_.Actions.Execute -match 'powershell|cmd|rundll32|regsvr32|wscript|mshta'
} | ForEach-Object {
    $findings += [PSCustomObject]@{Type='SUSPICIOUS_TASK'; Path=$_.TaskName; MD5=$_.Actions.Execute}
}

# 4) Active connections from TrueConf processes to public IPs
Get-NetTCPConnection -State Established |
    Where-Object { $_.RemoteAddress -notmatch '^(10\.|172\.(1[6-9]|2[0-9]|3[01])\.|192\.168\.|127\.)' } |
    ForEach-Object {
        $proc = Get-Process -Id $_.OwningProcess -ErrorAction SilentlyContinue
        if ($proc -and $proc.Path -match 'trueconf|phantom') {
            $findings += [PSCustomObject]@{Type='NETWORK_CONNECTION'; Path=$proc.Path; MD5="$($_.RemoteAddress):$($_.RemotePort)"}
        }
    }

if ($findings) { $findings | Format-Table -AutoSize; $findings | Export-Csv "$env:TEMP\headmare_hunt_$(hostname)_$(Get-Date -Format yyyyMMdd).csv" -NoTypeInformation }
else { Write-Output "[+] No Head Mare/PhantomCore artifacts found on $(hostname)" }

Response Priorities

Immediate (0-4 hours):

  • Block all 40 pulse IoCs (hashes, domains, IPs) at EDR, proxy, and DNS layers. Deploy SHA-256 equivalents from the Kaspersky report once obtained.
  • Inventory all TrueConf servers (internal and partner-connected); take unpatched servers offline or isolate them pending patch verification and web shell sweeps.
  • Retro-hunt every endpoint that installed or updated the TrueConf client in the past 90 days; hash-match installers against the IoC set.
  • Sweep TrueConf servers for web shells: unexpected files in web root directories, recently modified scripts, and anomalous child processes of the server service (use Sigma rule 3 above).

24 hours:

  • PhantomCore profiles host and domain data and may harvest credentials accessible on compromised endpoints. Force credential resets for all users who joined meetings hosted on suspect servers — prioritizing privileged and service accounts.
  • Review authentication logs for anomalous logons from affected endpoints; enable or verify MFA enforcement.
  • Check for lateral movement from confirmed-compromised hosts: SMB/RDP/WinRM authentication events in the 72 hours following installer execution.

1 week:

  • Establish a vendor software integrity verification process: hash-verify conferencing client downloads against vendor-published digests before enterprise deployment; route updates through an internal distribution point rather than direct server pulls.
  • Apply TrueConf vendor patches on a documented SLA; add conferencing servers to the internet-facing asset attack surface management program.
  • Segment conferencing infrastructure from the production LAN — a compromised meeting server should not reach domain controllers or file shares.
  • Add supply chain scenarios (trojanized client from a trusted partner server) to tabletop exercises and detection validation cycles.

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.