I'm not even sure if this is why the newly synchronizing wallet gets stuck, but that's the attack mentioned in the whitepaper, however if this is the case I think it should be straight forward to fix by making the wallet downloads the other available version of the blockchain when it can't synchronize with the fake one.