2

Losses from create2 wallets that look similar to recently active wallets has surpassed $60m: https://gbhackers.com/create2-bypass-wallet-security-alerts/

Even today I made a transaction, and noticed that create2 contract was deployed which looks very similar to my own wallet. So, clearly the create2 opcode is very useful in this attack pattern as you can cycle through a large number of potential wallets until you find one that looks similar to your target.

Instead of simply getting rid of create2 - what if create2 always returns the same wallet address until it is claimed? This may have to be enforced across all transactions the entire block as simply a recursive call may fool a check that is only scoped to the caller function.

Is this a reasonable patch? or is there a better way of fixing this vulnerably?

Improve this question
2
  • Not sure what you mean by "claimed". You can also try posting to ethereum-magicians.org to get feedback, and possibly assistance or even co-authors for an EIP.
    – eth ♦
    Nov 18 at 1:32
  • @eth according to the blockchain explorer we have broken 100k affected wallets and over $60m stolen. I posted to thereum-magicians.org and as far as i can tell they are trolling me.
    – rook
    yesterday

1 Answer 1

Reset to default
1

Even without create2, people could still do address poisoning attacks...it would just be a little harder to generate the addresses but still not hard enough to make a difference.

Improve this answer
1
  • Correct. The shortcut is still present. Forcing the calculation to be on-chain by requiring the block_hash to be apart of the calculation would prevent pre-computation.
    – rook
    yesterday

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.