Really looking for remote detection of infested machines so I could take immediate action. Hmmm, maybe that is exactly what the VX writers/users would be looking for?
Main Topics
Browse All Topicslooking for a subnet scanner
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Best collection of free vulnerability scanners out there is Back-Track3
http://www.remote-exploit.
Check out their list of tools:
http://wiki.remote-exploit
http://wiki.remote-exploit
Microsoft also has a baseline analyzer to ensure all your PCs on the network meet a minimum requirement
http://technet.microsoft.c
A network scanner would allow you to check for machines vulnerable to MS08-067.
Nmap 4.85BETA1 for instance has a script which will check for this vulnerability - it would be executed thus:
nmap -sS -PN -p139,445 --script smb-check-vulns 10.0.0.0/8
it can be downloaded from http://nmap.org/dist/?C=M;
The problem with this method is twofold:
1) The conficker/downadup/kido malware may infect machines that aren't vulnerable to MS08-067, see http://www.f-secure.com/v-
and these machines couldn't be found with a network scanner.
2) conficker effectively patches the MS08-067 vulnerability (in memory) and listens for attempts to exploit it to identify other machines that it would want to communicate with https://forums.symantec.co
Therefore, a box vulnerable to ms08-067 may not actually be infected and those that are will not respond to attempts to exploit ms08-067.
One possibility would be to check your firewall logs for access to domains to which the infected machines are known to attempt access:
http://www.google.co.uk/se
the current list is downadup_domain_blocklist_
Another might be to run a script which contacts each machine and tries to execute a dns lookup from that machine for one of the many security related domain names which the worm blocks.
If you have an enterprise anti-virus solution then scan every machine overnight.
I just wanted to update this question with regard to using Nmap to detect machines compromised with conficker.
Since my previous comment on this topic, Nmap 4.85BETA5 has been released and the smb-check-vulns script has been updated with a test which specifically detects a Conficker modified server service (i.e. a host compromised by conficker).
Nmap can be obtained at http://nmap.org/download.h
The command to use, either on the command line or from within Zenmap, is as follows:
nmap -PN -p139,445 -n -v --script smb-check-vulns --script-args safe=1 <target_IPs>
where target_IPs is a single hostname, IP address or range of IP adresses.
The result for a clean machine might look like this:
Host script results:
| smb-check-vulns:
| MS08-067: NOT RUN
| Conficker: Likely CLEAN
|_ regsvc DoS: NOT RUN (add --script-args=unsafe=1 to run)
A compromised machine:
Host script results:
| smb-check-vulns:
| MS08-067: NOT RUN
| Conficker: Likely INFECTED
|_ regsvc DoS: NOT RUN (add --script-args=unsafe=1 to run)
The "--script-args safe=1" part of the command prevents the MS08-67 check from being performed which is why you see "NOT RUN" next to it's entry in the Host script results. This check has a high chance of crashing vulnerable machines and so executing that test is not recommended.
The interesting line in the output is the Conficker one. Happy hunting!
Read more at:
http://jahboite.co.uk/b
or via google:
http://www.google.c
As an update Todays topics on full-disclosure include a conficker scanner for the network.
https://www-secure.symante
Business Accounts
Answer for Membership
by: page1985Posted on 2009-01-26 at 12:59:59ID: 23470894
Try SoftPerfect Network Scanner (free).
http://www.softperf ect.com/pr oducts/net workscanne r/