In early August (
specifically only on one day, Aug 2nd, 2016) and
only for a few hours, the download mirror which a third party website, FossHub, was hosting for Classic Shell version 4.3.0 got hacked by some hackers calling themselves Peggle Crew. They did not tamper with the Classic Shell files, instead they managed to replace the installer file with another fake installer containing a trojan that when launched, corrupts the MBR (Master Boot Record) of the PC. This renders the computer unbootable.
As soon as the hack was detected, the download link on the main site
http://www.classicshell.net was fixed to link to a clean installer file. Classic Shell became once again safe to download immediately after the hack was detected within a few hours and the fake installer replaced with a genuine one.
Those of who who pay attention to the UAC prompt in Windows should not have gotten infected because the authentic installer is digitally signed and shows a green UAC prompt along with the developer's name, whereas the fake one shows a bright yellow UAC prompt indicating a warning. The infection can only happen if you say Yes to the UAC prompt of the fake installer, not if you doubled click it but said No to the UAC prompt.Here is a FAQ for those of you whose PC got affected by malware when they accidentally downloaded and ran the hacked installer on August 2nd, 2016. Anyone else downloading the current installer after August 2 or now should rest assured that it is clean and free of malware. You can verify this by checking the digital signature of the installer's properties.
How do I know I have downloaded the correct file?There are few things to watch for:
- Check the file properties in Explorer – right-click -> Properties. Look for a tab named “Digital Signatures”. It should list “Ivaylo Beltchev” as the signer. The hacked file doesn’t even display the “Digital Signatures” tab.
- When you run the real installer it will not immediately ask you for admin permissions. Only after you finish selecting your settings you will be asked. The hacked file asks right away.
- The prompt for permissions will be blue for the real file and say "Verified publisher: Ivaylo Beltchev". The fake file will show a yellow prompt and say "Publisher: Unknown".
- The fake file will of course not install Classic Shell. It will just flicker once and exit. So if you managed to install Classic Shell 4.3.0, then you had the right file and you are safe
What do I do if I launched the fake file and got infected?If you haven’t rebooted yet, save your work and back up your important files. If things go very wrong you may have to reinstall Windows and will lose your files.
Also make sure you have a working Windows 10 disk before rebooting. You can make one using the instructions here:
https://www.microsoft.com/en-us/softwar ... /windows10To repair the MBR, follow the instructions here:
viewtopic.php?f=12&t=6440Also in video form:
https://www.youtube.com/watch?v=DD9CvHVU7B4There are also few forum threads with useful information:
viewtopic.php?f=12&t=6434viewtopic.php?f=12&t=6437Reddit thread about the hack and possible fixes:
https://www.reddit.com/r/pcmasterrace/c ... shell_readOnce again, we assure you that except for a few hours on August 2nd, 2016 when Classic Shell's installer was hacked, Classic Shell is completely safe to use again.