Rewterz Threat Alert – Cobalt Strike Malware- Active IOCs

Severity

High

Analysis Summary

Cobalt Strike first appeared in 2012 in response to alleged flaws in the Metasploit Framework, an existing red team (penetration testing) tool. Cobalt Strike 3.0 was released in 2015 as a stand-alone opponent emulation platform. However, researchers began observing threat actors using Cobalt Strike by 2016. Cobalt Strike’s use in hostile activities was previously connected with massive cybercriminal operations like TA3546 and APT40. Two-thirds of detected Cobalt campaigns from 2016 to 2018 were attributable to well-resourced cybercrime organizations or APT groups, according to researchers.

Cobalt Strike lets the attacker install a ‘Beacon’ agent on the target PC which provides the attacker with a plethora of capabilities, including command execution, file transfer, keylogging, mimikatz, port scanning, and privilege escalation. Cobalt Strike includes a toolkit called Artifact Kit that is used to create shellcode loaders. 

Researchers discovered a new wave of phishing attacks in September that infect job seekers in the United States and New Zealand with Cobalt Strike beacons. The malware campaign used the lure of a job in order to infect victims with leaked versions of Cobalt Strike beacons.

Researchers discovered a new wave of phishing attacks in September that infect job seekers in the United States and New Zealand with Cobalt Strike beacons. The malware campaign used the lure of a job in order to infect victims with leaked versions of Cobalt Strike beacons. It was observed that Cobalt Strike is not the only piece of malware used in the attacks. In certain situations, individuals were instead infected with a different type of information-stealing malware known as RedLine or an Amadey botnet executor.

Impact

• Data Exfiltration
• Information Theft

Indicators of Compromise

MD5

• f372afce288f142c6c5c06e8c7b2e19c
• 8b37ecb7799a193716ed6742da9569a7
• 86b0ef24b4da699168117e89fe8fef00
• 71a9066a265eed33ea52f348e220adcb

SHA-256

• 25177f86963cd89171a6f06bcd0559806f7c1fa1cff3a52eee89ad38c024b819
• a0410b34f9a1161434b2df05470e2bc5d917ad44e419fe9d6a5008e3e3898b47
• 9a9dc1b30c9fd8d6c9ce511474054b1cb7f6d6f7c2424da06503601f2737f4eb
• dec4c226a5745c4434fae3ab6cd53fa70831399f7ffbaa952763d427d6c5bea9

SHA-1

• 67bc7f825d6bf1a131e88b988f6c1a29c81a043a
• 7d165f1189462df1ca4d97f0001553d7b2292d6e
• 0e3948bcb435d59b2085792ddb02e3d130c9b175
• 1d11047e4fbfd38bad9aa71a0f4ce183ac7c6e9d

Remediation

• Block all threat indicators at your respective controls.
• Search for Indicator of compromise (IOCs) in your environment utilizing your respective security controls
• Emails from unknown senders should always be treated with caution.
• Never open links or attachments from unknown senders.
• Ensure that general security policies are employed including: implementing strong passwords, correct configurations, and proper administration security policies.
• Limit access to administrative accounts and portals to only relevant personnel and make sure they are not publicly accessible.
• Patch and upgrade any platforms and software timely and make it into a standard security policy. Prioritize patching known exploited vulnerabilities and zero-days.