UNC1069 (MASAN) Gemini misuse and deepfake Zoom lures
DPRK-linked UNC1069 used Gemini for crypto research and lures, and used deepfakes of crypto figures to push a fake 'Zoom SDK' that delivers the BIGMACHO backdoor.
What happened
DPRK-linked UNC1069 used Gemini for crypto recon, wallet path research, Spanish lure text, and credential-theft 'update' instructions. Separately used deepfake images/video of crypto industry figures to push malicious 'Zoom SDK' links delivering BIGMACHO backdoor.
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 · Actor prepares cryptocurrency operations
The report describes two related capability areas without proving a single combined chain.
Hunt: A model-provider investigation correlates related accounts, repeated offensive requests and shared infrastructure or exposed operator sessions.
Attacker-side planning is generally absent from victim SIEM logs. These templates require provider-owned audit data and do not identify AI use from a victim process alone.
Source for step 1 - 02 · Gemini assists research and lure text
Requests cover cryptocurrency reconnaissance, wallet paths and Spanish-language messages.
Hunt: A model-provider investigation correlates related accounts, repeated offensive requests and shared infrastructure or exposed operator sessions.
Attacker-side planning is generally absent from victim SIEM logs. These templates require provider-owned audit data and do not identify AI use from a victim process alone.
Source for step 2 - 03 · Separate deepfake Zoom lure
Deepfake images or video impersonate cryptocurrency industry figures.
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 3 - 04 · Malicious Zoom SDK delivers BIGMACHO
The separately reported social-engineering branch leads to a backdoor download.
Hunt: A program delivered by the reported lure executes, establishes access or contacts infrastructure outside the approved software baseline.
A program name alone is not a signature. This normalized template requires the relevant platform collector and does not assert Windows-only policy coverage.
Source for step 4
Why it matters
Reported entry point: Social engineering / deepfake lures with malicious Zoom SDK download. Reported impact: the cited report does not establish a confirmed victim outcome; reported targets include Cryptocurrency users/industry; using the named AI products does not by itself establish exposure.
What you can do
Protection & prevention
Verify Zoom/SDK downloads; deepfake skepticism; block unofficial SDKs
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.
01Actor prepares cryptocurrency operationsProvider-side abuse investigationCustom schema · Draft
The report describes two related capability areas without proving a single combined chain.
What to look for
A model-provider investigation correlates related accounts, repeated offensive requests and shared infrastructure or exposed operator sessions.
Keep the separately described development and impersonation capabilities distinct; do not invent a combined victim chain.
Visibility: Provider / operator records
Required logs
- Provider-owned account / request audit
- Abuse-review findings and linked-account context
- Lawfully available exposed operator-session evidence
Coverage limit. Attacker-side planning is generally absent from victim SIEM logs. These templates require provider-owned audit data and do not identify AI use from a victim process alone.
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 - Provider-side abuse investigation
id: c8c1edc0-c79a-4644-a876-2c1a6cb9a438
status: experimental
description: A model-provider investigation correlates related accounts,
repeated offensive requests and shared infrastructure or exposed operator
sessions.
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:
- model.request
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 ("model.request")
| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId
| order by TimeGenerated descSPL
sourcetype="openattacks:audit"
EventType IN ("model.request")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _timeInvestigation steps
- Correlate accounts, request rates, infrastructure and source-described behavior in provider-owned records.
- For victim-side defense, pivot to the reported execution or access stage rather than trying to detect attacker-side prompts.
02Gemini assists research and lure textProvider-side abuse investigationCustom schema · Draft
Requests cover cryptocurrency reconnaissance, wallet paths and Spanish-language messages.
What to look for
A model-provider investigation correlates related accounts, repeated offensive requests and shared infrastructure or exposed operator sessions.
Visibility: Provider / operator records
Required logs
- Provider-owned account / request audit
- Abuse-review findings and linked-account context
- Lawfully available exposed operator-session evidence
Coverage limit. Attacker-side planning is generally absent from victim SIEM logs. These templates require provider-owned audit data and do not identify AI use from a victim process alone.
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 - Provider-side abuse investigation
id: c8c1edc0-c79a-4644-a876-2c1a6cb9a438
status: experimental
description: A model-provider investigation correlates related accounts,
repeated offensive requests and shared infrastructure or exposed operator
sessions.
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:
- model.request
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 ("model.request")
| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId
| order by TimeGenerated descSPL
sourcetype="openattacks:audit"
EventType IN ("model.request")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _timeInvestigation steps
- Correlate accounts, request rates, infrastructure and source-described behavior in provider-owned records.
- For victim-side defense, pivot to the reported execution or access stage rather than trying to detect attacker-side prompts.
03Separate deepfake Zoom lureLure → user action / deliveryCustom schema · Draft
Deepfake images or video impersonate cryptocurrency industry figures.
What to look for
An impersonating message, ad or website leads to a suspicious download, consent request, pasted command or payment instruction.
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.
04Malicious Zoom SDK delivers BIGMACHOUnexpected payload / remote-access behaviorCustom schema · Draft
The separately reported social-engineering branch leads to a backdoor download.
What to look for
A program delivered by the reported lure executes, establishes access or contacts infrastructure outside the approved software baseline.
Confirm the payload platform and delivery branch from original reporting before choosing endpoint-specific rules. No Windows policy coverage is assumed here.
Visibility: Defender-side logs where collected
Required logs
- Platform-specific process and file provenance
- Signer / hash and software inventory
- Per-process network and remote-session records
Coverage limit. A program name alone is not a signature. This normalized template requires the relevant platform collector and does not assert Windows-only policy coverage.
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 - Unexpected payload / remote-access behavior
id: 998d4263-6e73-4472-a74d-cb4d61c28544
status: experimental
description: A program delivered by the reported lure executes, establishes
access or contacts infrastructure outside the approved software baseline.
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:
- process.unapproved.exec
- remote.session.start
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 ("process.unapproved.exec", "remote.session.start")
| project TimeGenerated, EventType, Actor, Asset, Action, Target, CorrelationId
| order by TimeGenerated descSPL
sourcetype="openattacks:audit"
EventType IN ("process.unapproved.exec", "remote.session.start")
| table _time EventType Actor Asset Action Target CorrelationId
| sort - _timeInvestigation steps
- Confirm the payload's operating system, origin and execution context before choosing a platform-specific rule.
- Correlate the launched program with child processes, persistence and network activity; verify authorization.
Technical detailsTooling, impact & MITRE ATLAS
Attack context
- AI's role
- AI as operator
- Initial access
- Social engineering / deepfake lures with malicious Zoom SDK download
Tooling as reported
AI products, models and artifacts
- Gemini
- deepfake image/video
Other tooling
- BIGMACHO backdoor
- fake Zoom SDK
Targets and reported impact
- Targets / sectors
- Cryptocurrency users/industry
Reported attribution
UNC1069 aka MASAN; DPRK-associated
Structured attribution
- Actor
- UNC1069 aka MASAN
Detection rules
- Review attack-specific indicatorsGUIDANCE
Monitor for the techniques described in UNC1069 (MASAN) Gemini misuse + deepfake Zoom lures. Refer to sources for specific IOCs and TTPs.
Source defensive notes
Verify Zoom/SDK downloads; deepfake skepticism; block unofficial SDKs
MITRE ATLAS
AI-specific catalog annotations based on the reported behavior; these are not MITRE case-study assignments.
A separately reported lure uses deepfake industry figures. Source
Gemini supports cryptocurrency research and lure writing. Source
Sources & research credit
1 sourceResearch by Google Threat Intelligence Group · Google GTIG
Record & downloads
- Source record name
- UNC1069 (MASAN) Gemini misuse + deepfake Zoom lures
- Entry ID
- unc1069-gemini-deepfake-crypto-2025
- Catalog review
- October 20, 2026
- Category
- adversary-use-of-ai
- AI involvement confidence
- confirmed