{"id":1658,"date":"2009-04-06T08:15:24","date_gmt":"2009-04-06T08:15:24","guid":{"rendered":"https:\/\/www.darknet.org.uk\/?p=1658"},"modified":"2015-09-09T19:38:08","modified_gmt":"2015-09-09T11:38:08","slug":"how-to-scan-for-conficker-worm","status":"publish","type":"post","link":"https:\/\/www.darknet.org.uk\/2009\/04\/how-to-scan-for-conficker-worm\/","title":{"rendered":"How to Scan for Conficker Worm"},"content":{"rendered":"

A bit of an update to the conficker worm that is supposedly scheduled for new updates and instructions today wednesday 1st. April 2009 and that nobody except for the bad guys knows what those instructions would be. Fyodor has rolled out a new nmap beta release to the nmap scripting engine that enables it to check if a particular machine is possibly infected by the conficker worm.<\/p>\n

\nThanks to excellent research by Tillmann Werner and Felix Leder of The Honeynet Project<\/a> and implementation work by Ron Bowes, David Fifield, Brandon Enright, and Fyodor, we’ve rolled out a new Nmap release which can remotely scan for and detect infected machines. Nmap 4.85BETA5 is now available from the download<\/a> page, including official binaries for Windows and Mac OS X. To scan for Conficker, use a command such as:\n<\/p><\/blockquote>\n

nmap -PN -T4 -p139,445 -n -v --script=smb-check-vulns --script-args safe=1 IP<\/pre>\n