dForceMicro-cap

dForce receives a B- risk grade (35/100) from Hindenrank, where lower scores indicate lower risk. High risk — hacked twice with the same bug class and the multi-chain deployment multiplies every vulnerability across 7+ chains A lending and stablecoin protocol deployed across 7+ blockchains including Ethereum, Arbitrum, and BSC, managing about $100M in deposits. Its D+ grade reflects two separate hacks ($25M in 2020, $3.64M in 2025) and the amplified risk of running the same code on many chains.

The key risks identified for dForce are: (1) dForce has been hacked twice. The same type of bug (reentrancy) was exploited both times, five years apart. A pattern of repeated exploits suggests deeper code quality issues (2) The same code runs on 7+ chains. When the 2025 hack hit Arbitrum, the identical bug existed on Optimism too. One vulnerability means simultaneous losses on every chain (3) The USX stablecoin depends on liquidation bots that vary in quality across chains. On smaller chains like KAVA, bots are slow or absent, so bad debt piles up and USX can lose its peg

dForce scores 35/100 across eight risk dimensions: Mechanism Novelty: 0/15, Interaction Severity: 8/20, Oracle Surface: 2/10, Documentation Gaps: 5/10, Track Record: 10/15, Scale Exposure: 0/10, Regulatory Risk: 5/10, Vitality Risk: 5/10. The highest risk area is Track Record at 10/15.

Among 90 rated Lending protocols on Hindenrank, dForce ranks #43 by safety (lowest risk score = safest). Its 35/100 risk score and B- grade place it in the middle tier of Lending protocols.

dForce scores 10/15 on the Track Record risk dimension, indicating some history of security incidents or exploits. Higher scores reflect more severe or frequent incidents. Review the full risk report for details.