MATCHBOIL’s evolution and practical cybersecurity defenses
A downloader’s job can be simple and still demand close attention. ESET Research’s examination of MATCHBOIL samples from April 2024 to April 2026 shows UAC-0099 repeatedly modifying a tool whose core purpose has remained stable: fetch another payload, install it, and keep it running. The report describes changes in code structure, obfuscation, persistence, and execution. It does not attribute MATCHBOIL’s development or operation to AI.
That distinction is worth stating plainly. The findings support a discussion of malware evolution and defensive priorities, not an AI-driven attack narrative. The technical detail is useful precisely because it shows how ordinary components can be adapted over time. (Source: ESET Research.)
What ESET says about UAC-0099
ESET characterizes UAC-0099 as a cyberespionage group active since at least 2022. The group targets Ukrainian government organizations, financial institutions, and media; based on that targeting, ESET assesses with medium confidence that it is aligned with Russian interests. Researchers also say it can act as an initial-access broker for Sandworm. MATCHBOIL is one part of its toolkit; another downloader associated with the group is LONEPAGE.
ESET’s telemetry linked observed MATCHBOIL victims to Ukraine. The report describes samples seen at transportation companies from July to August 2025, a manufacturing company in December 2025, and an energy-sector company in June 2026. These are the observations in ESET’s telemetry, not a complete victim list or proof that the campaign was confined to those sectors. Attribution and scope should stay no broader than the evidence.
Dark Reading also reported on UAC-0099 and MATCHBOIL’s changing capabilities. The technical chronology and victim observations discussed here are drawn from ESET’s research. (Sources: ESET Research; Dark Reading.)
How MATCHBOIL reaches a system
ESET describes a spear-phishing delivery chain. A malicious link leads to an archive containing a VBScript file; the script downloads and executes MATCHBOIL. The user must be persuaded to run the script manually for the described sequence to proceed. That human step is a practical place for defenders to focus, though it should not be mistaken for the only possible route in every incident.
At runtime, MATCHBOIL checks for a sample-specific directory under %LOCALAPPDATA%. If that directory already exists, it terminates. It gathers information about the machine, including CPUID and BIOS serial number, to identify the victim during command-and-control communication. Later versions gathered further system details.
ESET describes three HTTPS requests to the command-and-control server. The first returns a numeric value used in a header in the second request. The response to that request contains code from which a sample-dependent regular expression extracts a hex-encoded payload; MATCHBOIL decodes it. A third request returns a string saved beside the installed payload, which ESET says is most probably a configuration file. In most analyzed cases, that payload was MATCHWOK, a C# backdoor that ESET says is used exclusively by UAC-0099 and was previously documented by CERT-UA.
This sequence gives incident responders a map of the downloader’s broad behavior, not a universal signature. ESET notes that headers, patterns, directory names, and other details can vary among samples. (Source: ESET Research.)
What changed between 2024 and 2026
The earliest samples ESET analyzed date to April 2024. They used obfuscated class and method names, encrypted strings, and a custom decryption routine. In 2024, MATCHBOIL was a one-shot downloader: it installed a payload and relied on persistence mechanisms to run it.
The July 2025 samples introduced asynchronous task execution, so each network request waited for the previous one to finish. These versions also collected more machine information for an HTTP header. ESET reports Run-key registry persistence and execution of the installed payload through a Win32_Process object created via ManagementClass.
Samples from late 2025 added more substantial changes. MATCHBOIL could run on a two-minute timer and retrieve a newer payload, rather than downloading only once. ESET also observed sandbox checks and a graphical interface displayed when a user ran the payload. Some later changes made that interface less conspicuous. The researchers document a move toward .NET Reactor obfuscation as well as changing persistence methods.
By April 2026, a sample used a date check and installed its payload under %LOCALAPPDATA%\SMTPClient as SMTPClientApplication.exe; its persistence used a scheduled task named Checker under MailClient. ESET contrasts this comparatively ordinary-looking filename with a more conspicuous name used in late 2025. Other logic, including collection of victim information and extraction of payload data, remained largely unchanged.
The pattern is steady iteration, not a new malware mission. ESET concludes that the changes reflect operator interest in improving MATCHBOIL, including to avoid detection and preserve it as a useful part of the group’s toolkit. The research identifies no AI system or process behind that work. (Source: ESET Research.)
Defensive priorities drawn from the findings
Start with the delivery behavior. Unexpected email links that lead to archives and scripts deserve scrutiny, especially when a user is asked to run a script manually. Clear reporting paths and controls on unnecessary script execution can reduce exposure, but neither replaces endpoint monitoring or a tested incident process.
Look for behaviors in combination. Script-launched downloads, unusual activity under %LOCALAPPDATA%, new Run-key entries or scheduled tasks, and repeated outbound HTTPS requests are reasonable investigation leads based on ESET’s account. None is unique to MATCHBOIL. A suspicious task or encrypted web connection alone does not establish compromise; correlate endpoint, identity, and network evidence before drawing conclusions.
The version history is a warning against relying on a single static indicator. Persistence shifted between registry entries and scheduled tasks; filenames and directories changed; and the later timer-based behavior altered how the downloader could retrieve payloads. Defenders should review both relevant autorun locations and scheduled-task activity, and should be prepared for variations rather than treating one observed filename as definitive.
ESET reports that UAC-0099 used virtual private servers such as BitLaunch for command-and-control hosting and cloud services such as Cloudflare to hide servers. The analyzed infrastructure used HTTP and HTTPS; TLS certificates were generated with Let’s Encrypt and were not reused on other domains. These observations can inform threat hunting, but infrastructure details can change and should not be treated as durable blocklists. (Source: ESET Research.)
A measured reading of the campaign
MATCHBOIL matters because ESET documents sustained refinement across two years while the downloader’s fundamental role stayed recognizable. Changes to obfuscation, persistence, sandbox checks, and payload retrieval make it a moving target for defenders. The responsible response is to monitor behavior, investigate the chain from delivery to persistence, and keep confidence levels explicit when describing attribution.
There is no basis in ESET’s reporting for saying AI developed or operated MATCHBOIL. The evidence points to UAC-0099’s continuing malware work and to practical defensive questions about scripts, persistence, and staged downloads. That’s enough to take seriously without adding claims the research doesn’t make.
matchboils evolution and practical cybersecurity defenses