As reported by The Hacker News, the threat actor known as Head Mare has resurfaced with a sophisticated supply-chain-style attack campaign, exploiting unpatched TrueConf Server vulnerabilities to replace legitimate client installers with the PhantomCore remote access trojan. Detections reported by Kaspersky in July 2026 confirm this group continues to evolve its tradecraft with alarming speed.

Threat Intelligence: As reported by The Hacker News, the threat actor known as Head Mare has resurfaced with a sophisticated supply-chain-style attack campaign, exploiting unpatched TrueConf Server vulnerabilities to replace legitimate client installers with the PhantomCore remote access trojan.

Why This Attack Pattern Is Especially Dangerous

What makes this campaign particularly insidious is the abuse of a trusted software distribution channel. TrueConf is a widely deployed enterprise video conferencing and collaboration platform. When employees download what appears to be a legitimate client installer from their own organization's server, they have virtually no reason to question its integrity. This is not a phishing lure that trained employees might spot — it is a weaponized update pipeline that bypasses nearly every layer of user awareness training.

This technique mirrors tactics seen in high-profile supply chain compromises globally, but here the attacker doesn't need access to an upstream vendor. They only need to compromise the on-premises server and let the organization's own infrastructure do the rest. That distinction matters enormously for defenders.

Who Is Head Mare?

Head Mare is a threat actor assessed to operate with motivations aligned against Russian and Commonwealth of Independent States (CIS) targets, making this campaign unusual in its geographic focus. The group has demonstrated persistent interest in the Russian industrial, energy, and technology sectors — all of which rely heavily on collaboration infrastructure like TrueConf. Their repeated exploitation of the same platform suggests either a strategic focus on high-value targets in these verticals or continued success finding unpatched deployments.

The Broader Supply Chain Risk

This incident underscores a systemic risk that organizations across all sectors face: on-premises software distribution servers are frequently overlooked in patch and hardening programs. These servers are often treated as infrastructure rather than attack surface, yet they sit in a position of extraordinary trust within a network. A compromised update or installer server can achieve lateral movement and initial access simultaneously, at scale, across an entire organization.

Organizations that self-host collaboration or endpoint management platforms must treat those servers with the same rigor as internet-facing web applications — because the threat actors already are.

PhantomCore: What Defenders Need to Know

PhantomCore is a capable remote access trojan previously attributed to Head Mare operations. Its deployment via poisoned installers means it may arrive on endpoints with user-level or even elevated privileges, depending on how the installer is executed. Organizations should expect PhantomCore to enable persistent access, credential harvesting, and staging for follow-on ransomware or data exfiltration operations — consistent with Head Mare's observed post-compromise behavior.

Vulnerability Details

Affected Vendor
TrueConf (on-premises server deployments)
Attack Type
Chained vulnerability exploitation enabling installer replacement / supply chain poisoning
Payload
PhantomCore RAT
Exploitation Status
Actively exploited in the wild (confirmed July 2026)
Targeted Sectors
Instrumentation, electronics, transport, energy, IT, and software development
Patch Availability
Ensure TrueConf Server is updated to the latest available version; consult the official TrueConf security advisory

Shield53 Recommendations

Immediate Actions

Vulnerability Details
Patch TrueConf Server immediately. Any unpatched TrueConf Server deployment should be treated as potentially compromised until fully updated and audited.
Audit installer integrity. Verify the cryptographic hash of all TrueConf client installers currently hosted on your infrastructure against vendor-published hashes. Do not trust cached or previously distributed packages.
Isolate and forensically examine TrueConf servers. If you cannot confirm your server was not exposed during the vulnerable window, conduct a full forensic review before returning it to service.
Hunt for PhantomCore indicators. Engage threat hunting teams to search for PhantomCore IOCs across endpoints that received TrueConf installer packages in recent months. Kaspersky's published research is a primary IOC source.
Enable binary/installer signing validation. Where possible, enforce code signing verification for all software installers before execution, using application control solutions (e.g., Windows Defender Application Control, AppLocker).

Strategic Controls

  • Apply network segmentation to isolate software distribution and collaboration servers from direct end-user workstation access where feasible.
  • Implement file integrity monitoring (FIM) on directories where installer packages are stored on distribution servers.
  • Review privileged access to collaboration platform administration consoles — these are high-value targets for initial access.
  • Ensure EDR solutions are deployed and active on all endpoints, with behavioral detection rules tuned for RAT-like activity including unusual outbound connections following software installations.

Head Mare's repeated success exploiting TrueConf infrastructure is a clear signal: patch cycles for on-premises collaboration tools cannot be treated as low priority. For organizations in energy, transport, and industrial sectors especially, the consequences of a persistent RAT foothold extend far beyond data theft.