Intrusec's detailed analysis: This Trojan aims to be a distributed port scanner whose presence is very difficult to detect. It port scans random addresses across the IP address space, with a random source address also spoofed. By spoofing the source address, the Trojan is able to avoid easy detection, but it also means it can not receive the results of the TCP SYN that is sent. However, since the Trojan also sniffs the network it is on in promiscuous mode, it is likely, over time, to pick up scans from other installations of Trojans that randomly selected a source address that happened to be on its subnet. As the number of Trojans installed across the Internet grows, more spoofed packets will be sent out by each Trojan, and more of the spoofed source addresses will be captured by other Trojans.

Each time a reply to a Trojan is seen, indicating an open port has been found, it is written to a file and saved. Daily, the Trojan will then deliver the list of open ports it recorded while sniffing to a file and deliver that file to a predefined IP address.

In addition, a specially crafted packet can be sent to the subnet the Trojan is listening on which contains in its sequence number the IP address the Trojan should deliver the open port list to daily. However, in the current incarnations of this Trojan this functionality appears to be disabled.

Finally, the Trojan contains a feature whereby if it fails to connect to the IP address it is supposed to deliver its open ports list to, it will automatically attempt to remove itself from the system.

The Trojan we have identified has been a file named 'a' that resides in /tmp/.../a on the file system. Its packet collection activity monitors for any packet with a window size of 55808 and records all packets matching that window size. The packet capture is written to its current directory (/tmp/.../ typically) in a file named 'r'.

There is a default IP address of 12.108.65.76 that the Trojan attempts to make a standard connection (not spoofed) to on TCP port 22 and deliver the packet capture after it has been running for 24 hours, however this appears to have been randomly selected as it is not an active system on the Internet, and it is potentially dynamically modifiable by a packet that can be sent to the Trojan.

The Trojan appears to contain some functionality to change the IP address it delivers its packet captures to, but this functionality is not operational in the Trojan we have obtained. It appears the stubbed out code, if activated, would function as follows: If a packet is captured that contains a window size of 55808 and a TCP option window scale of 2, the Trojan modifies the IP address packet captures are delivered to based on the sequence number of that packet.

While a novel concept, this Trojan seems largely to have been written as a proof of concept relative to the ideas Lancope described as a '3rd generation Trojan.' Other than generating large amounts of network traffic, it contains no self-replicating or malicious behavior, and a few high-speed port scans from compromised host would be a far more effective and efficient means to map open ports on the Internet than this type of Trojan.

We have only observed the Trojan on Linux systems to date. However, the program itself is quite portable to other UNIX variants, so it is possible if not likely that it may also exist on other UNIX distributions. It is also possible that the 'original' Trojan is Windows-based.

The Trojan appears to be installed on a system either manually, or through an external exploit that is unrelated to the Trojan itself. There is no exploit code or means to install itself on a host built-in to the Trojan itself. It is easy to identify that a system on your network has been infected with this or a related Trojan due to its extremely noisy network activity it generates with TCP packets with a window size of 55808. However, other legitimate services may intentionally or incidentally also send packets with this same window size, so do not solely rely upon the presence of such a packet as guaranteeing the existence of such a Trojan. Security vendors who claim that identifying massive quantities of port scanning originating from their network as a unique feature of their software should be taken with a grain of salt. It is more difficult to identify the specific system on your network that has been infected with this Trojan due to its spoofing activities other than for its daily non-spoofed connection to remote port 22. Tools that can assist you in locating the actual physical source of these spoofed packets (through looking at MAC addresses and ARPs) may be quite useful.

Please visit and link to http://www.intrusec.com/55808.html to receive the latest information available regarding this Trojan.

Additional Links: http://www.eweek.com/article2/0,3959,1130759,00.asp
http://gcn.com/vol1_no1/daily-updates/22371-1.html
http://www.lancope.com/news/Virus_Alert_Trojan.htm