Hackers Reuse Malware Loader in International Campaigns
The persistent .NET loader confirms attackers are standardizing their infection chain across recent global phishing activity.
Updated on Oct. 28, 2026 in Cybersecurity

Live Poll
Do you trust your current digital security measures to protect you from sophisticated phishing campaigns?
Hackers are employing a reusable .NET malware loader across phishing campaigns, with recent activity in Colombia sharing a binary-identical tool to a September 2026 UK-linked case. These campaigns utilize obfuscated scripts and encrypted PowerShell to deliver XWorm malware.
Why it matters
The reuse of a consistent loader across geographically distinct campaigns suggests a standardized delivery infrastructure that persists even when attackers swap payload hashes and execution targets to evade detection.
The malware loader is a .NET-based binary that serves as the entry point for XWorm payloads. Analysts confirmed the loader recovered in October 2026 is binary-identical to one documented in a September 10, 2026, UK-linked case.
The players
XWorm
A modular remote access trojan that allows attackers to control infected systems, steal data, and deploy additional malicious software.
The details
The infection chain relies on obfuscated scripts—code masked to prevent static analysis—and encrypted PowerShell, which is an automated task runner, to execute the malicious file. By using a standardized .NET loader, attackers maintain a consistent bridgehead into systems while customizing the subsequent XWorm payload, a modular remote access trojan, to suit specific regional targets. This separation between the loader and the payload allows the threat actor to rotate unique payload hashes across different campaigns to avoid signature-based detection.
Timeline
September 10, 2026: The initial UK-linked case involving the identical loader is documented.
October 2026: Evidence of the reused loader appears in recent phishing campaigns targeting Colombia.
The Tech Race
This activity follows the pattern of modular malware distribution established in the September 2026 UK-linked case. It underscores the ongoing arms race between automated detection systems and actors who reuse foundational code to maintain persistent access.
Security teams should prioritize updating signature-based defenses to detect the specific .NET loader patterns rather than relying solely on payload hashes. Organizations in affected regions should expect continued attempts to gain unauthorized access via encrypted PowerShell scripts.
The takeaway
The persistence of a binary-identical loader confirms that attackers are optimizing their operational costs by standardizing core infection vectors. Security analysts should monitor for similar .NET loader signatures appearing in emerging phishing campaigns to identify repeat threat activity.
Further reading
For broader trends in threat actor infrastructure and code reuse, explore our Cybersecurity section.
Source note: This article includes information reported by IT Security News - cybersecurity, infosecurity news.
Live Poll
Do you trust your current digital security measures to protect you from sophisticated phishing campaigns?






