Cases › security breach › LR-2026-0307
North Korean group uses AI to mass-produce tailored phishing PDFs against South Korean users
Preliminary Why: Publisher not yet named · subject to change
Severity moderate: Over 100 customized phishing documents were tailored to individual South Korean targets, and fake job offers targeted industry workers.
Earliest source we hold 2026-10-30 · Captured by AI Risk Wire 2026-11-01 00:47 UTC
North Korean hacking groups used AI tools, including the ARTEX open-source penetration-testing framework and AI coding tools such as Cursor, to mass-produce phishing lure documents, fake job offers and malware. One group created more than 100 customized PDF lure documents tailored to each target from August to September, and fake job offers were made to AI, blockchain and cybersecurity workers via three front companies. Microsoft Threat Intelligence reported the findings, evaluating that three of eight North Korean groups reached an "operational integration" stage, and recommended stronger identity verification for job applicants, phishing response and malware detection.
Risks this incident falls under
| Risk | Role | NIST AI 600-1 | Incidents | Last 6 quarters |
|---|---|---|---|---|
| AI used to run a cyber attack | Primary | Information Security | 38 | |
| AI system attacked or breached | Also | Information Security | 1 |
Sorted by rule from the case's fields; not yet read from the sources.
Control failure chain
L1 · ModelProvider not namedModel provider
Sources not yet read for controls.
Model version not linked to a model card.
Other controls for this risk at this layer, not yet read for: Safety training and refusal, Cyber and weapons safeguards, Abuse monitoring and account enforcement, Staged or restricted release, Dangerous-capability testing before release, Outside red-teaming, Content safety classifiers, Safeguards kept on in testing, Reasoning monitoring.
L2 · HarnessARTEXAgent framework vendor
Sources not yet read for controls.
L3 · ApplicationDeployer not namedDeployer
Sources not yet read for controls.
L4 · Infrastructure / targetOrganisation hit
Sources not yet read for controls.
Other controls for this risk at this layer, not yet read for: Known flaws patched, Multi-factor sign-in and password policy, Network segmentation, Intrusion and endpoint detection, Backups and recovery, Phishing and fraud filters.
HeldFailedGot aroundMissingNot mentionedNot read yetAttacker's ownOrder: model · harness · application · target
The same controls in other incidents of this risk
| Control | Layer | Here | Held elsewhere | Did not hold elsewhere |
|---|---|---|---|---|
| Content safety classifiers | L1 Model | Not read yet | ||
| Safety training and refusal | L1 Model | Not read yet | 1 | |
| Cyber and weapons safeguards | L1 Model | Not read yet | ||
| Dangerous-capability testing before release | L1 Model | Not read yet | ||
| Outside red-teaming | L1 Model | Not read yet | ||
| Staged or restricted release | L1 Model | Not read yet | ||
| Abuse monitoring and account enforcement | L1 Model | Not read yet | ||
| Reasoning monitoring | L1 Model | Not read yet | 1 | |
| Safeguards kept on in testing | L1 Model | Not read yet | ||
| Known flaws patched | L4 Infrastructure / target | Not read yet | ||
| Multi-factor sign-in and password policy | L4 Infrastructure / target | Not read yet | ||
| Network segmentation | L4 Infrastructure / target | Not read yet | ||
| Intrusion and endpoint detection | L4 Infrastructure / target | Not read yet | ||
| Backups and recovery | L4 Infrastructure / target | Not read yet | ||
| Phishing and fraud filters | L4 Infrastructure / target | Not read yet |
Risk grouping: Not yet classified
No source we hold states: who caused it, intended or not, before or after release, the ai's part.
The story
No source states: when it happened, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case, the cause, what set it off.
Others like this
Show every field, with its source and grade
The AI system
What happened
Impact
Context
LR-2026-0307 · version 2 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · changes to this case · JSON