North Korea runs cyber operations as a state revenue stream as well as an intelligence service, so the same regime that spies on diplomats also steals cryptocurrency, robs banks and places fake IT workers inside Western companies. US authorities attribute this activity to units of the Reconnaissance General Bureau (RGB), and the FBI has attributed thefts as large as the roughly 1.5 billion US dollars taken from Bybit in February 2025. This guide is the hub for North Korean activity in NHI Mgmt Group content: it maps the main clusters (Lazarus Group, APT38, Kimsuky, Andariel and newer groups), explains the revenue and espionage playbooks, and sets out the identity-centred controls that interrupt them. It is written for threat intelligence analysts, SOC leads, security architects and leaders in finance, crypto, defence, technology and policy organisations. The group-level detail sits in the individual profiles linked throughout, starting with the Lazarus Group Threat Actor Profile.
Key takeaways
- One state, many overlapping clusters. MITRE ATT&CK notes that North Korean units share personnel, infrastructure and malware, and that many researchers report all of it as Lazarus Group; track the behaviours, not just the names.
- Revenue is a strategic mission. The US Treasury said in 2019 that Bluenoroff was formed to earn revenue in response to sanctions, partly to fund nuclear and ballistic missile programmes.
- Identity is the common entry point. Fake recruiters, spoofed journalists, trojanised developer tools and fraudulent job applicants all aim to obtain a trusted identity, a session token or a signing path.
- Developers and finance staff are prime targets. The Bybit theft ran through a developer's cloud session; the AppleJeus cases used trojanised trading apps; IT worker schemes copy source code repositories.
- Controls span HR, email and cloud. Candidate identity verification, DMARC at enforcement, phishing-resistant MFA, short-lived tokens and monitoring of code and wallet signing paths each break a different playbook.
Who runs North Korean cyber operations
US government sources place the cyber units under the RGB, North Korea's primary intelligence organisation. Treasury's September 2019 sanctions designated Lazarus Group, Bluenoroff and Andariel as controlled by the RGB, with Lazarus subordinate to the 110th Research Center of the RGB's 3rd Bureau and Bluenoroff and Andariel described as sub-groups of Lazarus. A May 2024 FBI, State Department and NSA advisory describes Kimsuky as subordinate to the RGB's 63rd Research Center.
| Cluster (ATT&CK ID) | Common aliases | Main mission | NHI Mgmt Group profile |
|---|---|---|---|
| Lazarus Group (G0032) | HIDDEN COBRA, Labyrinth Chollima, ZINC, Diamond Sleet | Espionage, destructive attacks, theft; often used as an umbrella term | Lazarus Group Threat Actor Profile |
| APT38 (G0082) | Bluenoroff, BeagleBoyz, Stardust Chollima, Sapphire Sleet | Financial operations against banks, SWIFT endpoints, ATMs, casinos and crypto exchanges | APT38 Threat Actor Profile Guide |
| Kimsuky (G0094) | APT43, Emerald Sleet, Velvet Chollima, Black Banshee, THALLIUM | Espionage on Korean Peninsula policy, nuclear issues and sanctions | Kimsuky Threat Actor Profile |
| Andariel (G0138) | Silent Chollima, Onyx Sleet, PLUTONIUM | Espionage on South Korean government and military; financial operations against ATMs, banks and exchanges | Andariel Threat Actor Profile Guide |
| APT37 (G0067) | ScarCruft, Reaper, InkySquid, Ricochet Chollima | Espionage, mainly against South Korea | APT37 Threat Actor Profile Guide |
| AppleJeus (G1049) | Citrine Sleet, UNC4736, Gleaming Pisces | Cryptocurrency theft via trojanised trading software | Covered in this guide |
| Contagious Interview (G1052) | DeceptiveDevelopment, DEV#POPPER, PurpleBravo | Fake job interviews targeting developers; credential and crypto theft | Contagious Interview Threat Actor Profile Guide |
| Moonstone Sleet (G1036) | Storm-1789 | Fake companies and personas; financial and espionage operations | Covered in this guide |
ATT&CK states that North Korean group definitions overlap significantly. Treat names from different vendors as approximate, and map detections to techniques rather than to a single cluster label. For how vendor naming schemes relate, see the Threat Actor Groups Guide.
Revenue generation operations
The financial playbook has moved from banks to cryptocurrency and, more recently, to insiders on payroll.
Bank and payment system theft
- SWIFT fraud: the February 2021 US indictment of three RGB officers alleges attempts from 2015 to 2019 to steal more than 1.2 billion US dollars from banks in Vietnam, Bangladesh, Taiwan, Mexico, Malta and Africa using fraudulent SWIFT messages. Treasury cited about 80 million US dollars taken from the Central Bank of Bangladesh's account at the New York Federal Reserve after requests totalling 851 million.
- ATM cash-out: the same indictment describes a FASTCash scheme, including 6.1 million US dollars stolen from BankIslami Pakistan in October 2018.
Cryptocurrency theft
- Exchange intrusions: Treasury cited industry reporting that the three sanctioned groups likely stole about 571 million US dollars in cryptocurrency from five Asian exchanges between January 2017 and September 2018.
- Trojanised trading apps: the indictment lists AppleJeus-family applications such as Celas Trade Pro, WorldBit-Bot, Union Crypto Trader, Kupay Wallet, CoinGo Trade, Dorusio, CryptoNeuro Trader and Ants2Whale.
- Supply chain into signing: on 26 February 2025 the FBI stated North Korea was responsible for the theft of about 1.5 billion US dollars from Bybit, naming the activity TraderTraitor. The Bybit hack ran through a Safe{Wallet} developer's laptop and hijacked AWS session tokens that bypassed MFA, which let the attackers change the code shown to signers.
IT worker schemes
North Korean IT workers obtain remote jobs under false identities and send their wages to the regime. The FBI's January 2025 public service announcement warned that, once discovered, some have held stolen data and code to ransom and in some cases released proprietary code publicly. They copy company repositories to personal accounts and harvest credentials and session cookies to work from non-company devices. See the Insider Threat from Fake IT Workers Guide (North Korean IT Worker Schemes) and the Hiring Fraud and Candidate Identity Verification Guide.
Espionage operations
- Policy and nuclear intelligence: ATT&CK describes Kimsuky collecting on foreign policy, national security, nuclear policy and sanctions, with targets in South Korea, the United States, Japan, Russia, Europe and the United Nations.
- Spoofed experts: the May 2024 FBI, State and NSA advisory describes Kimsuky posing as journalists, academics and East Asia experts, spoofing legitimate domains with weak or missing DMARC policies and changing Reply-To addresses so answers reach actor accounts. Targets include think tanks, universities, media, government staff and military members.
- Defence and technology: Lazarus-attributed activity and Andariel target defence and government organisations, with ATT&CK noting Andariel's destructive attacks against South Korean targets.
- Use of AI: ATT&CK records that Kimsuky was observed in 2023 using commercial large language models for vulnerability research, scripting, social engineering and reconnaissance.
- Supply chain espionage: the JumpCloud breach began with spear phishing in June 2023 and was attributed by JumpCloud to a North Korean nation-state actor; attackers used the identity platform's command framework to reach a small number of customer devices.
Destructive and disruptive operations
North Korea is also willing to cause damage. The 2021 indictment describes the November 2014 destructive attack on Sony Pictures Entertainment and the creation of WannaCry 2.0 ransomware in May 2017. Treasury cited reporting that WannaCry affected at least 150 countries and shut down about 300,000 computers. ATT&CK links Lazarus to Operation Blockbuster reporting and to campaigns such as DarkSeoul and Ten Days of Rain against South Korea.
Tracking North Korean activity
Most of what defenders can act on comes from a small number of government and framework sources. Build them into your intelligence intake rather than relying on vendor blog summaries.
| Source | What it gives you | How to use it |
|---|---|---|
| FBI public service announcements (ic3.gov) | Formal US attribution of thefts, IT worker warnings, published wallet addresses | Feed addresses to transaction screening; turn employer recommendations into HR controls |
| Joint cybersecurity advisories (FBI, CISA, NSA, State Department) | Actor tradecraft, RGB unit attribution, specific mitigations such as DMARC settings | Map advisory techniques to detections and track remediation of each mitigation |
| US Treasury OFAC sanctions designations | Which groups and individuals are sanctioned | Sanctions checks before any payment to an extortionist or counterparty |
| US Department of Justice indictments | Named individuals, alleged schemes and losses | Context for risk assessments and board briefings |
| MITRE ATT&CK group pages | Aliases across vendors and technique sets per cluster | Build hunts and coverage maps by technique |
Naming discipline: record the source's own name for each event (for example the FBI's TraderTraitor for Bybit) alongside the ATT&CK group, and note the confidence the source states. This avoids reports that silently merge different clusters into "Lazarus".
Sharing: report suspected North Korean activity to the FBI through ic3.gov, as the advisories ask, and retain original emails and attachments for investigators. Sector ISACs are the fastest route for peer indicators.
How the identity playbooks work
| Playbook | Identity targeted | ATT&CK technique | Control that breaks it |
|---|---|---|---|
| Fake recruiter or job interview | Developer workstation and its tokens | T1566.002 Spearphishing Link; T1204.002 Malicious File; T1585.001 Social Media Accounts | No code tests on corporate devices; EDR; awareness for engineers |
| Spoofed journalist or academic | Expert's mailbox and credentials | T1566.001 Spearphishing Attachment; T1684.001 Impersonation | DMARC p=reject; Reply-To inspection; phishing-resistant MFA |
| Trojanised trading or developer software | Wallet keys, exchange credentials | T1195.002 Compromise Software Supply Chain | Allowlisted software; isolated signing devices |
| Hijacked developer cloud session | Session tokens with deploy rights | T1078 Valid Accounts | Short-lived tokens, device-bound sessions, deploy approvals |
| Fake IT worker | A legitimate employee identity | T1078 Valid Accounts; T1213 Data from Information Repositories | Identity proofing, device and location checks, repository exfiltration alerts |
| Data extortion after discovery | Copied source code and data | T1657 Financial Theft; T1567 Exfiltration Over Web Service | Least privilege on repositories; offboarding that revokes all tokens at once |
Package registry abuse is a growing channel. The axios npm compromise shows a hijacked publishing account used to spread a North Korean backdoor; see the npm Tokens Security Guide.
Detection and defence programme
Phased approach
- Know your exposure (month 1): list the people and systems North Korean playbooks target in your organisation: developers with production or signing rights, treasury and wallet operators, policy experts, remote contractors and HR recruiters.
- Close the email gap: move DMARC from p=none to p=quarantine and then p=reject, with rua aggregate reporting, as the 2024 advisory recommends. Monitor reports for two to four weeks at quarantine before reject so legitimate senders are not lost; reverting the DNS record is the rollback. See the DMARC, SPF and DKIM Guide.
- Harden developer and signing paths: require phishing-resistant MFA, shorten cloud session lifetimes for accounts that can deploy, require a second approver for production releases and keep wallet signing on dedicated devices. Pilot on one team before mandating.
- Fix hiring and onboarding: apply the FBI's employer recommendations: verify identity during interviewing, onboarding and employment; cross-check applicants for reused CV content, VoIP numbers and emails; audit staffing firms; and complete as much onboarding in person as possible.
- Detect insiders that are not who they claim: alert on remote desktop tools, multiple concurrent video call software, logins to one account from different countries in a short period, and repository cloning to personal accounts.
- Prepare for extortion: agree in advance who decides on response if a dismissed worker threatens to release code, and check sanctions obligations before any payment. See the Ransomware Payments and Sanctions Guide.
Decision guidance
- Crypto and fintech firms: assume you are targeted. Prioritise signing path integrity, developer session controls and blocking transactions with addresses the FBI publishes, as it asked after Bybit.
- Software companies hiring remotely: the IT worker risk outweighs most malware risk; invest in identity proofing and device checks first.
- Think tanks, universities and media: DMARC enforcement and training on impersonated experts give the biggest return; a small organisation can do both in weeks.
- Large enterprises: build North Korea-specific hunts from ATT&CK technique sets and share indicators through sector ISACs.
Metrics
- Percentage of owned sending domains at DMARC p=reject.
- Percentage of accounts with production deploy or signing rights using phishing-resistant MFA and sessions under 12 hours.
- Percentage of remote hires completing identity verification at offer and at a later check.
- Number of repository clones to unmanaged or personal destinations alerted and triaged per month.
- Time from detecting a fraudulent worker to full revocation of their accounts, tokens and keys.
Framework mapping
| Control area | NIST CSF 2.0 | NIST SP 800-53 Rev. 5 | CIS Controls v8.1 |
|---|---|---|---|
| Personnel screening and identity proofing | GV.RR-04 | PS-3, IA-12 | Control 5 Account Management |
| Email authentication | PR.PS-01 | SI-8 | Control 9 Email and Web Browser Protections |
| Phishing-resistant MFA and sessions | PR.AA-03 | IA-2, AC-12 | Control 6 Access Control Management |
| Software supply chain | GV.SC-05 | SR-3 | Control 16 Application Software Security |
| Awareness | PR.AT-01 | AT-2 | Control 14 Security Awareness and Skills Training |
| Threat intelligence and monitoring | ID.RA-02, DE.CM-01 | PM-16, SI-4 | Control 13 Network Monitoring and Defense |
Common failure patterns
- Treating a cluster name as the whole threat: blocking indicators for one named group while a sister cluster uses the same lure with new infrastructure.
- Coding tests on corporate laptops: engineers running a recruiter's take-home project on the machine that holds production credentials.
- Long-lived developer sessions: cloud sessions that stay valid for days on laptops that can push code, as in the Bybit case.
- DMARC left at p=none: the 2024 advisory singles this out as the gap Kimsuky exploits.
- Hiring checks done once: identity verified at interview but never again, so a different person can do the job.
- Partial offboarding: disabling the directory account but leaving personal access tokens, SSH keys and cloud keys active.
Lessons from incidents
- Bybit (2025): a single developer's authenticated session was enough to alter what signers saw. Bind deploy sessions to managed devices and require independent verification of what is being signed.
- JumpCloud (2023): the attacker persisted past the first credential rotation, and JumpCloud later force-rotated all customer admin API keys. Plan rotations as one coordinated event and treat identity vendors as Tier 0.
- axios npm (2026): a hijacked publishing account spread a backdoor quickly through automated dependency updates. Use trusted publishing and slow down auto-merge for new releases.
Practitioner checklist
- Map which North Korean playbooks apply to your sector and name the exposed roles.
- Set DMARC to p=reject on all sending domains, with aggregate reporting.
- Require phishing-resistant MFA and short, device-bound sessions for anyone with deploy, signing or treasury rights.
- Ban recruiter coding tests and unsolicited trading or wallet software on corporate devices.
- Adopt the FBI's remote hiring checks and repeat identity verification after onboarding.
- Alert on repository cloning to personal accounts and on remote desktop or concurrent video call tools.
- Build offboarding that revokes every token, key and session in one action.
- Block transactions with wallet addresses the FBI attributes to North Korean actors if you operate in crypto.
- Check sanctions obligations before any extortion payment.
Standards and references
- FBI: North Korea Responsible for $1.5 Billion Bybit Hack
- FBI: North Korean IT Workers Conducting Data Extortion
- FBI, US Department of State, NSA: North Korean Actors Exploit Weak DMARC Security Policies to Mask Spearphishing Efforts
- US Department of the Treasury: Treasury Sanctions North Korean State-Sponsored Malicious Cyber Groups
- US Department of Justice: Three North Korean Military Hackers Indicted in Wide-Ranging Scheme to Commit Cyberattacks and Financial Crimes
- MITRE ATT&CK: Lazarus Group (G0032)
- MITRE ATT&CK: Kimsuky (G0094)
- MITRE ATT&CK: APT38 (G0082)
Related NHI Mgmt Group resources: Lazarus Group Threat Actor Profile · Insider Threat from Fake IT Workers Guide (North Korean IT Worker Schemes) · Crypto Exchange Identity and Key Security Guide · Threat Actor Groups Guide