DPRK Cyber IndexYearsActorsSourcesAttacks on North KoreaMethodologyContributeSearch

UnoRe DAO

Date (as written)
2023-11
Year
2023
Country
Estonia
Actor pages
did not attribute the activity to a named threat actor
Tags (as written)
FinancialGain Cryptocurrency
Dollar figures (as written)
$219,000; 219,000

Source entries (4)

lazarus.day

UnoRe DAO · 2023-11
On November 14, 2023 at approximately 15:49 UTC, Uno Re suffered a deployer private-key compromise that let an attacker transfer contract ownership, alter the claims assessor role, and drain SSIP, SSRP, and Rewarder contracts. Uno Re reported losses of 32.4 million UNO, 127.9 thousand USDC, 59.3 thousand USDT, and 18.4 ETH, with stolen UNO sold through Uniswap and PancakeSwap before proceeds moved through exchanges, mixers, swaps, and additional chains.
https://lazarus.day/incidents/unore/

tayvano/lazarus-bluenoroff-research

UnoRe DAO · 2023-11-14
Amt Stolen: $219,000
https://github.com/tayvano/lazarus-bluenoroff-research/blob/main/hacks-and-thefts/unoredao.md

UN Panel of Experts S/2024/215

Uno Re Dao (possibly DPRK IT workers) · 14 November 2023
Annex 95: Suspected DPRK cyberattacks on cryptocurrency-related companies (2017-2023) investigated by the Panel. Table 2023: Victim: Uno Re Dao (possibly DPRK IT workers); Date: 14 November; Amount (USD equivalent): 219,000; Location: Estonia
https://undocs.org/S/2024/215

Mendeley Data: Collection of DPRK state-sponsored threat actors' activities v2 (Lyu, Sungkyunkwan Univ.)

UnoRe DAO · 2023-11
Reported: 2023-11; Victims: UnoRe DAO; Motivations: FinancialGain; Sectors: Cryptocurrency; Countries: Estonia
https://data.mendeley.com/datasets/wwb2rzgfn7/2

Values found later for empty fields

actors: did not attribute the activity to a named threat actor
Forensic work suggested the attack may be part of a broader operation targeting developer and deployer accounts, with DareNFT and LunaFi cited as related examples, but the report did not attribute the activity to a named threat actor.
https://lazarus.day/reports/security-incident-post-mortem-report-and-the-road-ahead-HUo5N/

Suggest a correction on GitHub