The contract allows a user to claim multiple times if they can increase their Snow token balance after claiming. There’s no proper mechanism preventing multiple claims.
The function claimSnowman() computes the Merkle leaf based on current token balance.
Since token balances can change, the Merkle proof becomes invalid unless the leaf matches the current balance.
However, a user who accumulates new tokens after claiming can produce new leaves and signatures.
The getClaimStatus function is not used in claimSnowman to determine if the user has already claimed or not.
A user can use the same signed message to call claimSnowman multiple times.
Contract logic violates airdrop intent.
HIGH
HIGH
Manual review
Enforce require(!s_hasClaimedSnowman[receiver], "Already claimed"); at function start.
Mark the hash as used to not allow replay attacks.
The claim function of the Snowman Airdrop contract doesn't check that a recipient has already claimed a Snowman. This poses no significant risk as is as farming period must have been long concluded before snapshot, creation of merkle script, and finally claiming.
The contest is live. Earn rewards by submitting a finding.
This is your time to appeal against judgements on your submissions.
Appeals are being carefully reviewed by our judges.