Linux.Wifatch's primary mode of infection is by logging into devices using weak or default telnet credentials.67 Once infected, Linux.Wifatch removes other malware and disables telnet access, replacing it with the message "Telnet has been closed to avoid further infection of this device. Please disable telnet, change telnet passwords, and/or update the firmware."8
Ballano, Mario (1 Oct 2015). "Is there an Internet-of-Things vigilante out there?". Symantec. Retrieved 14 November 2016. https://community.broadcom.com/symantecenterprise/communities/community-home/librarydocuments/viewdocument?DocumentKey=ef23b297-5cc6-4c4a-b2e7-ff41635965fe&CommunityKey=1ecf5f55-9545-44d6-b0f4-4e4a7f5f5e68&tab=librarydocuments ↩
Das, Samburaj (October 2, 2015). "Linux.Wifatch: Vigilante Hacker Infects Routers with Malware to Fight Bad Malware". hacked.com. Retrieved 14 November 2016. https://hacked.com/linux-wifatch-vigilante-hacker-infects-routers-malware-fight-bad-malware/ ↩
Kovacs, Eduard (October 7, 2015). "Developers of Mysterious Wifatch Malware Come Forward". securityweek.com. Retrieved 15 November 2016. https://www.securityweek.com/developers-mysterious-wifatch-malware-come-forward ↩
"linux.wifatch". The White Team. October 5, 2015. Retrieved 15 November 2016. https://gitlab.com/rav7teif/linux.wifatch ↩
Cimpanu, Catalin (Oct 7, 2015). "Creators of the Benevolent Linux.Wifatch Malware Reveal Themselves". Softpedia. Retrieved 14 November 2016. http://news.softpedia.com/news/creators-of-the-benevolent-linux-wifatch-malware-reveal-themselves-493938.shtml ↩