Dexodus, Zora, Numa: $946K Lost to Replays, Access Bugs, and Locked-in Prices
Dexodus let a stale Chainlink report slip through and lost $291K. Zora’s airdrop logic had no access control, leaking $128K. Numa’s sell-burn-lock flow inflated token price mid-loan, costing $527K. Every failure was one unchecked line.
In Brief
Dexodus lost $291K in a signature replay attack.
Zora was exploited for $128K after missing access controls in their token claim function.
Numa suffered a $527K loss due to a flash loan price manipulation.
Hacks Analysis
Dexodus | Amount Lost: $291K
On May 26, the Dexodus Finance exploit on Base chain resulted in a $291K loss due to a signature replay attack. The attacker used a valid but outdated Chainlink price report via the performUpkeep() function, which lacked proper timestamp validation. This allowed them to open a 100x leveraged long position on ETH at an artificially low price of $1,816. They then closed the position at the current market price of $2,520 within the same transaction, profiting approximately $291K.
Exploited Contract (Verifier Proxy on Base): 0xde1a28d87afd0f546505b28ab50410a5c3a7387a
On April 24, the Zora exploit on Base chain resulted in a $128K loss. The root cause of the exploit was that Zora’s TokenCommunityClaim contract’s claim() function didn’t have proper access control and allowed the attacker to input any _claimTo address. The attacker targeted addresses with unclaimed token allocations and used them as the _user parameter, while setting _claimTo to a contract they controlled. This allowed the attacker to reroute airdropped tokens to their own address.
Exploited Contract (Zora: Token Community Claim on Base): 0x0000000002ba96c69b95e32caab8fc38bab8b3f8
On April 18, the Numa exploit on Arbitrum resulted in a $527K loss due to a price manipulation exploit. The attacker used a flash loan to interact with the sell() function, which burned NUMA tokens and reduced total supply. This increased the token’s internal price. The attacker then locked the manipulated price using lockNumaSupply(). With the inflated value fixed, they borrowed assets from the protocol at favorable rates and withdrew them for profit.
Exploited Contract (on Arbitrum): 0x9857127d6987a177d87c13d2dfdaa771bf625a69
The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.
A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!
Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.
Follow-up: Conduct a follow-up review to ensure that the remediation steps were effective and that the smart contract is now secure.
Follow-up: Conduct a follow-up review to ensure that the remediation steps were effective and that the smart contract is now secure.
In Brief
Remitano suffered a $2.7M loss due to a private key compromise.
GAMBL’s recommendation system was exploited.
DAppSocial lost $530K due to a logic vulnerability.
Rocketswap’s private keys were inadvertently deployed on the server.
Hacks
Hacks Analysis
Huobi | Amount Lost: $8M
On September 24th, the Huobi Global exploit on the Ethereum Mainnet resulted in a $8 million loss due to the compromise of private keys. The attacker executed the attack in a single transaction by sending 4,999 ETH to a malicious contract. The attacker then created a second malicious contract and transferred 1,001 ETH to this new contract. Huobi has since confirmed that they have identified the attacker and has extended an offer of a 5% white hat bounty reward if the funds are returned to the exchange.
.webp)
