Moderate risk — battle-tested Aave V3 base provides strong foundation, but self-repaying loan complexity, young Monad infrastructure, and concentrated veTokenomics governance add meaningful risk layers.
Top Risks
1
Pre-launch security audit by Composable Security found 23 issues including 1 critical and 3 high vulnerabilities. While these were resolved before deployment, the high issue count suggests complex attack surface that may harbor additional undiscovered vulnerabilities.
2
Monad-native deployment means the protocol is tied to Monad's relatively new and less battle-tested infrastructure. Monad is a young EVM-compatible L1, and its reliability under stress has not been extensively proven.
3
veTokenomics with veDUST governance directing 100% of protocol revenue creates incentive for governance capture — concentrated veDUST holders could redirect all protocol income to themselves at the expense of other users.
4
Self-repaying loan functionality adds complexity beyond the base Aave V3 architecture, creating additional attack surface in the repayment automation logic.
Risk Breakdown
Frequently Asked Questions
Is Neverland safe to use?
Neverland receives a C+ risk grade (37/100) from Hindenrank, where lower scores indicate lower risk. Moderate risk — battle-tested Aave V3 base provides strong foundation, but self-repaying loan complexity, young Monad infrastructure, and concentrated veTokenomics governance add meaningful risk layers. Neverland is a Monad-native lending protocol built on the battle-tested Aave V3 architecture, featuring self-repaying loans and veTokenomics through the Pixie Dust (DUST) governance token. With approximately $21M TVL on Monad mainnet, it underwent a security review by Composable Security that identified and resolved 23 issues including 1 critical and 3 high vulnerabilities before deployment. Its B- risk grade reflects the added complexity of self-repaying loan automation on top of Aave V3, dependency on the young Monad L1 chain, and governance concentration risk from veDUST directing 100% of protocol revenue.
What are the main risks of using Neverland?
The key risks identified for Neverland are: (1) A pre-launch security audit found 23 issues including 1 critical and 3 high-severity vulnerabilities. While all were resolved before deployment, the high finding count suggests complex code with a significant attack surface that may harbor additional undiscovered issues. (2) Self-repaying loans add automated yield-to-repayment logic on top of the base Aave V3 framework. This additional complexity creates new potential attack vectors not present in standard Aave V3 deployments, similar to the type of auxiliary feature that caused the Euler Finance exploit ($197M loss). (3) veDUST governance allows holders to direct 100% of protocol revenue. If governance becomes concentrated, a single entity could redirect all protocol income to their own positions while also influencing lending parameters like collateral factors and interest rates. (4) Monad is a relatively new L1 blockchain whose reliability under market stress has not been extensively proven. If Monad experiences network issues, all lending operations including liquidations and oracle updates would pause, potentially creating bad debt.
What is Neverland's risk score breakdown?
Neverland scores 37/100 across eight risk dimensions: Mechanism Novelty: 3/15, Interaction Severity: 6/20, Oracle Surface: 2/10, Documentation Gaps: 2/10, Track Record: 10/15, Scale Exposure: 3/10, Regulatory Risk: 5/10, Vitality Risk: 6/10. The highest risk area is Track Record at 10/15.
How does Neverland compare to other Lending protocols?
Among 90 rated Lending protocols on Hindenrank, Neverland ranks #52 by safety (lowest risk score = safest). Its 37/100 risk score and C+ grade place it in the middle tier of Lending protocols.
Has Neverland ever been hacked or exploited?
Neverland 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.