★ Deployer linked within 3 hops to DPRK/Lazarus
StakeWise v3's assessment for RD-F-125 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
[★ CRITICAL FACTOR] No DPRK/Lazarus cluster proximity identified across all accessible hops. Deployer 0x229f53ef: 1-hop = Binance 16 (major CEX, definitionally not a DPRK cluster). Checked Safe signers: signer 4 (1-hop = Binance 18 — clean), signer 6 (1-hop = Coinify 1 — clean regulated processor), signer 7/tsudmi.eth (1-hop = unlabelled peer-to-peer, pre-2021, no DPRK label). Web search 'StakeWise DPRK Lazarus North Korea developer': returned zero StakeWise-specific results. OFAC SDN public list: no StakeWise entities or addresses. Protocol leadership (Tsumak, Kutakov) based in Tallinn, Estonia with verifiable real-world employment histories spanning TradFi (Avaron AM) and engineering — no DPRK proximity indicators. No escalation required.
Sources #
- URLLazarus Group developer attacks (general) — no StakeWise mentioned in search resultsWeb search 'StakeWise DPRK Lazarus North Korea developer' — no StakeWise-specific results returned; only generic Lazarus group educationretrieved 2026-05-16
- StakeWise: Deployer 1 — Etherscan funding chainEtherscan deployer 0x229f53ef — Funded By Binance 16; 1-hop = major CEX, not a DPRK clusterretrieved 2026-05-16
Methodology #
Determine whether the deployer address has an on-chain path of ≤3 hops to a Chainalysis/OFAC DPRK-labeled cluster address.
See the full factor methodology and distribution across all protocols →