@Alynx I re-installed my system after XZ incident. After that, I have never faced this issue again. Re-installing the system was mentioned as a workaround in the upstream thread too. However, there's no other fix exist, and it's currently unknown how this issue happens.