DIP Exploit Drains $111K After Router Transfer Executes Twice
The DIP exploit drained an estimated $111,000 on BNB Chain after a flaw in DIP’s customized transfer logic let the same router-linked token movement execute twice.
According to the report, the attacker abused how the AIC/DIP liquidity pair handled accounting. The duplicated settlement broke the usual AMM assumption that one transfer request should cause one net balance change. The attacker then manipulated the pool so its live DIP balance matched exactly twice the recorded reserve (2R vs. R). A first DIP transfer reduced the balance from 2R to R, and the second transfer removed the remaining R, emptying the real DIP reserve.
Afterward, the attacker used the AIC/DIP pair’s reserve sync and reverse settlement, receiving AIC from the compromised liquidity position. The proceeds were then converted via the related AIC/USDT pool, turning the accounting failure into stablecoin-denominated value.
The article notes the exploit did not stem from skim(router) or sync() malfunctioning; those behaved normally. The core fix is removing the second unconditional transfer in the router-specific path, plus follow-up work to verify the patched router route and rebuild the affected liquidity.
For traders, the DIP exploit highlights near-term smart-contract and LP risk around router-integrated token transfer logic, especially when pool accounting can be desynced.
Neutral
This news is largely contract- and pair-specific. The DIP exploit targets the AIC/DIP LP accounting and drains DIP reserve, which is likely to create localized sell pressure and liquidity stress for DIP/AIC (bearish for those tokens), but it should not automatically translate into broad market weakness for BTC/ETH because the attack vector is not a systemic protocol failure.
In the short term, traders often respond to confirmed exploits by reducing exposure to the affected pair, watching for halted trading, liquidity removal, and changes in pool reserves. Any remaining DIP or AIC in the market can see volatility around exploit news and after patch/deployment communications.
In the long term, if the fix is deployed correctly and affected liquidity is rebuilt, the event can shift from “active risk” to “resolved risk,” limiting sustained damage. Similar past router/transfer-path exploits typically cause a rapid repricing of the involved assets, while overall DeFi market impact is often secondary unless multiple pools or widely-used contracts are compromised.