SecPod

Learn Search

Search across all Learn content

← Back to Security Research
NetamLoader Malware Targets Asian Government Windows 10 Systems Through Advanced .NET Injection

NetamLoader Malware Targets Asian Government Windows 10 Systems Through Advanced .NET Injection

NetamLoader is a multi-stage .NET malware loader targeting customized Windows 10 systems used by Asian government organizations. Discover its AppDomainManager injection techniques, XAML-based execution, AMSI bypass, encrypted command-and-control communications, indicators of compromise, and mitigation strategies.

Nov 2, 2026By Aditya Jha8 min read
malware research

NetamLoader Malware Targets Customized Windows 10 Systems Intended for Asian Government Entities

A previously unidentified threat actor deployed a sophisticated, multi-stage .NET malware-loading framework against a customized Windows 10 environment intended for government entities in Asia. The operation combined legitimate Microsoft-signed components, AppDomainManager injection, unsafe deserialization, XAML execution, defense evasion and encrypted command-and-control capabilities.

Security Research | Malware Analysis

Malware Family NetamLoader Multi-stage .NET malware loader
Target Environment Windows 10 Customized government-oriented build
Threat Attribution Unknown No confirmed association with a known APT
Observed Scope 1 Victim Reported through Kaspersky telemetry
AppDomainManager .NET Malware XAML Execution Unsafe Deserialization AMSI Bypass Encrypted C2

Overview

NetamLoader is a previously undocumented .NET assembly-loading framework discovered by Kaspersky during the first half of 2026. The malware was identified within a suspicious Windows Cabinet (CAB) archive stored in a Windows update-package directory on an affected system in Asia.

The investigation revealed that the malware exploited weaknesses in legitimate .NET configuration-processing and deserialization mechanisms. Rather than relying on an obviously malicious executable, the attack used a legitimate application together with a Microsoft-signed assembly to initiate an extensive chain of encrypted and compressed payloads.

The initial execution process involved PatchMyPC-ScriptRunner.exe, a legitimate component associated with the Patch My PC endpoint-management platform. Its accompanying configuration file caused the .NET runtime to initialize Microsoft.HostIntegration.Connectors.dll, a Microsoft-signed assembly.

The attackers abused the assembly's configuration-processing behavior to read attacker-crafted fabric.config and Resources.resx files. These resources eventually activated multiple XAML-based payloads and additional .NET loaders.

The final malware component was designed to collect host information, identify proxy settings, construct encrypted HTTPS requests and retrieve additional XAML instructions. It was configured to contact openaigpt4v[.]com. The published investigation describes this communication capability but does not conclusively establish a successful C2 exchange for the analyzed victim.

Key Finding: NetamLoader combines trusted software components, configuration-based execution hijacking, unsafe deserialization and layered XAML payloads to create a modular malware execution framework with sophisticated anti-analysis capabilities.
Attribution and Targeting: Kaspersky reported one victim in Asia. The operating system was identified as a custom Windows build intended for government entities. The available evidence does not independently confirm the organizational identity of the affected victim. The threat actor and original delivery route remain unknown.

Background

Government-oriented operating system deployments may include specialized software, administrative utilities and customized update-management mechanisms. These environments can create opportunities for attackers who understand how legitimate software handles configuration files and trusted dependencies.

NetamLoader came to light when Kaspersky Security Network detected a suspicious application configuration file employing AppDomainManager injection. The file was located inside a CAB archive under the Windows SoftwareDistribution directory.

The analyzed package contained legitimate Patch My PC components and Microsoft-signed assemblies. Most of the extracted files did not contain malicious executable code. Instead, the attacker-controlled resource file and the crafted configuration chain activated the malicious payload.

Files Found in the CAB Archive

File Function
fabric.config Attacker-crafted configuration used to direct resource loading
Microsoft.HostIntegration.Connectors.dll Microsoft-signed assembly whose configuration processing was abused
PatchMyPC-Enum.dll Legitimate supporting component
PatchMyPC-Models.dll Legitimate supporting component
PatchMyPC-ScriptRunner.exe Legitimate executable serving as the initial host
PatchMyPC-ScriptRunner.exe.config Configuration enabling AppDomainManager loading
Resources.resx Malicious serialized and encoded payload resource

The presence of legitimate software in the archive does not prove that Patch My PC or Microsoft distribution infrastructure was compromised. A supply-chain attack was suspected, but the initial delivery mechanism was not observed.

Technical Context: AppDomainManager is a legitimate .NET runtime mechanism. NetamLoader abused the initialization of a Microsoft-signed assembly and its handling of crafted configuration and resource files. The initial Microsoft-signed assembly was not itself an attacker-created binary.

Malware and Technique Details

⚙

AppDomainManager Injection

Redirects .NET application initialization into a Microsoft-signed assembly whose configuration-processing functionality is abused by the attacker.

{}

Unsafe Deserialization

Processes malicious serialized resource data through BinaryFormatter and TypeConfuseDelegate-based behavior.

▦

XAML Execution

Uses multiple XAML layers to decode, reconstruct and execute subsequent .NET payloads in memory.

⛔

Security Evasion

Implements AMSI bypasses, selected CLR telemetry suppression and forensic artifact cleanup.

⚙

COM Surrogate Execution

Executes a later XAML stage through a COM-related mechanism inside the legitimate dllhost.exe process.

⇄

Encrypted Remote Tasking

Implements HTTPS command-and-control requests protected using AES-128-CBC and HMAC-SHA256.

Technical Profile

Attribute Details
Malware Name NetamLoader
Malware Type Multi-stage .NET assembly loader
Target Environment Customized Windows 10 build intended for Asian government entities
Observed Victims One victim reported in Kaspersky telemetry
Threat Actor Unknown
Initial Artifact Windows Cabinet archive
Execution Mechanism AppDomainManager injection
Deserialization BinaryFormatter / TypeConfuseDelegate
Payload Technology XAML, .NET assemblies and JSON configuration
Execution Hosts PatchMyPC-ScriptRunner.exe, dllhost.exe
Defense Evasion AMSI bypass, CLR telemetry suppression and artifact removal
C2 Domain openaigpt4v[.]com
Communication Security AES-128-CBC and HMAC-SHA256
Certificate Configuration Wildcard trusted certificate thumbprint tp: "*"
Associated CVE No specific published CVE identified

NetamLoader's attack chain includes unsafe deserialization weaknesses and configuration-processing abuse. Although these behaviors involve security weaknesses, the published investigation did not assign a specific CVE to the observed attack. Therefore, no campaign-wide CVSS or EPSS score is provided.

Visual Attack Flow

The following diagram summarizes the reported malware execution chain, from the suspicious update-package archive through .NET resource loading, XAML execution, defense evasion and the final remote-tasking functionality.

NETAMLOADER: MULTI-STAGE EXECUTION ARCHITECTURE Configuration-driven loading and layered XAML execution
STAGE 1: INITIAL EXECUTION
01

Suspicious Windows Update CAB Archive

The package contains legitimate components, a crafted .NET application configuration and malicious resource material.

Initial delivery mechanism not observed
↓
02

Patch My PC Application Startup

PatchMyPC-ScriptRunner.exe starts and processes its associated .NET application configuration.

Legitimate execution host
↓
03

Microsoft-Signed Assembly Initialization

AppDomainManager initialization loads Microsoft.HostIntegration.Connectors.dll. Its configuration-processing functionality reads attacker-crafted fabric.config and Resources.resx.

T1574.014: AppDomainManager
↓
STAGE 2: PAYLOAD RECONSTRUCTION AND EXECUTION
04

Resource Deserialization

The malicious resource is parsed using unsafe BinaryFormatter deserialization and associated XAML execution techniques.

BinaryFormatter / TypeConfuseDelegate / XamlReader
↓
05

Multi-Layer XAML Payload Loading

XAML-1 and XAML-2 reconstruct additional encrypted and compressed components, including XAML-2-1, XAML-2-2 and the first .NET loader.

Encoded and encrypted payloads
↓
06

AMSI Bypass and Artifact Cleanup

The malware attempts to suppress security scanning, remove selected forensic artifacts and interfere with CLR telemetry.

Defense impairment and anti-forensics
↓
07

Administrative Privilege Check

The first .NET loader verifies that its execution context has administrative privileges before proceeding with subsequent stages.

Execution precondition, not privilege escalation
↓
STAGE 3: FINAL PAYLOAD AND REMOTE TASKING
08

Execution Inside dllhost.exe

A subsequent XAML stage loads inside the legitimate Windows COM surrogate process, where the final .NET plugin is initialized.

COM-related execution mechanism
↓
09

Configured Encrypted C2 Communication

The plugin is configured to collect environment information, identify proxy settings and construct encrypted requests to openaigpt4v[.]com.

HTTPS / AES-128-CBC / HMAC-SHA256
↓
10

Remote XAML Task Execution

The implemented framework can retrieve additional XAML instructions and execute them inside isolated .NET AppDomains.

Remote task execution capability
Delayed Command-and-Control Logic

The framework uses configurable waiting periods and conditional polling intervals to reduce frequent network activity. These intervals are part of the malware's analyzed code and configuration.

C2 Timing Behavior

20 to 40 min Initial Connection Delay
5 to 6 min Shorter Polling Interval
22 to 28 hrs Long Retry Interval

These timing values describe the malware's implemented configuration and code behavior. They are not proof that a successful C2 session occurred on the observed system.

Attack Methodology (NetamLoader Infection Chain)

PHASE 01: INITIAL ARTIFACT

Suspicious Windows Update Package

A suspicious CAB archive was discovered under the Windows SoftwareDistribution directory. It contained legitimate application files, an attacker-crafted configuration and the malicious Resources.resx resource. The original delivery method could not be established.

PHASE 02: INITIAL EXECUTION

Application Configuration Abuse

When PatchMyPC-ScriptRunner.exe started, the .NET runtime processed the accompanying configuration file. The configuration specified an AppDomainManager implementation in the Microsoft-signed Microsoft.HostIntegration.Connectors.dll assembly.

PHASE 03: CONFIGURATION PROCESSING

Malicious Resource Loading

The Microsoft-signed assembly's configuration-processing behavior was abused through an attacker-crafted fabric.config file. This configuration caused a resource parser to process Resources.resx, which contained malicious serialized data and embedded payload layers.

PHASE 04: UNSAFE DESERIALIZATION

BinaryFormatter and XAML Execution

The malicious resource contained Base64-encoded serialized data. The loading chain abused unsafe BinaryFormatter deserialization and TypeConfuseDelegate behavior to initiate XAML-based execution. This activated the initial XAML payload stage.

PHASE 05: PAYLOAD RECONSTRUCTION

Multiple Encrypted XAML Layers

XAML-1 loaded the subsequent XAML-2 stage, which reconstructed additional components identified as XAML-2-1 and XAML-2-2. These stages implemented security-evasion behavior and prepared encrypted .NET payloads and JSON configuration data for further execution.

PHASE 06: DEFENSE IMPAIRMENT

AMSI Bypass and Telemetry Suppression

The malicious components attempted to interfere with Antimalware Scan Interface functionality and selected .NET runtime telemetry. The loader also performed cleanup operations targeting extracted malicious files, CLR usage logs and Windows Prefetch artifacts.

PHASE 07: EXECUTION PRECONDITION

Administrative Privilege Verification

The first .NET loader checked whether the current execution context had administrator privileges. If the required privileges were not available, the loader could terminate the relevant execution path by throwing an exception. This was a prerequisite check, not an observed privilege-escalation technique.

PHASE 08: PROCESS EXECUTION

COM-Related Execution Inside dllhost.exe

The loading chain constructed another XAML stage and activated execution through a COM-related mechanism. The subsequent payload ran inside dllhost.exe and loaded the final .NET plugin. The chain also involved deserialization-related weaknesses in its COM execution mechanism.

PHASE 09: C2 INITIALIZATION

Environment Profiling and Encrypted Communication

The final .NET plugin was designed to query Windows and .NET version information, identify proxy configuration and construct encrypted HTTPS requests. The analyzed configuration contained the domain openaigpt4v[.]com. The implementation used AES-128-CBC encryption and HMAC-SHA256 authentication.

PHASE 10: REMOTE TASKING

Downloaded XAML Execution and Polling

The malware framework implemented functionality for retrieving additional XAML payloads and executing them in isolated .NET AppDomains. Long waiting intervals were configured to limit repeated network activity. The published research did not conclusively establish the final downstream objectives or a successful C2 exchange with the victim.

Indicators of Compromise (IOCs)

The following indicators and host artifacts are associated with the published NetamLoader analysis. Network addresses are defanged to prevent accidental navigation.

Network Indicators

Type Indicator Description
C2 Domain openaigpt4v[.]com Configured command-and-control infrastructure
C2 URL Prefix hxxps://openaigpt4v[.]com/model_v4/ Base path used to construct HTTPS requests containing an instance identifier and query parameters
Associated IP 104.18.14[.]219 Shared CDN infrastructure address associated with the reported domain. Not suitable as a standalone malicious-IP indicator

File Hash Indicators (MD5)

Artifact MD5 Hash
CAB Archive F2458ED133F8D0CA19E22C10F577E98E
Resources.resx E1DC6F1ED193594F2284BE22AE08DFA4
.NET 1 Loader AB81564BCB8CA7E710C66832DE747556
.NET 2 Plugin CFB8B281BDF5D9390E64B10C312FB2C1
fabric.config 67E3617F8709D34F806F8E02BADBA8A5
PatchMyPC-ScriptRunner.exe.config 514AC0D73B8A1B73488EF5E2E55A75C3
XAML-1 514117D536E347560D049CFE0C609632
XAML-2 9000820D8153C24CD60D53001D3A97B6
XAML-2-1 B3C4A635179680EDAFB5D006CF0CFFC6
XAML-2-2 4F28622C5E60C01319BF48CF742FE1A5
XAML-3 C86D53392A87DD3F3E62D62C9B92A9BD

Reported File Locations

Artifact Location
CAB Archive C:\Windows\SoftwareDistribution\Download\e4537a1762fcafd2fd96bfc825bad34f9db9a24d
Application Configuration C:\Windows\SoftwareDistribution\Download\Install\PatchMyPC-ScriptRunner.exe.config
Loader Configuration C:\Windows\SoftwareDistribution\Download\Install\fabric.config
Malicious Resource C:\Windows\SoftwareDistribution\Download\Install\Resources.resx

Behavioral Detection Opportunities

AppDomainManager Configuration Changes

Unexpected .NET configuration entries such as appDomainManagerAssembly and appDomainManagerType in software-management directories.

Unsafe Resource Deserialization

Suspicious serialized data, runtime XAML parsing and unusual assembly-loading behavior associated with application resources.

Unusual dllhost.exe Activity

Unexpected .NET assembly loading, abnormal process relationships or suspicious outbound network activity from COM surrogate processes.

Telemetry Interference

AMSI bypass behavior, changes to COMPlus_ETWEnabled and deletion of CLR usage logs or selected Prefetch artifacts.

IOC Interpretation: Legitimate Windows filenames, Microsoft-signed assemblies and shared hosting infrastructure IP addresses are not sufficient to establish malicious activity. Correlate them with known malicious hashes, configuration anomalies, suspicious execution and network evidence.

MITRE ATT&CK Coverage

The following MITRE ATT&CK techniques map to the behavior described in the NetamLoader research. These mappings represent analytical classifications rather than attribution to a specific named threat group.

Technique ID Technique Name Tactic
T1574.014 Hijack Execution Flow: AppDomainManager Execution / Stealth
T1218 System Binary Proxy Execution Stealth
T1027 Obfuscated Files or Information Stealth
T1620 Reflective Code Loading Stealth
T1685 Disable or Modify Tools Defense Impairment
T1070.004 Indicator Removal: File Deletion Stealth
T1012 Query Registry Discovery
T1071.001 Application Layer Protocol: Web Protocols Command and Control
T1573.001 Encrypted Channel: Symmetric Cryptography Command and Control
T1105 Ingress Tool Transfer Command and Control
N/A Initial Access: Not documented Initial Access
N/A Persistence mechanism not confirmed Persistence
N/A No privilege escalation technique documented. Administrative privileges were checked, not obtained by the malware. Privilege Escalation
N/A Credential theft not documented Credential Access
N/A Lateral movement not documented Lateral Movement
N/A Data collection beyond host profiling not confirmed Collection
N/A Data exfiltration not confirmed Exfiltration
N/A Destructive or disruptive impact not documented Impact

N/A indicates that no applicable technique was established by the available investigation for that tactic. It does not imply that the threat actor lacked the capability. The command-and-control mappings describe implemented malware functionality, not independently confirmed successful communication.

Mitigation & Recommended Actions

Organizations operating sensitive Windows environments should prioritize software integrity validation, configuration monitoring, runtime detection and controlled network communications. The following measures address techniques associated with NetamLoader's loading framework.

CRITICAL PRIORITY

Validate Software Update Integrity

Verify update-package origins, digital signatures and file integrity. Monitor unexpected configurations and resource files within trusted software-management directories. Investigate suspicious CAB archives and unauthorized modifications to deployment workflows.

CRITICAL PRIORITY

Detect AppDomainManager Injection

Monitor unexpected .NET application configuration changes, especially entries defining appDomainManagerAssembly or appDomainManagerType. Correlate configuration changes with assembly-loading events and trusted process execution.

HIGH PRIORITY

Monitor Unsafe Deserialization and XAML Execution

Investigate suspicious BinaryFormatter deserialization, unusual XAML parsing, runtime assembly loading and encoded resource contents. Review applications that process untrusted serialized data.

HIGH PRIORITY

Strengthen Endpoint Defense Monitoring

Detect attempts to interfere with AMSI, CLR telemetry and endpoint-security components. Alert on suspicious artifact deletion, unexpected process execution and abnormal activity inside dllhost.exe.

HIGH PRIORITY

Restrict Unauthorized Outbound Communications

Monitor the reported C2 domain openaigpt4v[.]com and investigate unexpected outbound traffic from software-management or COM surrogate processes. Apply DNS filtering, network segmentation and egress restrictions.

HIGH PRIORITY

Enforce Application Control and Least Privilege

Restrict unauthorized executable and assembly loading. Review administrative privileges granted to update-management processes and apply controlled software execution policies where operationally feasible.

MEDIUM PRIORITY

Maintain Supported Windows and .NET Components

Apply security updates to Windows, .NET runtime components and endpoint-management applications. Patching should be combined with behavior-based monitoring because no publicly identified CVE has been associated with the analyzed NetamLoader attack chain.

HIGH PRIORITY

Conduct Threat Hunting and Forensic Investigation

Search for reported malicious hashes, suspicious application configurations, unexpected resource deserialization, abnormal dllhost.exe execution and related network indicators. Preserve relevant logs and forensic artifacts before remediation.

Defensive Priority: The most valuable controls against NetamLoader involve identifying abnormal .NET configuration loading, unsafe resource deserialization, XAML payload execution, security telemetry interference and suspicious outbound communications. These measures help reduce exposure even when no publicly identified CVE has been associated with the attack.

Instantly Fix Risks in Endpoints & Cloud with Saner

Saner is a continuous and integrated vulnerability & exposure management platform that instantly fixes risks in endpoints and cloud.

Featured Posts

Open Agentic AI in the Wild: How AI-Driven Attacks Are Changing Vulnerability Management
Agentic AI in the Wild: How AI-Driven Attacks Are Changing Vulnerability Management

CVE Research

Agentic AI in the Wild: How AI-Driven Attacks Are Changing Vulnerability Management

Oct 30, 2026

Open WARP PANDA Weaponizes VMware ESXi Zero-Day Logging Gap to Evade Audit Visibility
WARP PANDA Weaponizes VMware ESXi Zero-Day Logging Gap to Evade Audit Visibility

CVE Research

WARP PANDA Weaponizes VMware ESXi Zero-Day Logging Gap to Evade Audit Visibility

China-nexus threat actor Warp Panda exploited an insufficient logging zero-day in VMware ESX (CVE-2026-41709) to blind audit visibility, deploying BRICKSTORM malware and hijacking Microsoft 365 accounts across targeted U.S. legal networks

Oct 30, 2026

Open Cisco Firewall Zero-Day Under Attack: Hackers Exploit SSL VPN Flaw to Crash ASA and FTD Devices
vulnerability researchCisco Firewall Zero-Day Under Attack: Hackers Exploit SSL VPN Flaw to Crash ASA and FTD Devices

CVE Research

Cisco Firewall Zero-Day Under Attack: Hackers Exploit SSL VPN Flaw to Crash ASA and FTD Devices

Oct 30, 2026

Open PolyShell: Critical Magento Flaw Allows Unauthenticated RCE, Exploited Since March 2026
vulnerability researchPolyShell: Critical Magento Flaw Allows Unauthenticated RCE, Exploited Since March 2026

CVE Research

PolyShell: Critical Magento Flaw Allows Unauthenticated RCE, Exploited Since March 2026

CVE-2026-48356 is a critical unrestricted file upload vulnerability in Adobe Commerce and Magento Open Source. Unauthenticated attackers can submit polyglot files through guest-cart REST item routes and write them under pub/media/custom_options/. When the web server executes or serves that path as PHP, the result can be remote code execution or stored XSS. Mass exploitation has been observed since March 2026, including links to CMS-block loaders on hundreds of stores. The issue is listed in the CISA KEV catalog. This article covers how the flaw works, campaign activity, indicators of compromise, affected and fixed versions under APSB26-73, and practical remediation steps.

Oct 29, 2026