Some of the IPs will have an infection type, and these will only be for the HTTP bots or the Spam relays.
As we have grown in size, so have our data sets, requiring us to change our storage technology and methodology. We had to make certain changes to the data sets, which have then required certain output changes as well.
What does the C&C really mean?
The IP for the C&C could be a real command and control system that we or a partner is monitoring either directly or passively. It could also be one of the many sinkhole servers that we and our partners operate. If it is a sinkhole server, this means that your IP address reached out and communicated somehow with our server. We cannot issue commands, nor can we control your system from our sinkhole server, since it is a mostly-passive capture device. We only harvest the connection information and report it back out.
Why is the C&C blank or set to 0.0.0.0?
This can occur for several reasons. We may not have the C&C IP address, depending on the source of the data and the method of tracking. For example, you could have a drone IP labeled as Spam. Since we extracted only the last hop from a Spam message, we do not know the controlling source and cannot report on it.
In the instances where the capture point was our Sinkhole server, we are the C&C in this instance, and there is no reason to include our IPs.
If we have the data, we will always include it in the reports. We filter nothing from the data that we send, except to ensure that you receive only the data for your area of responsibility.
What types of tags are there for drones?
As of Monday, 1 November 2010, we have the following tags:
- data stealer
- Girlbot Trojan
- iframe exploit
- Kaiten Backdoor
- Mariposa – BlackEnergy Payload
- Trojan Jupebot/KNB
- Unclassified Trojan
- Unclassified Trojan – first detected 21/Apr/2009
- Unclassified Trojan, first detected 28/Sep/2010
- Unknown Trojan, first detected 14/12/2010
What does it really mean when something was tagged as “spam” for a drone?
When we collect Spam messages, the message headers can be almost completely falsified, except the last hop connection before it hits a Spam trap. These are the IPs that we are reporting. That IP somehow relayed or originated the message to the traps.
I found the IP you listed, but my logs show a few hours off. Is your time correct?
All of our logs are in UTC, but we only send out the first event for each IP. There could be dozens or hundreds in a day. Because of the quantity of events on a daily basis, it is not practical to send out each and every event seen on an IP.