Greetings again random internet-surfing technology enthusiasts,
Today, I’d like to tackle a puzzling issue that many techs encounter with regard to disinfecting Chrome and problematic extensions that manifest within it. Of course, anyone with any technical expertise is aware of the fact that browser extensions are currently one of the hottest attack vectors for unsuspecting users’ machines, but removing and keeping such extensions from reloading is another matter entirely. Some of examples of these include:
- AdBlocker (not the legitimate and excellent AdBlock)
- Vosteran Search
- …and many, many others
Most techs use some degree of automatic scanning and removal tools, and that’s fine, provided they don’t rely on them exclusively (as it doesn’t work… something I’ve covered countless times in the past). However, even those who dabble in manual or assisted-manual disinfection procedures have probably found that Chrome is one of the most problematic items to permanently clean on a user’s PC. This is ironic because Chrome also happens to be the browser I recommend to my clients for safety and speed currently (and it has been for quite some time). Does that mean that we should move on to a different browser choice instead?
Fortunately, nope. There is indeed a pretty universal solution to this problem, and today I’ll reveal it to you. For purposes of illustration, we’ll choose the third example extension I listed above for today’s explanation (WebProtector).
Each Chrome extension is affiliated with a unique identifier to help users locate and install the extension from the Chrome Web Store. WebProtector’s, for instance, happens to be kfecnpmgnlnbmipaogfhoacoioifjgko. The Web Store does indeed host this extension in spite of its fraudulence; and Google, for all their great work in producing a relatively safe browser in Chrome, have done a pretty terrible job of keeping the store cleaned of such filth. The problem with WebProtector (and many of these other extensions) is that even after they’re cleaned from the computer and all other malware is removed, the users may find that they reload themselves regardless later on with little or no warning. You might think that completely uninstalling Chrome, removing all directories on the system relating to Chrome, and cleaning/resetting the user’s Chrome Data profile (as I described in another post recently) should logically solve the problem. But it doesn’t. The extension yet again reloads itself upon future reinstallations.
The answer to the puzzle is Policies in the Windows registry. Chrome stores its policies in the following two keys:
Under these keys you will find a subkey called Extensions; it is from this key that Chrome is instructed to load the infected extensions upon each reinstallation and subsequently thereafter at regular intervals. Simply deleting these keys (provided the user is not reliant on any policies in Chrome for administrative purposes) will prevent the behavior. At an elevated command prompt, try typing these commands:
REG DELETE “HKCU\Software\Policies\Google” /f
REG DELETE “HKLM\Software\Policies\Google” /f
Specifically, the autoinstall keys that are likely being used are:
However I like to remove the entire Policies key on most machines as other suspect keys are also often used, such as whitelisting of bad extensions and even blacklisting of good ones.
It also goes without saying that the extension itself must first be removed for this to work. That includes killing the keys relating to it in the following locations:
As well as the associated files within the user’s Chrome User Data directory. If you’re really just looking to clean sweep the entire program, you can follow my previous instructions to backup the user’s Bookmarks and other personal items and then simply wipe out all related keys and files after uninstalling Chrome. This will finally solve the problem!