UNC4899 (PUKCHONG) uses Gemini for exploit and tooling R&D
DPRK group UNC4899 used Gemini for code development, exploit research and tooling aimed at edge devices and modern browsers.
What happened
DPRK UNC4899 (PUKCHONG), known for supply-chain compromise, used Gemini for code development, exploit research, and tooling improvements targeting edge devices and modern browsers.
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 requests exploit research support
UNC4899 researches edge devices and modern browsers.
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 supports development
The model helps with code, exploit research and tooling improvements.
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 · Existing offensive tooling is refined
The source describes development assistance to an actor known for supply-chain compromise.
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 3 - 04 · Specific deployment is undisclosed
The seed does not connect each model interaction to a confirmed victim intrusion.
Source for step 4
Why it matters
Reported impact: the cited report does not establish a confirmed victim outcome; using the named AI products does not by itself establish exposure.
What you can do
Protection & prevention
Supply-chain integrity; browser/edge device patching
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 requests exploit research supportProvider-side abuse investigationCustom schema · Draft
UNC4899 researches edge devices and modern browsers.
What to look for
A model-provider investigation correlates related accounts, repeated offensive requests and shared infrastructure or exposed operator sessions.
Review exploit-research requests at the provider; specific victim deployments are not established at this stage.
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 supports developmentProvider-side abuse investigationCustom schema · Draft
The model helps with code, exploit research and tooling improvements.
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.
03Existing offensive tooling is refinedProvider-side abuse investigationCustom schema · Draft
The source describes development assistance to an actor known for supply-chain compromise.
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.
Technical detailsTooling, impact & MITRE ATLAS
Attack context
- AI's role
- AI as operator
Tooling as reported
AI products, models and artifacts
Reported attribution
UNC4899 aka PUKCHONG; DPRK
Structured attribution
- Actor
- UNC4899 aka PUKCHONG
Detection rules
- Review attack-specific indicatorsGUIDANCE
Monitor for the techniques described in UNC4899 (PUKCHONG) Gemini for exploit and tooling R&D. Refer to sources for specific IOCs and TTPs.
Source defensive notes
Supply-chain integrity; browser/edge device patching
MITRE ATLAS
AI-specific catalog annotations based on the reported behavior; these are not MITRE case-study assignments.
The supplied source explicitly describes generative-model tooling assisting the reported activity; this mapping does not establish additional autonomy or victim impact. Source
Sources & research credit
1 sourceResearch by Google Threat Intelligence Group · Google GTIG
Record & downloads
- Source record name
- UNC4899 (PUKCHONG) Gemini for exploit and tooling R&D
- Entry ID
- unc4899-pukchong-gemini-2025
- Catalog review
- October 20, 2026
- Category
- adversary-use-of-ai
- AI involvement confidence
- confirmed