According to PANews, a recent article by SlowMist highlights a security vulnerability in smart contract deployment that has garnered significant attention. The issue involves an attack method using CREATE and CREATE2 to deploy 'same address, different contract' scenarios. Attackers can initially deploy a secure contract to gain authorization, then self-destruct it and redeploy a malicious contract using the same deployment path. This tactic can lead to the execution of malicious logic through delegatecall, potentially resulting in the hijacking of DAO governance rights.
SlowMist advises developers to record and verify code hashes, exercise caution when using delegatecall, and be aware of the risks associated with contract self-destruction and address reuse. These measures are recommended to mitigate the potential threats posed by this vulnerability.