【Blockchain Rhythm】The decentralized trading protocol FutureSwap on the Arbitrum chain has been attacked again. According to monitoring by security research institutions, the damage caused by this incident amounts to approximately $74,000.
This time, the attacker used a classic reentrancy vulnerability, but the execution was quite sophisticated—divided into two stages. First, three days ago, the attacker exploited a loophole when providing liquidity, using reentrant calls to mint far more LP tokens than normal. Then, they waited—an entire 3 days. This time gap was crucial, likely to bypass certain protective mechanisms or wait for on-chain state changes.
The second stage was the harvest—the attacker used these illegally minted LP tokens to burn and redeem, directly withdrawing the underlying collateral assets. From the protocol’s perspective, it had no idea how these LP tokens were generated and was simply drained of real assets.
This is not the first time FutureSwap has had security issues. Similar reentrancy vulnerabilities are actually common Achilles’ heels for DeFi protocols, and many projects have fallen victim to them. For users, this is also a reminder—no matter how tempting the yields from liquidity mining are, you must first check the protocol’s security audit reports.
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
11 Likes
Reward
11
7
Repost
Share
Comment
0/400
BoredRiceBall
· 1h ago
Old tricks again, using a 3-day time gap to play psychological warfare here? This protocol is really quite something.
View OriginalReply0
MysteryBoxAddict
· 8h ago
Wait three days in each phase before taking action. This tactic is really brilliant; anyone else would be caught off guard.
View OriginalReply0
DegenDreamer
· 8h ago
Another reentrancy vulnerability... FutureSwap is really playing hard this time, waiting three days before harvesting. This kind of thinking really is impressive.
View OriginalReply0
GmGnSleeper
· 8h ago
Another reentrancy vulnerability... FutureSwap was heavily exploited this time. The three-day gap in operations was indeed meticulous, making it a textbook-style attack.
View OriginalReply0
MetaverseLandlady
· 8h ago
Reentrancy vulnerabilities are still happening in 2024. This team really doesn't take security seriously.
View OriginalReply0
FlashLoanLord
· 8h ago
Reentrancy vulnerabilities are still being exploited in 2024? FutureSwap's performance this time is a bit disappointing.
View OriginalReply0
NFTregretter
· 8h ago
Reentrancy vulnerabilities keep popping up? This protocol is really hopeless, why are people still willing to use it?
FutureSwap on Arbitrum suffers re-entrancy attack again, losing $74,000 in funds
【Blockchain Rhythm】The decentralized trading protocol FutureSwap on the Arbitrum chain has been attacked again. According to monitoring by security research institutions, the damage caused by this incident amounts to approximately $74,000.
This time, the attacker used a classic reentrancy vulnerability, but the execution was quite sophisticated—divided into two stages. First, three days ago, the attacker exploited a loophole when providing liquidity, using reentrant calls to mint far more LP tokens than normal. Then, they waited—an entire 3 days. This time gap was crucial, likely to bypass certain protective mechanisms or wait for on-chain state changes.
The second stage was the harvest—the attacker used these illegally minted LP tokens to burn and redeem, directly withdrawing the underlying collateral assets. From the protocol’s perspective, it had no idea how these LP tokens were generated and was simply drained of real assets.
This is not the first time FutureSwap has had security issues. Similar reentrancy vulnerabilities are actually common Achilles’ heels for DeFi protocols, and many projects have fallen victim to them. For users, this is also a reminder—no matter how tempting the yields from liquidity mining are, you must first check the protocol’s security audit reports.