Kaspersky Uncovers NetamLoader, a Malware Framework Hiding Inside Trusted Windows Update Components

It sits idle for 20 to 40 minutes before reaching out
NetamLoader's delay before contacting attacker servers makes short-window network monitoring unreliable.
Mark

Start with the basics. What actually did Kaspersky find?

Mimi

A compressed archive in the Windows update folder of a PC running a customized Windows 10 setup used by some Asian government agencies. It held genuine Patch My PC components and Microsoft-signed modules, with some helper files altered to load malicious commands.

Mark

Why does that combination matter?

Mimi

Because everything looks trustworthy. A legitimate program loads the bad code, so checking whether each file is genuine isn't enough. Kaspersky's point is that you have to examine how components interact.

Luke

Before we get carried away, how many systems are we talking about?

Mimi

Kaspersky confirmed one compromised system through its own monitoring network.

Luke

So claims about broad government targeting rest on one confirmed machine. And who's behind it?

Mimi

Unknown. Kaspersky has no direct evidence tying it to a specific group.

Mark

And the Patch My PC question? The archive was in the update folder.

Mimi

That suggests a possible supply chain attack, but researchers found no sign that Patch My PC or its distribution system was compromised. The entry route is also unconfirmed.

Luke

Worth stressing that the supply chain angle is a possibility raised by the folder location, not a finding.

Mark

What about the waiting period?

Mimi

It idles 20 to 40 minutes before contacting the attacker's server, and it can delete some update-related records. That frustrates short-window network monitoring and makes tracing harder, which is why Kaspersky advises storing logs separately.

  • A file that looked at home in a Windows update folder drew scrutiny, and what it carried was NetamLoader, a previously unseen framework hiding inside legitimate components.
  • Signed Microsoft modules and Patch My PC tools were quietly altered so trusted programs would load malicious commands when they ran.
  • The malware waits 20 to 40 minutes before calling home and can erase update-related logs, making it hard to catch in a short monitoring window.
  • Kaspersky has confirmed one compromised system but has no direct link to a specific hacking group and has not found how the file arrived.
  • Researchers stress that Patch My PC's distribution has shown no confirmed compromise, so the supply-chain question stays open while defenders are urged to verify update origins and keep logs off-device.

On a government-run customized Windows machine in Asia, an ordinary-looking archive tucked into a software update folder turned out to hide something more deliberate. Kaspersky's researchers have named the framework NetamLoader and traced how it borrows the credibility of legitimate, signed software to stay out of sight. As with many quiet intrusions, the question that matters most is not only what the malware does, but how trust itself was walked through the door, and that answer is still unknown.

The first sign was a compressed file sitting in the Windows update folder of a PC in Asia. It looked like it belonged there, and that was what made it worth a closer look. The machine ran a customized Windows 10 setup of the kind some government agencies in the region operate, and inside the archive Kaspersky's researchers found legitimate software parts, some of which had been quietly turned into weapons.

Kaspersky's Global Research and Analysis Team, known as GReAT, named the new framework NetamLoader. The archive held components of the patch management tool Patch My PC, along with modules carrying valid Microsoft signatures. The attackers had altered auxiliary files so that the trusted program, once running, would load malicious commands.

The design is built around concealment. NetamLoader waits 20 to 40 minutes before contacting its external server for further code, which defeats short-window traffic monitoring. It can also delete certain update-related records, erasing traces of its activity. Kaspersky has confirmed one compromised system through its own monitoring network, but it cannot yet tie the campaign to a specific group, explain how the file first arrived, or point to any compromise of Patch My PC or its distribution.

Sergey Lozhkin, who leads GReAT's Asia-Pacific and META research center, placed the case in a broader context. Many governments now prioritize technological sovereignty, and building their own operating systems is often the first step. Control over the platform brings the responsibility of protecting every layer, from the update path to the maintenance tools. Checking whether each program is legitimate is not enough, he argued; defenders must also examine how components interact.

Kaspersky's advice follows that logic: inspect unusual files in update folders, verify the origin of update packages, watch legitimate programs for abnormal execution and external connections, and store logs separately so activity can be traced even if local records are wiped. The industry expects attacks that combine signed modules with trusted programs to grow, and for now the central questions remain how the file got in, who sent it, and whether any vendor's distribution was touched.

The first sign was a compressed file sitting in the Windows update folder of a PC in Asia. It looked like it belonged there, and that is what made it worth a closer look. The machine ran a customized Windows 10 configuration of the kind some government agencies in the region operate. Inside the archive, Kaspersky's researchers found a bundle of legitimate software parts, and some of them had been quietly turned into weapons.

Kaspersky said on the 16th that its Global Research and Analysis Team, known as GReAT, had identified a previously unseen malware framework and named it NetamLoader. The investigation began in the first half of this year. The archive held components of the third-party patch management tool Patch My PC, along with modules carrying valid digital signatures from Microsoft. The attackers had altered some of the auxiliary files so that the legitimate program, when it ran, would load malicious commands.

The design leans heavily on concealment. NetamLoader does not act the moment it runs. It sits idle for 20 to 40 minutes before reaching out to an external server controlled by the attackers to fetch further commands and malicious code. That pause makes it hard to catch by watching network traffic for a short window. The framework can also delete certain Windows update-related records, wiping traces of what it did. Kaspersky's analysis describes it as built with several layers of hiding to slip past antivirus programs. Critics note that security tools which trust update paths will struggle to flag it.

Much remains unknown. Kaspersky confirmed one compromised system through its own threat monitoring network, but it does not yet have direct evidence tying the attack to any specific hacking group. The route by which the malicious file first reached the machine has not been established either. And the researchers found no evidence that Patch My PC, or the distribution system for the relevant software, was actually compromised.

The archive's location in the update folder raises the possibility of a supply chain attack, in which malware travels through the legitimate distribution channels of trusted vendors, a method that individual organizations have trouble blocking alone. The researchers were careful to draw a line here: possible, but no sign of compromise of the distribution system itself has been confirmed.

The malware was also built to match the customized operating system environment of the targeted agency. Sergey Lozhkin, who heads GReAT's research center for Asia-Pacific and the Middle East and Africa, pointed to the context. Many governments now treat "technological sovereignty," meaning less reliance on foreign technology, as a top priority, and building their own operating systems is often where that begins. Running your own platform gives control over the system, he said, but it also brings the heavy responsibility of protecting the whole ecosystem without gaps, from the update path to the maintenance tools the platform depends on. Such an ecosystem, he added, takes time to mature. In his view the case shows that checking whether each program is legitimate is not enough; defenders must also examine how multiple components interact.

Kaspersky's recommendations follow from that. Inspect unusual executable and configuration files inside software update folders, and verify the origin of update packages. Analyze abnormal code execution by legitimate programs together with their connections to external servers. Keep system logs in a separate repository so activity can still be traced if attackers delete local records.

The security industry worries that attacks combining legitimately signed modules with legitimate programs may become more common, and that checking individual files for integrity will not be enough to stop them. Demand is expected to grow for organizations to treat the update path itself as part of the threat model and to monitor continuously how components interact. For now, the open questions are how the file got in, who sent it, and whether any vendor's distribution was touched.

Operating one's own platform secures control over the system, but it carries the heavy responsibility of protecting the entire ecosystem without gaps, from the update path to maintenance tools.
— Sergey Lozhkin, head of Kaspersky GReAT's Asia-Pacific and META research center
Contattaci Domande frequenti