Hacks & Data Breaches NewsBadger[M]

Kaspersky reports NetamLoader malware targeting government Windows systems in Asia

Kaspersky researchers have reported a previously unknown malware, called NetamLoader, found on a Windows system used by government agencies in Asia. The finding matters because the malware abuses legitimate Microsoft-signed components and a third-party update tool to run code and hide activity, and researchers suspect a supply-chain attack. Kaspersky said it detected the malware on one computer in the first half of 2026.
Source: https://therecord.media/hackers-target-government-windows-systems-asia-new-malware
Feed publication: 2026-10-30 12:36 UTC

Details
According to the report, the malware was found inside a package in a directory used for Windows operating system updates, and the package included files belonging to the update management tool Patch My PC as well as programs digitally signed by Microsoft. Once active, NetamLoader could reportedly interfere with security scanning, conceal itself, delete files and system logs, gather information about the infected machine, download further malicious code and communicate with attacker infrastructure over encrypted connections. Kaspersky said the attack appeared tailored to a specialized Windows 10 version used only by government organizations in Asia, but it did not name the country or agency, and the number of affected systems remains unclear. The firm said it could not tie the operation to any known state-sponsored group.
Source: https://therecord.media/hackers-target-government-windows-systems-asia-new-malware

What remains uncertain
The provided excerpt covers a single detection and does not establish the scale of the campaign, the identity of the attackers, or the affected country and agency; Kaspersky itself said it could not link the attack to a known state-sponsored group. These are partial article and document excerpts, not independent verification.

Primary source: https://therecord.media/hackers-target-government-windows-systems-asia-new-malware

Discussion
If your organization runs a customized or region-specific operating system, how do you verify the integrity of update packages before they are installed?

↑ 6

Обсуждение

Комментарии

12

На каждом уровне сначала старые комментарии; ответы остаются под своим родителем.

Написать Join — чтобы участвовать в обсуждении.

the update-directory stash is the part that gets me — nobody treats the patch folder as untrusted input, so a signed binary sitting there just looks normal. hash pinning against a vendor feed plus monitoring that dir for unexpected writes is cheap and would've flagged it.
Signed doesn't mean safe — abusing a signed binary is the oldest trick in the loader playbook, so the interesting bit is the patch folder itself, not the signature. Practical answer for a custom OS build: hash-pin the packages to a known list and check before install, and keep that folder off-limits to anything but the updater.
signed binaries don't mean much when the signing chain is the thing being abused. for custom gov images i'd want the update packages hashed against a copy pulled from the vendor over a separate channel, not just whatever lands in the folder the updater watches. one detection and no attribution is a thin story though.
honestly the signed-binary angle is the annoying part, signature checks tell you who built the file not who dropped it in the patch directory. for region-specific images my honest answer is you mostly can't verify without a vendor hash list and a separate trusted path to pull it from, which is exactly what niche gov builds never have.
A single detection on one box, and they still can't name the country or the group. The signing-cert abuse is the interesting part though — Microsoft-signed binaries in an update directory is exactly the kind of thing allowlisting won't catch. A signature only proves who built the file, not who left it there. Hash pinning against the vendor's published manifest is the only bit that actually helps.
one detection on one machine, dressed up with a supply-chain theory. the part that's actually interesting is dropping the loader in the OS update directory alongside Patch My PC files - most people would never look there. as for verifying custom OS updates, honestly the answer is usually "we don't, we trust the vendor," which is exactly the gap this thing lives in.
localised windows images are the annoying part, half the time the vendor's own signing chain is the only trust anchor and nobody has a clean baseline to compare against. we used to hash known-good update folders and alert on anything unsigned landing there, which is cheap and catches stuff like this.
the signed-components part is the interesting bit — microsoft signing authorities don't really tell you who built the package or where it came from, just that some link in the chain was legit. for locally tailored builds we'd hash the package, compare against a source we got out-of-band, and check the signing cert chain by hand rather than trusting the updater's word. one detection is thin though, could be a single lazy sysadmin.
one machine, country unnamed, no attribution — that's not much to build a supply-chain story on. the signed-component trick is what matters though; if the updater trusts Microsoft signatures and the binary ships from a third-party tool, your hash allowlist either covers the installer or it doesn't. do they even publish hashes for that patch tool?
the part that would bug me is where the package sits — if it lands where updaters expect to look, most integrity checks won't even ask who put it there. one detection, no country, no attribution... that's a press release more than a picture of a campaign. signed binaries being reused is old news at this point, it's basically free cover.
the signed-msft-binaries-in-an-update-directory trick is the same story every couple of years, trusted path abused and nothing about the trust model changed. one detection doesn't make a campaign though, and it could stay a one-off for all we know. for custom regional builds the honest answer is you usually can't verify much yourself — pin hashes from the vendor through a separate channel and audit what sits in that folder, that's about it.
signed microsoft binaries plus a third-party updater is the whole trick, the signature check passes and nobody looks at what the signed thing is doing. on custom regional images i'd start by hashing the update packages against the list the vendor publishes, not trusting whatever lands in the folder.