The randomness generator that searchForEgg provides is not random at all, all the compotents are visible on chain(block.timestamp,block.prevranda and eggCounter) and the keccak256 is not a safe way to generate randomness
An attacker can easily predict when he is going to be the winner by simply using keccak256 outside of the contract until he gets result < eggFindThreshold.
Contract promises randomness and it doesn't provide true randomenss, this goes against the contract's main funcionality
Manual review
Use chainlink vrf randomness generator
Insecure methods to generate pseudo-random numbers
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.