ESET Online Help

Search
Select the topic

Botnet feed

The Botnet feed shares all the data ESET has about the Botnet network. The feed consists of three types of feeds (botnet, cc, and target). Each feed contains different information.

ei.botnet

Below is a description of some attributes of the ei.botnet feed.

Detection—The name of the detection defined by ESET (Win32/TrojanDownloader.Wauchos.CX trojan).

Hashes—The hash of the detected file (SHA1, MD5, SHA256).

File_extension—The type of the malicious file (.exe, .sys, .dll, script, or unk).

Used by—The family name of the attacking botnet. This field has the same value as the target field in ei.target (Win32/Dorkbot.H worm).

Last alive—The timestamp of when ESET was last able to communicate with the server (2015-12-03 13:17:31).

URIobj type=C2—The link of the Command and Control (CnC) server. This value might also be a TOR link (http://t7yz3cihrrzalznq.onion/assets).

Config—The SHA-1 hash of the configuration file when downloaded (.ini, .bin).

URIobj type=target—The targeted link string botnet is attacking (*paypal.*/webscr?cmd=_login-submit*).

Files downloaded by the main file—These files may be downloaded by the main file. If so, the feed contains the following:

oDetection—The name of the detection defined by ESET.

oHashes (SHA1, MD5, or SHA256)

oType of file (.exe, .sys, .dll, script, or unk)

JSON

Below is a snippet of an ei.botnet feed in JSON format.

STIX 2.0

Below is a snippet of an ei.botnet feed in STIX 2.0 format.

 

The following types of STIX domain objects are available for the botnet feed:

Indicator 1—The main Indicator of Comprise (IoC), which is a malicious file that communicates with a CnC server. This object is always present in the feed

Observed data 1—Additional information about the malicious file.

Malware—A detection of a malicious botnet file.

Identity—The malware targets obtained from the configuration of the CnC. This object is optional.

Observed data 2—If a malicious file (IoC 1) creates or downloads additional files, the files will be connected to that file (IoC 1) via Sighting.

Indicator 2—The secondary IoC tied to IoC 1. This object refers to the link of the CnC server and the associated data. If the last communication with the CnC server through the given link was more than 48 hours ago, Indicator 2 turns to Observed data 3.

Observed data 3—This object shows all links that were pointing to the CnC server hosting the malware. If the links were active in the last 48 hours, they also have a relationship with Indicator 2.

Relationship

stix_relationships_botnet_feed