★ Deployer linked within 3 hops to DPRK/Lazarus
Beefy Finance'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 #
No OFAC SDN designation found for any Beefy team address or the deployer's funding chain. Web search 'Beefy Finance team DPRK Lazarus North Korea sanctioned' returned zero adverse results — results cover general DPRK/Lazarus information with no Beefy mention. No Chainalysis-published report links any Beefy address to a DPRK-labeled cluster. Arkham returned 403 (no access). Deployer funding chain 2-hop trace shows only unlabeled August-2020 wallets with minimal DeFi activity — no DPRK proximity. Attacker routing through Beefy vaults (Sonne Finance 2024) does not constitute team DPRK linkage per rubric standing rule (U4). No escalation required.
Sources #
- URLOFAC Targets DPRK IT Workers Using Crypto — ChainalysisWeb search 'Beefy Finance team DPRK Lazarus North Korea sanctioned' — zero adverse results returned; all results are general Lazarus/DPRK articles with no Beefy mentionretrieved 2026-05-16
- OFAC SDN List | U.S. Department of the TreasuryOFAC SDN list search — no Beefy Finance or associated address entriesretrieved 2026-05-16
- 0x010dA5FF... funder address | Etherscanetherscan.io/address/0x010da5ff... and 0x65685579... — 2-hop funding chain; no DPRK/Lazarus cluster label on any hopretrieved 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 →