Inside the Kronos malware – part 2

In the previous part of the Kronos analysis, we took a look at the installation process of Kronos and explained the technical details of the tricks that Kronos uses in order to remain more stealthy. Now we will move on to look at the malicious actions that Kronos can perform.
Analyzed samples
ede01f7431543c1fef546f8e1d693a85 – downloader (a .doc with a malicious macro)
2a550956263a22991c34f076f3160b49 – main bot (packed)

Special thanks to @shotgunner101 and @chrisdoman for sharing the samples.
Configuration and targets
Kronos is known as a banking Trojan. For the purpose of enabling and configuring this feature, the bot may download from its CnC additional configuration file. After being fetched, it is stored in the installation folder in encrypted form. (It is worth to notice that when the config is sent over the network it is encrypted using AES CBC mode – but when it is stored on the disk, AES in ECB mode is used.)
Below you can see an example of the installation folder of Kronos, created in %APPDATA%/Microsoft. The folder name is further used as a BotId. Both stored files, the executable and the configuration, has the same name that differs only by the extension:

Here you can see the captured configuration file in a decrypted form:

The format of the configuration follows the standard defined by the famous Zeus malware.
The config specifies the external script that is going to be injected in the targeted website, as well as the place of the injection. Below you can see a fragment of the configuration for a sample target – Wells Fargo Bank:

In the given example, the injected script is figrabber.js
It is hosted on the server of the attacker:

The current configuration targets several banks, but also steals credentials for popular services like Google, Twitter, and Facebook.
Indeed, if we open the websites that are targeted by the malware we can see that the injects has been performed. The fragments of code that were defined in the config are implanted in the source of a legitimate website. Some examples included below:


The injected scripts are responsible for opening additional pop-up that is trying to phish the user and steal his/her personal data:

Wells Fargo:

More cases, and their comparison with a normal site behavior before the infection, demonstrated on the video:

The form is customized to fit the theme of each page. However, its content is the same for each target. Overall, the attack is not very sophisticated and it will probably look suspicious to the more advanced users. It’s based purely on social engineering – trying to convince a user to input all personal data that are necessary for banking operations:

Apart from infecting browsers and stealing the data, Kronos also has a downloader feature. During our tests, it downloaded a new executable and saved it in the %TEMP%. Payloads are stored in the additional directory with the same name as the main installation directory:

Downloaded payload:
6f7f79dd2a2bf58ba08d03c64ead5ced – nCBngA.exe
The payload is downloaded from Kronos CnC:

…in unencrypted form:

In the analyzed case, downloaded payload was just an update of the Kronos bot. However, the same feature may also be used for fetching and deploying other malware families.
Command and Controll (CnC) server
In the analyzed case, Kronos used Fast-Flux technique for it’s CnC. The domain was resolved to a different IP each time. For example, the domain was resolved to an IP address randomly picked from the pool given below:

Watching the communication with the CnC, we observed queries to the site connect.php, with an optional parameter a:
connect.php – initial beacon
connect.php?a=0 – sending data to the CnC
connect.php?a=1 – downloading the configuration form the Cnc

CnC panel
Thanks to the code of the CnC panel that leaked online, we can have more insights on all the functionalities and their implementation. Like most of the malware panels, the Kronos panel is written in PHP and uses MySQL database. Overview of the files:

It turns out, that in total the bot has three commands:
a=0 – sends the grabbed page content
a=1 – fetch the configuration file
a=2 – send the logged windows
Below we can see the relevant fragments of the panel’s code (implemented inside connect.php), responsible for parsing and storing the data uploaded by the respective commands.
Command #0 (a=0):
Command #2 (a=2):
The configuration that is sent to the bot is prepared by the following code:
Command #1 (a=1):

We can also see very clearly how the config is encrypted – using AES in CBC mode, where the key is first 16 bytes of md5 of the BotId (it confirms what researchers form Lexsi lab found by reverse engineering).

However, AES is not the only cryptographic algorithm that is utilized by Kronos. Other commands use BlowFish in ECB mode:
Command #0 (a=0):

Command #2 (a=2):

In all cases, there is a variable called UniqueId that is used as a key. The UniqueId is nothing more but the BotId, that is sent in every POST request in XOR encoded form.

You can find the corresponding Python scripts for decoding the appropriate requests and responses here:
Kronos comes also with option of adding some plugins, extending the core functionality:

As we may conclude, the plugins are capable of extending Kronos with some espionage capabilities, such as VNC (for viewing the desktop) and logging typed keystrokes.
Decrypting the communication
With the help of prepared scripts (available here), we can decrypt the important elements of the communication between the Kronos bot and the CnC server. Let’s assume that we have a PCAP file with a captured traffic.
The BotId
We need to start from getting the Kronos BotId, because as we know it will be used to derive the encryption keys. We will find it in the requests sent by the bot to its CnC (74 bytes long):

After dumping the request, we can use the following script to decode it:
./ –infile dump1.bin

As the output we will get the decoded beacon, consisting of:
Hash of the configuration file (if no configuration file was present at the moment, this part will be filled with “X” characters)
The BotId

So, in the demonstrated case the BotId is {117BB161-6479-4624-858B-4D2CE81593A2}.
The configuration
Having the BotId, we can move to decrypt the configuration. It arrives in the response to the a=1 request:
Example of the request followed by the encrypted response from the CnC:

After dumping the response, we can use another script to decode it, giving the BotId as a parameter:
./ –datafile dump2.bin –botid {117BB161-6479-4624-858B-4D2CE81593A2}

As a result, we will get the configuration file. Example of the decoded config:
The sent reports
Sometimes we can find the Kronos bot reporting to the CnC in requests a=0 or a=2:

Example of the encrypted request:

Finding out what was exactly the data stolen by Kronos is not difficult if we dump the data and use the dedicated script:
./ –datafile dump3.bin –botid {117BB161-6479-4624-858B-4D2CE81593A2}

Example of the decoded report:
In terms of code quality, Kronos is written in a decent way, however it’s features are nothing novel. Although the bot got good reviews on underground forums, in terms of popularity it was always legging behind. Probably it’s relatively high price was the important factor deciding why it lost with the competitors.
See also:
Inside the Kronos malware – part 1

This was a guest post written by Hasherezade, an independent researcher and programmer with a strong interest in InfoSec. She loves going in details about malware and sharing threat information with the community. Check her out on Twitter @hasherezade and her personal blog:
The post Inside the Kronos malware – part 2 appeared first on Malwarebytes Labs.
Click here for best antivirus and antispyware software

Powered by WPeMatico

This entry was posted in Antivirus. Bookmark the permalink.