Last Updated: 2009-03-16 19:55:42 UTC
by Tony Carothers (Version: 1)
Martin I. wrote in a bit ago in response to the diaries from Saturday and Sunday. Martin has noticed an increase in UDP traffic from various sources on the aforementioned ports. We are really wanting to see some full packet captures, so if anybody has the means and opportunity, we'd greatly appreciate it.
Last Updated: 2009-03-16 19:49:12 UTC
by Johannes Ullrich (Version: 1)
Thanks to Irwin for alerting us about a new version of rogue DHCP server malware he found in his network. The malware appears to be similar to Trojan.Flush.M which was found last December. Like back then, after infecting its target, the malware installs a rogue DHCP server. The main goal of the DHCP server is to spread a bad DNS server IP address.
Irwin did a good job comparing the two versions. Here is his summary of the differences:
- The new version sets the DHCP lease time to 1 hour.
- it sets the MAC destination to thebroadcast address, rather then the MAC address of the DHCP client
- it does not specify a DNS Domain Name.
- the options field does not contain an END option followed by PAD options.
- Unlike Trojan.Flush.M, the BootP Broadcast Bit is set.
The malicious DNS server is 220.127.116.11 and 18.104.22.168.
monitor connections to DNS servers other then the approved one pushed out by your DHCP server. This should help you spot this kind of malware. Yes, you can block the two IP addresses listed above, but it will likely do little good.
Johannes B. Ullrich, Ph.D.
SANS Technology Institute