# UNC4899 (PUKCHONG) Gemini for exploit and tooling R&D

- ID: unc4899-pukchong-gemini-2025
- Reported: 2025-11-05
- Researcher: Google Threat Intelligence Group
- Organization: Google GTIG
- AI role: attacker_uses_ai_as_operator (AI as operator)
- Confidence in AI involvement: not assessed
- Research / borderline: false
- Last reviewed: 2026-10-20
- Entry page: https://openattacks.ai/attacks/unc4899-pukchong-gemini-2025/
- Entry JSON: https://openattacks.ai/api/attacks/unc4899-pukchong-gemini-2025.json
- Browse title: UNC4899 (PUKCHONG) uses Gemini for exploit and tooling R&D
- Editorial summary: DPRK group UNC4899 used Gemini for code development, exploit research and tooling aimed at edge devices and modern browsers.
- Evidence class (catalog annotation): Provider report
- Source-stated target environments: Provider-side
- Stage hunts and conditional defenses: https://openattacks.ai/api/defenses/unc4899-pukchong-gemini-2025.json

## Technique
DPRK UNC4899 (PUKCHONG), known for supply-chain compromise, used Gemini for code development, exploit research, and tooling improvements targeting edge devices and modern browsers.

## Stack relevance (editorial)
Assessment: attacker\_tool\_only. Editorial applicability reviewed against the catalog source account; not a scan or independent incident verification.
The named AI product is used by the attacker. No reviewed mapping from owning that product to the reported victim conditions is available.
A product mention alone is not a victim-side applicability mapping. Selection does not verify affected versions, permissions or compromise.

## Initial access
unknown

## AI tooling and models
- [Gemini](https://gemini.google.com/)

## Other tooling
- unknown

## Victims and sectors
unknown

## Target geography
- unknown

## Attribution
UNC4899 aka PUKCHONG; DPRK

## Scale and metrics
unknown

## Attack flow
Catalog reconstruction of the supplied source account. Unknowns and research caveats are preserved.
### step-1: Actor requests exploit research support [access]
UNC4899 researches edge devices and modern browsers.
Evidence: https://cloud.google.com/blog/topics/threat-intelligence/threat-actor-usage-of-ai-tools/

### step-2: Gemini supports development [ai]
The model helps with code, exploit research and tooling improvements.
Evidence: https://cloud.google.com/blog/topics/threat-intelligence/threat-actor-usage-of-ai-tools/

### step-3: Existing offensive tooling is refined [execution]
The source describes development assistance to an actor known for supply-chain compromise.
Evidence: https://cloud.google.com/blog/topics/threat-intelligence/threat-actor-usage-of-ai-tools/

### step-4: Specific deployment is undisclosed [unknown]
The seed does not connect each model interaction to a confirmed victim intrusion.
Evidence: https://cloud.google.com/blog/topics/threat-intelligence/threat-actor-usage-of-ai-tools/

Connections:
- step-1 -> step-2
- step-2 -> step-3
- step-3 -> step-4

## Stage defense and hunting recommendations
Editorial recommendations, not validated coverage. Source-controlled query starters are drafts. Custom-schema examples require telemetry collection and field mapping; absence of a mapping means not assessed. MagicSword policy opportunities require managed Windows scope and enforcement.
### step-1: Provider-side abuse investigation
- Visibility: Provider / operator records
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/provider.sigma.yml
- KQL query download: /api/detections/provider.kql
- SPL query download: /api/detections/provider.spl
- Hunt hypothesis: A model-provider investigation correlates related accounts, repeated offensive requests and shared infrastructure or exposed operator sessions.
- Required telemetry: Provider-owned account / request audit; Abuse-review findings and linked-account context; Lawfully available exposed operator-session evidence
- Investigate: Correlate accounts, request rates, infrastructure and source-described behavior in provider-owned records.
- Investigate: For victim-side defense, pivot to the reported execution or access stage rather than trying to detect attacker-side prompts.
- Limitation: 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.
- Qualification: Review exploit-research requests at the provider; specific victim deployments are not established at this stage.
- No direct MagicSword prevention claim is recorded for this stage.

### step-2: Provider-side abuse investigation
- Visibility: Provider / operator records
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/provider.sigma.yml
- KQL query download: /api/detections/provider.kql
- SPL query download: /api/detections/provider.spl
- Hunt hypothesis: A model-provider investigation correlates related accounts, repeated offensive requests and shared infrastructure or exposed operator sessions.
- Required telemetry: Provider-owned account / request audit; Abuse-review findings and linked-account context; Lawfully available exposed operator-session evidence
- Investigate: Correlate accounts, request rates, infrastructure and source-described behavior in provider-owned records.
- Investigate: For victim-side defense, pivot to the reported execution or access stage rather than trying to detect attacker-side prompts.
- Limitation: 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.
- No direct MagicSword prevention claim is recorded for this stage.

### step-3: Provider-side abuse investigation
- Visibility: Provider / operator records
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/provider.sigma.yml
- KQL query download: /api/detections/provider.kql
- SPL query download: /api/detections/provider.spl
- Hunt hypothesis: A model-provider investigation correlates related accounts, repeated offensive requests and shared infrastructure or exposed operator sessions.
- Required telemetry: Provider-owned account / request audit; Abuse-review findings and linked-account context; Lawfully available exposed operator-session evidence
- Investigate: Correlate accounts, request rates, infrastructure and source-described behavior in provider-owned records.
- Investigate: For victim-side defense, pivot to the reported execution or access stage rather than trying to detect attacker-side prompts.
- Limitation: 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.
- No direct MagicSword prevention claim is recorded for this stage.

### step-4: No source-backed runtime hunt yet
- Visibility: Not established
- Query origin: catalog_authored; status: not_applicable; log scope: gap
- Hunt hypothesis: The supplied account does not establish a deployed victim-side behavior for this stage.
- Required telemetry: not assessed
- Investigate: Obtain a source-backed procedure and identify which party could observe it before drafting a detection.
- Limitation: Marketing claims, unknown steps and unconfirmed deployments are not detection coverage. No rule is generated for this stage.
- Qualification: The supplied account leaves this stage unestablished. Obtain a source-backed procedure before proposing a runtime query.
- No direct MagicSword prevention claim is recorded for this stage.


## MITRE ATLAS
Mappings are catalog annotations based on described behavior, not assignments or endorsements by MITRE.
- AML.T0016.002: Generative AI — The supplied source explicitly describes generative-model tooling assisting the reported activity; this mapping does not establish additional autonomy or victim impact.
  Technique: https://atlas.mitre.org/techniques/AML.T0016.002
  Evidence: https://cloud.google.com/blog/topics/threat-intelligence/threat-actor-usage-of-ai-tools/

## Defensive notes
Supply-chain integrity; browser/edge device patching

## Sources
- https://cloud.google.com/blog/topics/threat-intelligence/threat-actor-usage-of-ai-tools/
