Rewterz Threat Alert – Qakbot Malware: Rise In Attacks Evolve New Threat Techniques – Active IOCs

Severity

High

Analysis Summary

QBot, often known as QakBot, is modular information malware. It has been operational since 2007. This banking Trojan, QakBot steals financial data from infected systems, and a loader using C2 servers for payload targeting and download. Qakbot has worm capabilities, which let it propagate to other computers on the same network, as well as rootkit capabilities, which allow it to mask its existence and build persistence on infected computers. A malware attachment to a phishing email is commonly used in QakBot attacks. This particular campaign includes an xls file that contains macros. These macros run a script that fetches the Qakbot payload from a list of URLs. To get the victim to activate macros, the attackers employ a common trick, like when the target downloads the file, it is asked to allow changes and then content before viewing the document.

Recently, it is observed that attackers are employing a number of strategies to avoid detection, using Excel (XLM) 4.0 and ZIP file extensions. They are utilizing sophisticated strategies to evade automated detection and increase the likelihood that their attack will succeed, such as obfuscating code, using numerous URLs to deliver the payload and others. Threat actors are disguising attachments intended to spread malware using a variety of different common file names with typical keywords for finance and business operations. 

Impact

• Unauthorized Access
• Financial Theft
• Information Theft

Indicators of Compromise

IP

• 1[.]161[.]123[.]53
• 101[.]108[.]199[.]194
• 102[.]182[.]232[.]3
• 103[.]116[.]178[.]85
• 104[.]34[.]212[.]7
• 106[.]51[.]48[.]170
• 108[.]60[.]213[.]141
• 109[.]12[.]111[.]14
• 109[.]178[.]178[.]110
• 111[.]125[.]245[.]116
• 120[.]150[.]218[.]241
• 120[.]61[.]2[.]215
• 121[.]7[.]223[.]45
• 124[.]40[.]244[.]115

MD5

• 58f76fa1c0147d4142bfe543585b583f
• d7c3ed4d29199f388ce93e567a3d45f9
• 3243d439f8b0b4a58478dfa34c3c42c7
• 396c770e50cbad0d9779969361754d69
• c2b1d2e90d4c468685084a65ffee600e

SHA-256

• a032873b089205f97205524288909332c351100a848cd980f8c8cfed477d5bce
• d1559cb7df55e615b09125a5f56313c4c19ebc199cf948a3c9188535f9a5d1a7
• 8f60b0812923384cbc42e6560b4b9b682c2337df00e5b2aa64ff6eb9c9264696
• fc53f7eaaf72bca10651325f07885075c406b0064dd3078992d2d80a28ed371a
• 7f27858346e2c342c172730720368569df2ca5f7efe9228ac0040ed3a750debc

SHA-1

• 251bff766426152a208e713c88633cda47fcf49f
• c94a5613cab7ac5b56e255ab4cfa67a176ab07f0
• ad9f1def7e18adb06a7c1d54915e147202903a6a
• 61072b7e86c1dbfda41255d6902a4aa74b92876d
• 93b34efadbb1c93f4cc1667c2cb5ed92cb8dba63

Remediation

• Block the threat indicators at their respective controls.
• Search for IOCs in your environment.