Security1 distinct publisher3 min readUpdated
A researcher says an unreported campaign used a fake GSTR-3B overdue notice ahead of the 20 August filing deadline, delivering a patched DLL that a genuinely signed Microsoft binary loads.
The Watch · Security desk
.png)
Compiled by The WatchSomething wrong?How this is made
Independent researcher Himanshu Anand says he found an unreported Silver Fox campaign delivering the ValleyRAT backdoor to Indian taxpayers using a fake "GSTR-3B overdue" notice timed to the real 20 August GST filing deadline [1]. The delivery chain leans on a genuinely Microsoft-signed copy of SystemSettings.exe that sideloads a patched SystemSettings.dll, which still carries a Microsoft certificate that no longer validates [1][6].
The sample surfaced in ANY.RUN's public submissions on 7 August 2026, named GST_Filing_Overdue_GSTR-3B_GSTIN27ABCDE1234F1Z5_Due_20082026.zip [2]. GSTR-3B is the monthly return every GST-registered business in India files, GSTIN is the tax identifier, the 20th is the actual deadline, and per Anand the GSTIN in the filename uses the correct format, with the 27 prefix corresponding to Maharashtra [14]. The recovered config carries a build date of 2 August 2026 [9], which puts construction 18 days before the deadline it references [1] and public sighting 13 days before it [2].
The ZIP holds a 1.2 MB disk image, which Anand notes matters because files inside a mounted image do not inherit Mark-of-the-Web, so the "this came from the internet" prompts never fire [3]. Inside are two files: a 98 KB executable and a 59 KB SystemSettings.dll [4]. The executable is the real Windows Settings app, renamed, with a valid Microsoft Corporation signature [5]. The DLL was a real Microsoft binary until it was patched; the certificate is still attached but the hash mismatches [6]. Anand's point is the operational one: no unsigned attacker code ever touches disk, and stage one lives entirely inside a tampered system DLL that a signed Microsoft process loads voluntarily [7]. To a reputation-based filter, both files read as Microsoft [6].
The evasion continues inside the DLL. DllMain is stock CRT boilerplate and the exports are stubs, with the implant grafted into the CRT init path, so scanners keying on entry-point anomalies find nothing [15]. The orchestrator function never handles a readable string: API names, C2 addresses and paths are built as stack constants, decoded in place, used and zeroed, with junk calls interleaved [16]. The decoder is a single-byte XOR against 0x70, and the first decoded block resolves kernel32.dll and GetModuleHandleA [17]. Stage two injects into RuntimeBroker.exe carrying a full UACMe kit, a Defender tamperer and an AV process-killer [8]. ANY.RUN flagged the file as malicious with ValleyRAT, silverfox, winos and processkiller tags [10].
None of this is new behaviour for the group. Silver Fox, also tracked as SwimSnake and Void Arachne, is a China-nexus crew running ValleyRAT on the WinOS 4.0 framework, a plugin-based RAT with keylogging and screen capture [12]. Anand cites CloudSEK research on Income Tax Department lures aimed at Indian users since at least December 2025, NCC Group on SEO-poisoned fake installers, and a Russian false-flag operation intended to confuse attribution [13]. Sideloading behind signed binaries, disposable free-domain C2 and tax-season timing are described as the group's standard fare [19].
What to watch: the config includes three C2 endpoints, a dormant backup domain, and a 15-subdomain delivery platform issuing per-victim lure links, which means takedowns of one domain buy little [9]. Anand reports zero public coverage of the file, its C2s or the GST wave beyond a single urlscan record of the delivery domain [11], and his analysis was done on an ANY.RUN account provided under a collaboration [18]. The transferable lesson for defenders is scheduling: filing deadlines are published, so the weeks before the 20th of any month are a predictable window for lures that arrive wearing a valid signature.
Follow any of these and your For You feed starts watching them — no settings page required.
Ranked by verification strength, evidence, and original report placement.
Stage 2 injects into RuntimeBroker.exe with a full UACMe kit, a Defender tamperer and an AV process-killer.
Silver Fox (also SwimSnake / Void Arachne) is a China-nexus crew running ValleyRAT, built on the WinOS 4.0 framework: a plugin-based RAT with keylogger and screen capture.
Silver Fox's habitual tradecraft is DLL sideloading behind signed binaries, disposable free-domain C2, and tax-season timing.
An unreported Silver Fox campaign served ValleyRAT to Indian taxpayers with a fake 'GSTR-3B overdue' lure, timed to the real 20 August GST filing deadline. Delivery was a disk image containing a genuinely Microsoft-signed SystemSettings.exe that sideloads a patched SystemSettings.dll.
The file GST_Filing_Overdue_GSTR-3B_GSTIN27ABCDE1234F1Z5_Due_20082026.zip was submitted to ANY.RUN's public submissions on 7 August 2026.
The ZIP contains a 1.2 MB .img disk image; files inside a mounted image do not inherit Mark-of-the-Web, so the 'this came from the internet' prompts never fire, and the image mounts on double click like a USB drive.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Strong artefact detail, single unverified source
The technical core is unusually well evidenced for a blog post: signature states for both files, sizes, a named orchestrator function, a reproducible XOR 0x70 decoder, decoded C2 domains and URI paths, and a statically recovered domain that matches what the sandbox observed on the network — static and dynamic corroborating each other inside one analysis. What holds the score down is that everything comes from one self-published researcher with no second source, no file hashes in the captured text, second-hand-only references to the prior CloudSEK and NCC Group research, and a body that truncates before the detailed stage-2 reversing that the TLDR summarises.
Live infrastructure, unmeasured spread
There is real in-the-wild evidence: one sample in a public sandbox feed on 7 August 2026, a build date five days earlier, and a delivery platform the author describes as actively serving per-victim lure links across 15 subdomains at publication. But nothing in the cluster measures reach — no victim counts, no distribution volume, no telemetry on how many recipients received the GSTR-3B lure, and no confirmed compromise. Adoption here is 'confirmed operational, scale unknown'.
Slightly overstated framing
The mechanics are as described, but the framing runs ahead of the proof in two ways: 'unreported campaign' is an absence claim resting solely on the author's own searching, and campaign-scale language ('serving per-victim lure links as I type this', 'Indian taxpayers') is supported by one sample plus infrastructure enumeration with zero victim or volume data. Attribution to Silver Fox leans on sandbox tags and a zh-CN Accept-Language fallback rather than independent confirmation. The gap is modest, not egregious — the underlying artefacts are documented in detail and the author discloses his tooling relationship.
Disclosed vendor collaboration
The finding originates in the public feed of the same sandbox vendor that supplied the author's account through a collaboration, and the piece's central 'why static analysis matters' beat also functions as a showcase for that platform's public submissions and process-dump features. The author discloses the arrangement up front and states conclusions are his own, and there is no product pitch, referral link or commercial ask in the text, so the incentive is present and visible rather than concealed. A personal-reputation incentive around claiming an unreported campaign also sits behind the novelty framing.
Moderate
Confidence in the technical mechanism is high — the artefacts are specific, internally consistent and partly cross-checked between static and dynamic analysis. Confidence in scope, novelty and attribution is low: one publisher, one sample, no hashes in the captured text, no corroborating vendor or CERT source, cited prior research not supplied, and a truncated body for the stage-2 section. Net moderate.
build
A UDP packet is now enough: IKEEXT RCE moves from patch queue to fire drill1 distinct publisher
product
Nebius funds $4.5bn of AI capacity on terms that pay lenders mostly in stock2 distinct publishers
invest
Behind-the-meter gas is the data center buildout's real cost: 318 Mt a year1 distinct publisher
build
Grok 4.6 lands in Copilot two days after launch, and the model picker becomes a procurement problem1 distinct publisher
Distinct publishers with included, body-backed reporting in this cluster.
1 article · August 20, 2026