Snowman Merkle Airdrop

AI First Flight #10
Beginner FriendlyFoundrySolidityNFT
EXP
View results
Submission Details
Severity: low
Valid

Missing claim status check allows repeated claims after re-buying Snow

Title: Missing claim status check allows repeated claims after re-buying Snow
Impact: Low. Claimants can re-claim by re-buying tokens, though each claim costs the token price.
Likelihood: Medium. Requires repeated Snow purchases between claim cycles.
Reference Files: repos/src/SnowmanAirdrop.sol:47,69-99

Description

The claimSnowman() function sets s_hasClaimedSnowman[receiver] = true after a claim but never reads this mapping as a guard. The anti-double-claim check relies solely on the Snow balance becoming zero after tokens are transferred away. If a claimant acquires new Snow tokens (via buySnow or earnSnow), their balance becomes non-zero, the Merkle proof still matches their (address, 1) leaf, and the claim succeeds again — since s_hasClaimedSnowman is never checked.

if (i_snow.balanceOf(receiver) == 0) { revert SA__ZeroAmount(); } // only guard
// ... claim processing ...
s_hasClaimedSnowman[receiver] = true; // set but NEVER READ as guard

Each claim cycle burns the Snow tokens and costs the buy fee, limiting profitability unless NFT value exceeds the fee.

Risk

Impact: Low. The attacker must purchase Snow tokens for each claim cycle. If the NFT value exceeds the token fee, repeated claims are profitable, but the cost acts as a natural rate-limiter.
Likelihood: Medium. Requires repeated Snow purchases with ETH/WETH. Each cycle is a separate transaction.
With a buy fee of 0.03 ETH and NFT floor of 0.05 ETH, each claim nets 0.02 ETH profit — repeatable but gas costs eat into margin.

Proof of Concept

function testRepeatClaimViaRebuying() public {
vm.prank(alice); snow.approve(address(airdrop), 1);
(uint8 v, bytes32 r, bytes32 s) = vm.sign(alKey, airdrop.getMessageHash(alice));
airdrop.claimSnowman(alice, AL_PROOF, v, r, s);
assertEq(nft.balanceOf(alice), 1);
// Re-buy and claim again
vm.deal(alice, FEE);
vm.prank(alice); snow.buySnow{value: FEE}(1);
(v, r, s) = vm.sign(alKey, airdrop.getMessageHash(alice));
airdrop.claimSnowman(alice, AL_PROOF, v, r, s);
assertEq(nft.balanceOf(alice), 2);
}

Recommended Mitigation

if (s_hasClaimedSnowman[receiver]) revert("Already claimed");

Add the mapping check at the top of claimSnowman() to enforce one-time claims.

Updates

Lead Judging Commences

ai-first-flight-judge Lead Judge about 23 hours ago
Submission Judgement Published
Validated
Assigned finding tags:

[L-01] Missing Claim Status Check Allows Multiple Claims in SnowmanAirdrop.sol::claimSnowman

# Root + Impact   **Root:** The [`claimSnowman`](https://github.com/CodeHawks-Contests/2025-06-snowman-merkle-airdrop/blob/b63f391444e69240f176a14a577c78cb85e4cf71/src/SnowmanAirdrop.sol#L44) function updates `s_hasClaimedSnowman[receiver] = true` but never checks if the user has already claimed before processing the claim, allowing users to claim multiple times if they acquire more Snow tokens. **Impact:** Users can bypass the intended one-time airdrop limit by claiming, acquiring more Snow tokens, and claiming again, breaking the airdrop distribution model and allowing unlimited NFT minting for eligible users. ## Description * **Normal Behavior:** Airdrop mechanisms should enforce one claim per eligible user to ensure fair distribution and prevent abuse of the reward system. * **Specific Issue:** The function sets the claim status to true after processing but never validates if `s_hasClaimedSnowman[receiver]` is already true at the beginning, allowing users to claim multiple times as long as they have Snow tokens and valid proofs. ## Risk **Likelihood**: Medium * Users need to acquire additional Snow tokens between claims, which requires time and effort * Users must maintain their merkle proof validity across multiple claims * Attack requires understanding of the missing validation check **Impact**: High * **Airdrop Abuse**: Users can claim far more NFTs than intended by the distribution mechanism * **Unfair Distribution**: Some users receive multiple rewards while others may receive none * **Economic Manipulation**: Breaks the intended scarcity and distribution model of the NFT collection ## Proof of Concept Add the following test to TestSnowMan.t.sol  ```Solidity function testMultipleClaimsAllowed() public { // Alice claims her first NFT vm.prank(alice); snow.approve(address(airdrop), 1); bytes32 aliceDigest = airdrop.getMessageHash(alice); (uint8 v, bytes32 r, bytes32 s) = vm.sign(alKey, aliceDigest); vm.prank(alice); airdrop.claimSnowman(alice, AL_PROOF, v, r, s); assert(nft.balanceOf(alice) == 1); assert(airdrop.getClaimStatus(alice) == true); // Alice acquires more Snow tokens (wait for timer and earn again) vm.warp(block.timestamp + 1 weeks); vm.prank(alice); snow.earnSnow(); // Alice can claim AGAIN with new Snow tokens! vm.prank(alice); snow.approve(address(airdrop), 1); bytes32 aliceDigest2 = airdrop.getMessageHash(alice); (uint8 v2, bytes32 r2, bytes32 s2) = vm.sign(alKey, aliceDigest2); vm.prank(alice); airdrop.claimSnowman(alice, AL_PROOF, v2, r2, s2); // Second claim succeeds! assert(nft.balanceOf(alice) == 2); // Alice now has 2 NFTs } ``` ## Recommended Mitigation **Add a claim status check at the beginning of the function** to prevent users from claiming multiple times. ```diff // Add new error + error SA__AlreadyClaimed(); function claimSnowman(address receiver, bytes32[] calldata merkleProof, uint8 v, bytes32 r, bytes32 s) external nonReentrant { + if (s_hasClaimedSnowman[receiver]) { + revert SA__AlreadyClaimed(); + } + if (receiver == address(0)) { revert SA__ZeroAddress(); } // Rest of function logic... s_hasClaimedSnowman[receiver] = true; } ```

Support

FAQs

Can't find an answer? Chat with us on Discord, Twitter or Linkedin.

Give us feedback!