Sharik is a Trojan which injects itself into legitimate processes and adds registry entries for an added level of persistence. The infection also sends information about the victim's PC to a remote server. The threat can also receive commands from a known CnC server to download further malicious files. The point of origin in this case is almost always a compromised website as discussed previously in a colleague's blog. At the time of research, I had not pinpointed the initial infection for this threat. The end result of the Trojan infection appears to be identical to past iterations of this threat.
The following are known drop points for this threat:
Many of these files have already been talked about in other blogs, especially for the the corp-firewall.com and main-firewalls.com drop sites. What helped me tie all of these infectious files together was their distinct phone home traffic. Every instance mentioned above displays the same phone home behavior albeit to different locations. Below is the phone home activity displayed by all of the above trojans:
The transaction I'll be focusing on here is the very last bullet point. After the infection occurs on the victim's PC, it creates an autostarter that hooks into explorer.exe to add a level of resilience to hinder standard AV removal methods. At the time of research, the MD5 (fa33c07e27e4a1e9f1ecdf1172f12562) was being detected by 8/46 AV engines on Virustotal.
The main function of Sharik is to leave the victim open to further infection. To do this, the infection will set up a backdoor and communicate with it's CnC. The attacker can choose to attack the victim further later on. The standard communication between the victim and attacker appears to take place on a non-standard port 35618. Given the high volume of variants of this threat, it is advised to close this port or at least monitor it for suspicious activity.
It should also be noted that many of the above mentioned download locations are involved in other threats. For example, main-firewalls[.]com is very closely related to Nymaim ransomware. Another example is the md5, 771cc060cf15fc29290a0109c1cf7669, which is a Fareit variant. So what is a ransomware application and a FTP stealing trojan doing displaying the same phone home activity as a resilient backdoor Trojan? This activity hasn't been tied to on specific group at the time of research, but administrators and users should be on notice. Where there is smoke there will inevitably be fire. So if you suspect you or the users you are responsible for are seeing HTTP traffic like the above mentioned, then it definitely merits further investigation. Mind your clicks.