Fake DeepSeek and Grok Windows clients deliver stealers and backdoors
Fake DeepSeek and Grok desktop installers delivered stealers, SSH backdoors, Vidar, the BrowserVenom traffic proxy and Gh0stRAT variants.
What happened
No official DeepSeek Windows desktop client; fake DeepSeek/Grok installers delivered Python stealers, SSH backdoors, Vidar, BrowserVenom (browser traffic proxying), and Chinese-language trojanized installers including Gh0stRAT variants.
How it happened
Read the flow as text & sources
A catalog reconstruction of the supplied source account. Unknown steps remain explicit; an edge describes the reported relationship between steps.
- 01 · User finds an unofficial AI client
Fake DeepSeek or Grok desktop downloads are promoted through sites and ads.
Hunt: An impersonating message, ad or website leads to a suspicious download, consent request, pasted command or payment instruction.
Polished text, AI branding and a novel domain do not prove maliciousness or AI generation. Follow-on evidence matters.
Source for step 1 - 02 · AI product branding is impersonated
The installer presents itself as a trusted model client.
Hunt: An impersonating message, ad or website leads to a suspicious download, consent request, pasted command or payment instruction.
Polished text, AI branding and a novel domain do not prove maliciousness or AI generation. Follow-on evidence matters.
Source for step 2 - 03 · Trojanized installer runs
Reported branches deliver stealers, SSH backdoors or RAT variants.
Hunt: A newly downloaded or staged executable runs from a user-writable location and exhibits the reported follow-on behavior.
Many approved installers run from user-writable folders. These events are hunt candidates, not proof of malware or an enforced block.
MagicSword policy opportunity · The reported Windows installers and payloads on managed devices; validate signer and hash policy coverage.
Source for step 3 - 04 · Data theft or remote access
Payloads steal browser data, proxy traffic or establish attacker access.
Hunt: An unexpected process or tool accesses credential stores and is followed by token use or outbound transfer inconsistent with the owner.
Defender DeviceFileEvents is not a general file-read audit trail. Collect suitable object-access, EDR or application logs; legitimate developer tools also read secrets.
Source for step 4
Why it matters
Reported entry point: Users download fake AI desktop clients from unofficial sites/ads. Reported impact: Payloads steal browser data, proxy traffic or establish attacker access; reported targets include Users seeking DeepSeek/Grok desktop apps.
Check these source-linked conditions against your setup.
Fake DeepSeek / Grok Windows installers deliver the payloads in this account.
Conditions to check- The reported path requires installation of a malicious desktop package.
Source-linked applicability guidance. Confirm current scope in the original report.
What you can do
Protection & prevention
Verify desktop installer provenance and investigate unapproved executables and persistence.
Only official web apps; block unsigned AI installers; MagicSword prevent unexpected stealers
Catalog defensive guidance based on the reported behavior. Confirm scope and current mitigations in the original source.
Detection queries
Draft query starters grouped by the attack stages where they apply.
Start with the logs you collect. Each hunt identifies its required visibility, field mapping and limits. Queries are catalog-authored drafts using reusable behavior profiles; test with known activity and your normal baseline before alerting.
01User finds an unofficial AI clientLure → user action / deliveryCustom schema · Draft
Fake DeepSeek or Grok desktop downloads are promoted through sites and ads.
What to look for
An impersonating message, ad or website leads to a suspicious download, consent request, pasted command or payment instruction.
Trace the advertisement and unofficial download to file provenance and later execution.
Visibility: Defender-side logs where collected
Required logs
- Email / secure-web-gateway records
- Browser redirects, downloads and URL reputation
- User reports and downstream execution / identity events
Coverage limit. Polished text, AI branding and a novel domain do not prove maliciousness or AI generation. Follow-on evidence matters.
Custom-schema candidates, not out-of-box detectors. Map your application / cloud / platform logs to EventType, Actor, Asset, Action, Target and CorrelationId. KQL uses a custom OpenAttacksAudit_CL table; SPL uses openattacks:audit. EventType values are proposed normalization names, not native vendor event names. Correlation and environment-specific alert logic remain to be built.
Sigma
title: Hunt - Lure → user action / delivery
id: e0056b49-9905-485b-ac12-2aa076a7bc82
status: experimental
description: An impersonating message, ad or website leads to a suspicious
download, consent request, pasted command or payment instruction.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: application
product: openattacks_audit
definition: Custom normalized audit schema; map EventType, Actor, Asset, Action,
Target and CorrelationId from the required source logs first.
detection:
selection:
EventType:
- message.link.click
- web.download
condition: selection
KQL
// SCHEMA TEMPLATE: create/map this custom table before use; not a built-in Sentinel table.
// OpenAttacksAudit_CL: TimeGenerated(datetime), EventType/Actor/Asset/Action/Target/CorrelationId(string).
// Selects candidates only. Apply the stage hypothesis and correlation steps before alerting.
OpenAttacksAudit_CL
| where TimeGenerated > ago(7d)
| where EventType in ("message.link.click", "web.download")
| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId
| order by TimeGenerated descSPL
sourcetype="openattacks:audit"
EventType IN ("message.link.click", "web.download")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _timeInvestigation steps
- Reconstruct redirect and delivery provenance using original report indicators, without visiting payload URLs.
- Correlate the click with the actual download, consent or execution; verify the sender through an independent channel.
02AI product branding is impersonatedLure → user action / deliveryCustom schema · Draft
The installer presents itself as a trusted model client.
What to look for
An impersonating message, ad or website leads to a suspicious download, consent request, pasted command or payment instruction.
Use download provenance and follow-on behavior; an AI product name is not sufficient evidence of a malicious installer.
Visibility: Defender-side logs where collected
Required logs
- Email / secure-web-gateway records
- Browser redirects, downloads and URL reputation
- User reports and downstream execution / identity events
Coverage limit. Polished text, AI branding and a novel domain do not prove maliciousness or AI generation. Follow-on evidence matters.
Custom-schema candidates, not out-of-box detectors. Map your application / cloud / platform logs to EventType, Actor, Asset, Action, Target and CorrelationId. KQL uses a custom OpenAttacksAudit_CL table; SPL uses openattacks:audit. EventType values are proposed normalization names, not native vendor event names. Correlation and environment-specific alert logic remain to be built.
Sigma
title: Hunt - Lure → user action / delivery
id: e0056b49-9905-485b-ac12-2aa076a7bc82
status: experimental
description: An impersonating message, ad or website leads to a suspicious
download, consent request, pasted command or payment instruction.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: application
product: openattacks_audit
definition: Custom normalized audit schema; map EventType, Actor, Asset, Action,
Target and CorrelationId from the required source logs first.
detection:
selection:
EventType:
- message.link.click
- web.download
condition: selection
KQL
// SCHEMA TEMPLATE: create/map this custom table before use; not a built-in Sentinel table.
// OpenAttacksAudit_CL: TimeGenerated(datetime), EventType/Actor/Asset/Action/Target/CorrelationId(string).
// Selects candidates only. Apply the stage hypothesis and correlation steps before alerting.
OpenAttacksAudit_CL
| where TimeGenerated > ago(7d)
| where EventType in ("message.link.click", "web.download")
| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId
| order by TimeGenerated descSPL
sourcetype="openattacks:audit"
EventType IN ("message.link.click", "web.download")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _timeInvestigation steps
- Reconstruct redirect and delivery provenance using original report indicators, without visiting payload URLs.
- Correlate the click with the actual download, consent or execution; verify the sender through an independent channel.
03Trojanized installer runsUnapproved Windows program executionNative logs · Draft
Reported branches deliver stealers, SSH backdoors or RAT variants.
What to look for
A newly downloaded or staged executable runs from a user-writable location and exhibits the reported follow-on behavior.
Visibility: Defender-side logs where collected
Required logs
- Windows process creation
- Download provenance and file hashes
- File certificate information and application-control audit / block events
Coverage limit. Many approved installers run from user-writable folders. These events are hunt candidates, not proof of malware or an enforced block.
Windows process candidates. Sigma uses normalized process_creation fields; KQL requires Defender for Endpoint; SPL requires the Sysmon XML sourcetype. Tune collectors, fields and baselines before use.
Sigma
title: Hunt - Unapproved Windows program execution
id: e217e948-e57c-48b8-a331-66006de42ae1
status: experimental
description: A newly downloaded or staged executable runs from a user-writable
location and exhibits the reported follow-on behavior.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: process_creation
product: windows
detection:
selection:
Image|contains:
- \Downloads\
- \AppData\Local\Temp\
- \AppData\Roaming\
condition: selection
KQL
// Draft hunt; requires Defender for Endpoint process telemetry for this OS.
DeviceProcessEvents
| where Timestamp > ago(7d)
| where FolderPath contains "\\Downloads\\" or FolderPath contains "\\AppData\\Local\\Temp\\" or FolderPath contains "\\AppData\\Roaming\\"
| project Timestamp, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName, InitiatingProcessCommandLine, SHA1
| order by Timestamp descSPL
sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=1
Image IN ("*\\Downloads\\*", "*\\AppData\\Local\\Temp\\*", "*\\AppData\\Roaming\\*")
| table _time host User Image CommandLine ParentImage ParentCommandLine
| sort - _timeInvestigation steps
- Verify publisher, hash, origin, prevalence and local approval rather than trusting a product name or signature.
- Trace child processes and related credential, network or persistence events.
04Data theft or remote accessSensitive store access → credential useCustom schema · Draft
Payloads steal browser data, proxy traffic or establish attacker access.
What to look for
An unexpected process or tool accesses credential stores and is followed by token use or outbound transfer inconsistent with the owner.
Visibility: Defender-side logs where collected
Required logs
- File-read / API access telemetry for relevant secret stores
- Process identity and command lines
- Identity, token and outbound-network audit logs
Coverage limit. Defender DeviceFileEvents is not a general file-read audit trail. Collect suitable object-access, EDR or application logs; legitimate developer tools also read secrets.
Custom-schema candidates, not out-of-box detectors. Map your application / cloud / platform logs to EventType, Actor, Asset, Action, Target and CorrelationId. KQL uses a custom OpenAttacksAudit_CL table; SPL uses openattacks:audit. EventType values are proposed normalization names, not native vendor event names. Correlation and environment-specific alert logic remain to be built.
Sigma
title: Hunt - Sensitive store access → credential use
id: 46c46c62-2d83-4198-a8bf-d6637094527b
status: experimental
description: An unexpected process or tool accesses credential stores and is
followed by token use or outbound transfer inconsistent with the owner.
author: MagicSword OpenAttacks catalog
date: 2026-10-23
falsepositives:
- Authorized activity matching this broad hunt; baseline and investigate
before alerting.
level: low
logsource:
category: application
product: openattacks_audit
definition: Custom normalized audit schema; map EventType, Actor, Asset, Action,
Target and CorrelationId from the required source logs first.
detection:
selection:
EventType:
- secret.read
- credential.store.read
condition: selection
KQL
// SCHEMA TEMPLATE: create/map this custom table before use; not a built-in Sentinel table.
// OpenAttacksAudit_CL: TimeGenerated(datetime), EventType/Actor/Asset/Action/Target/CorrelationId(string).
// Selects candidates only. Apply the stage hypothesis and correlation steps before alerting.
OpenAttacksAudit_CL
| where TimeGenerated > ago(7d)
| where EventType in ("secret.read", "credential.store.read")
| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId
| order by TimeGenerated descSPL
sourcetype="openattacks:audit"
EventType IN ("secret.read", "credential.store.read")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _timeInvestigation steps
- Identify the actor, process and exact store touched, then pivot to token use from new devices or infrastructure.
- Correlate reads with egress and rotate affected credentials after confirming exposure.
Technical detailsTooling, impact
Attack context
- AI's role
- AI tool as lure
- Initial access
- Users download fake AI desktop clients from unofficial sites/ads
Tooling as reported
AI products, models and artifacts
Other tooling
- Vidar
- BrowserVenom
- Gh0stRAT
- Python stealers
Targets and reported impact
- Targets / sectors
- Users seeking DeepSeek/Grok desktop apps
- Target geography
- Multiple regions
The source describes global distribution. Chinese-language installers do not establish victims in China.
Detection rules
- Review attack-specific indicatorsGUIDANCE
Monitor for the techniques described in Fake DeepSeek / Grok Windows clients deliver stealers and backdoors. Refer to sources for specific IOCs and TTPs.
Source defensive notes
Only official web apps; block unsigned AI installers; MagicSword prevent unexpected stealers
Sources & research credit
3 sourcesResearch by Kaspersky / Securelist; McAfee; Unit 42 · Kaspersky
Record & downloads
- Source record name
- Fake DeepSeek / Grok Windows clients deliver stealers and backdoors
- Entry ID
- deepseek-grok-fake-windows-clients-2025
- Catalog review
- October 20, 2026
- Category
- adversary-use-of-ai
- AI involvement confidence
- confirmed