Flawed Windows Defender signature triggered false alarm

Microsoft's Windows Defender spyware detection software has mistakenly raised the Win32/PossibleHostsFileHijack alarm on some clean PCs. The error is caused by a flawed signature deployed via automatic update on Monday. Another signature update has now been issued to solve the problem, said Microsoft. Users are advised to ignore the warning and update the signature database of Windows […]

Microsoft's Windows Defender spyware detection software has mistakenly raised the Win32/PossibleHostsFileHijack alarm on some clean PCs. The error is caused by a flawed signature deployed via automatic update on Monday. Another signature update has now been issued to solve the problem, said Microsoft.

Users are advised to ignore the warning and update the signature database of Windows Defender via the Windows Update feature. Those who have put the alleged intruder into quarantine, or even deleted it, should use the Notepad text editor to at least create a minimal hosts file consisting of the following two lines:
127.0.0.1 localhost
::1 localhost

This file needs to be saved as C:\Windows\system32\drivers\etc\hosts (Windows XP and Vista) or C:\WINNT\system32\drivers\etc\hosts (Windows 2000) to ensure uninterrupted network traffic.

Source:→ h-online.com