Sentiment Protocol Exploit Exposes Read-Only Reentrancy Vulnerability on Arbitrum

A sophisticated read-only reentrancy attack on the Sentiment Protocol has resulted in the loss of approximately $1 million in user funds, casting a spotlight on persistent smart contract vulnerabilities in DeFi systems built on layer-2 networks.

The Exploit Mechanics

The attacker exploited a well-documented read-only reentrancy bug within Sentiment’s integration with the decentralized exchange Balancer. At approximately 17:50 UTC on April 4, the hacker manipulated the interaction between Sentiment and Balancer’s liquidity pools, tricking the protocol into allowing withdrawals far exceeding the attacker’s actual deposits. The stolen funds were denominated in USDC, USDT, wrapped Bitcoin, and Ether — all quickly converted to ETH and bridged from Arbitrum back to the Ethereum mainnet.

Read-only reentrancy attacks differ from classic reentrancy exploits. Rather than repeatedly calling a withdraw function, the attacker exploits a window where a contract’s state has not yet been updated after an external call. In Sentiment’s case, the Balancer pool integration failed to properly guard against stale state reads, enabling the attacker to inflate their balance assessment and drain funds. According to Igor Igamberdiev, head of research at Wintermute, at least three protocols have suffered exploits using this specific read-only reentrancy vector since its discovery by ChainSecurity over a year prior.

Affected Systems

Sentiment is a DeFi lending protocol operating on Arbitrum, one of Ethereum’s most prominent layer-2 scaling solutions. The exploit specifically targeted the protocol’s balance-checking mechanism tied to Balancer pools, which serve as the primary liquidity source. The attack affected all users who had deposited funds into Sentiment’s lending markets. Notably, Sentiment holds insurance coverage through Sherlock, a smart contract audit marketplace, with $2 million in coverage — enough to potentially cover the full extent of losses if the claim is validated.

The Mitigation Strategy

Following the exploit, Sentiment’s team moved swiftly to deploy an emergency fix. In an on-chain message sent to the attacker’s wallet, the protocol offered a $95,000 bounty — roughly 10% of the stolen funds — for the return of all assets by April 6, 08:00 UTC. If the hacker declined, the same bounty was offered to anyone who could help identify and prosecute the responsible party. This approach mirrors a growing trend in DeFi where protocols negotiate with attackers through on-chain messages, a strategy that recently succeeded when Euler Finance recovered nearly all of its $200 million in stolen funds after similar negotiations.

Lessons Learned

The Sentiment exploit underscores a troubling pattern: known vulnerabilities continue to claim victims months or even years after discovery. The read-only reentrancy bug was identified by ChainSecurity well before this attack, yet protocols integrating with Balancer and Curve pools without implementing proper guards remain exposed. With Bitcoin trading near $28,178 and Ethereum at $1,909, the DeFi ecosystem holds billions in total value locked, making thorough security audits and continuous re-evaluation of integrations an operational necessity rather than an optional expense.

User Action Required

If you have funds deposited in Sentiment or any protocol with Balancer or Curve pool integrations, revoke all outstanding token approvals immediately. Verify whether the protocols you use have implemented reentrancy guards specifically for read-only reentrancy vectors. Monitor official Sentiment channels for updates on the insurance claim process through Sherlock, and exercise heightened caution with any Arbitrum-based lending protocol that has not undergone a comprehensive re-audit since this vulnerability class was disclosed.

Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Always conduct your own research before engaging with any DeFi protocol.