1-minute read
What a defender needs to know
A targeted fake Web3 interview used LinkedIn, Calendly, a Google Apps Script assessment, and signed ClickOnce to compromise a cryptocurrency employee’s Windows workstation. Investigators fully analyzed version 1.0.0.201, but the source says version 1.0.0.182 had the closest link to the July incident and that the retained evidence did not prove version 1.0.0.201 ran on the victim. The recovered application displayed a real Google Workspace page while retrieving a password-protected archive with two credential stealers and a Go RAT with hidden VNC. Private keys were compromised and assets moved across six chains within roughly one hour. Static recovery confirmed the designed three-payload chain, but execution of every branch on the victim was unconfirmed. Operator attribution also remains unresolved.
Search process telemetry for rundll32.exe loading dfshim.dll, followed by dfsvc.exe, Launcher.exe, GapiUpdate.exe, or GapiUpdate.dll. Inspect %LOCALAPPDATA%\Apps\2.0, each user’s SideBySide\2.0 ClickOnce records, the DeviceSetupManager scheduled task, the published certificate, file hashes, and defanged network indicators. Treat Google Apps Script, Dropbox, and the other named shared services as contextual evidence because they were legitimate services abused by the chain.
The expected clean result is no attacker-controlled ClickOnce origin, published certificate, payload hash, or DeviceSetupManager task. Any match triggers host isolation and rotation of browser sessions, wallet keys, cloud tokens, source-control tokens, deployment secrets, VPN credentials, and SSH keys from a known-clean system. Reimaging removes the malware; session and credential invalidation removes access the stealers may already have copied.