The claim() function in MerkleAirdrop.sol verifies that a user's address and amount are included in the merkle tree but never records whether an address has already claimed their tokens.
The Issue:
Merkle proofs are deterministic - the same proof remains valid indefinitely because the merkle tree is immutable. Without state tracking to record completed claims, any eligible user can submit the same valid proof multiple times to drain the entire contract balance.
What Happens:
Eligible user calls claim() with their valid proof and 1 gwei fee → receives 25 USDC
Same user calls claim() again with the identical proof → receives another 25 USDC
User repeats steps 1-2 until contract is fully drained
Why This Works:
The merkle tree stored in i_merkleRoot never changes
MerkleProof.verify() only checks if the proof is valid against the static tree
No mapping or state variable tracks which addresses have already claimed
Each call to claim() is treated as independent with no memory of previous claims
Attack Economics:
Attacker cost: 4 gwei in fees (4 calls × 1 gwei per call) ≈ $0.00
Attacker profit: 100 USDC (entire contract balance)
Victim loss: 3 legitimate users receive nothing despite being eligible
This is a Missing State Tracking vulnerability where critical access control logic fails to persist state across function calls, enabling unlimited exploitation by a single actor.
The root cause is the complete absence of claim tracking logic. The contract validates proof correctness but never persists the fact that a claim was executed, allowing infinite replay of valid proofs.
Likelihood:
Any eligible user who discovers the vulnerability can immediately exploit it with zero technical barriers. The same proof used for the first legitimate claim works identically for all subsequent malicious claims. There are no rate limits, no time delays, and no on-chain signals to prevent exploitation.
The vulnerability is trivially discoverable through basic interaction testing. An eligible user testing their claim twice will immediately observe they can claim multiple times. Given the financial incentive (75 USDC profit for ~$0.00 cost), rational actors will exploit this upon discovery
Impact:
100% fund theft with zero recovery. A single attacker drains the entire 100 USDC contract balance by calling claim() four times with the same proof. The attack completes in seconds and costs only 4 gwei (~$0.00) in fees, yielding a profit of 100 USDC while preventing all other eligible users from claiming
Catastrophic trust violation and protocol failure. Three of the four eligible users receive nothing despite being legitimately entitled to 25 USDC each. The airdrop mechanism completely fails its core purpose of fair token distribution. The protocol suffers permanent reputational damage as users realize the system enabled theft of their rightful allocations.
Key Changes:
Added s_hasClaimed mapping to track claimed addresses
Added MerkleAirdrop__AlreadyClaimed error for double-claim attempts
Check claim status at the start of claim() function
Set s_hasClaimed[account] = true before token transfer (follows Checks-Effects-Interactions pattern)
Optional: Added hasClaimed() view function for transparency
This mitigation ensures each address can only claim once, eliminating the replay attack vector entirely.
## Description A user eligible for the airdrop can verify themselves as being part of the merkle tree and claim their airdrop amount. However, there is no mechanism enabled to track the users who have already claimed their airdrop, and the merkle tree is still composed of the same user. This allows users to drain the `MerkleAirdrop` contract by calling the `MerkleAirdrop::claim()` function over and over again. ## Impact **Severity: High**<br/>**Likelihood: High** A malicious user can call the `MerkleAirdrop::claim()` function over and over again until the contract is drained of all its funds. This also means that other users won't be able to claim their airdrop amounts. ## Proof of Code Add the following test to `./test/MerkleAirdrop.t.sol`, ```javascript function testClaimAirdropOverAndOverAgain() public { vm.deal(collectorOne, airdrop.getFee() * 4); for (uint8 i = 0; i < 4; i++) { vm.prank(collectorOne); airdrop.claim{ value: airdrop.getFee() }(collectorOne, amountToCollect, proof); } assertEq(token.balanceOf(collectorOne), 100e6); } ``` The test passes, and the malicious user has drained the contract of all its funds. ## Recommended Mitigation Use a mapping to store the addresses that have claimed their airdrop amounts. Check and update this mapping each time a user tries to claim their airdrop amount. ```diff contract MerkleAirdrop is Ownable { using SafeERC20 for IERC20; error MerkleAirdrop__InvalidFeeAmount(); error MerkleAirdrop__InvalidProof(); error MerkleAirdrop__TransferFailed(); + error MerkleAirdrop__AlreadyClaimed(); uint256 private constant FEE = 1e9; IERC20 private immutable i_airdropToken; bytes32 private immutable i_merkleRoot; + mapping(address user => bool claimed) private s_hasClaimed; ... function claim(address account, uint256 amount, bytes32[] calldata merkleProof) external payable { + if (s_hasClaimed[account]) revert MerkleAirdrop__AlreadyClaimed(); if (msg.value != FEE) { revert MerkleAirdrop__InvalidFeeAmount(); } bytes32 leaf = keccak256(bytes.concat(keccak256(abi.encode(account, amount)))); if (!MerkleProof.verify(merkleProof, i_merkleRoot, leaf)) { revert MerkleAirdrop__InvalidProof(); } + s_hasClaimed[account] = true; emit Claimed(account, amount); i_airdropToken.safeTransfer(account, amount); } ``` Now, let's unit test the changes, ```javascript function testCannotClaimAirdropMoreThanOnceAnymore() public { vm.deal(collectorOne, airdrop.getFee() * 2); vm.prank(collectorOne); airdrop.claim{ value: airdrop.getFee() }(collectorOne, amountToCollect, proof); vm.prank(collectorOne); airdrop.claim{ value: airdrop.getFee() }(collectorOne, amountToCollect, proof); } ``` The test correctly fails, with the following logs, ```shell Failing tests: Encountered 1 failing test in test/MerkleAirdropTest.t.sol:MerkleAirdropTest [FAIL. Reason: MerkleAirdrop__AlreadyClaimed()] testCannotClaimAirdropMoreThanOnceAnymore() (gas: 96751) ```
The contest is live. Earn rewards by submitting a finding.
Submissions are being reviewed by our AI judge. Results will be available in a few minutes.
View all submissionsThe contest is complete and the rewards are being distributed.