StrikeShark Campaign Uses SharkLoader to Deploy Cobalt Strike

· Original article ↗

Summary

Researchers detail StrikeShark, a campaign using SharkLoader to deploy Cobalt Strike through exploited public-facing applications and malicious droppers. Analysis describes its in-memory loading, evasion, persistence and credential-theft activity; attribution remains a低

Key points

  • Researchers identified SharkLoader, a previously undocumented loader that deploys Cobalt Strike Beacon, in activity affecting government, diplomatic and software development organizations across multiple countries.
  • Observed initial-access methods included exploiting internet-facing applications such as Exchange, Openfire and GeoServer, as well as custom droppers disguised as installers or PDF documents.
  • SharkLoader uses DLL sideloading and manipulates Windows loader state to bypass the loader lock; encrypted modules are decrypted and reflectively loaded in memory.
  • The malware installs API hooks, including hooks that suppress ETW logging and alter memory protections around Cobalt Strike Beacon activity, which researchers say may help evade memory scanning.
  • Post-compromise activity included persistence through scheduled tasks or a registry Run key, system and Active Directory reconnaissance, and attempts to dump credentials from LSASS and the NTDS database.
  • Researchers found no direct code or infrastructure links to a known actor. A Chinese-speaking threat-actor assessment is preliminary and low confidence; no clear evidence of data exfiltration had been observed.

Article Details

Attack Vectors
  • Exploitation of internet-facing applications, including Microsoft Exchange (CVE-2021-26855 and CVE-2021-27076), Openfire (CVE-2023-32315), and GeoServer (CVE-2024-36401).
  • Custom droppers disguised as legitimate software installers or applications, and in some cases as PDF documents, delivered SharkLoader components.
  • DLL sideloading through legitimate executables, including SystemSettings.exe, to load malicious SharkLoader DLLs.
  • Webshells were used for post-exploitation activity; the researchers suspect components were uploaded through a webshell.
  • Persistence through scheduled tasks and a Windows registry Run key.
Defensive Notes
  • The researchers recommend heightened vigilance and continued monitoring of this activity.

Indicators of compromise

TypeIndicatorContext
DOMAINcomms-record[.]comms-record[.]topListed by the article as C2 or related campaign infrastructure.
DOMAINconnect-microsoft[.]comListed by the article as C2 or related campaign infrastructure.
DOMAINms-record[.]comListed among indicators associated with the StrikeShark campaign.
DOMAINms-record[.]topListed among indicators associated with the StrikeShark campaign.
DOMAINms-tray[.]topListed by the article as C2 or related campaign infrastructure.
MD51f65544978b8ea0e745e573b8ee9684bHash of a SharkLoader dropper sample found on a machine in Lebanon.
MD524fcebdeecba65004fdb0923763d74fdHash of a malicious dropper used to deploy SharkLoader components in a campaign targeting a government entity in Taiwan.
MD59c872a0d5d5a38950e8b9ac9b488be3fHash of a SharkLoader DLL sample.
MD59cbd560f820c95d7c38342cd558cb5c6Hash of an encrypted SharkLoader component.
MD5a514d1bb62d7916475946fe7c07ac0aaHash of an encrypted SharkLoader component.
MD5aa3086be652c8b20b0b29b2730d57119Hash of a SharkLoader DLL sample.
MD5b3352b42432dedc4a519f011dc8b5d5aDropper sample hash listed among the campaign indicators.
MD5c559cc68986933200fd5d9e4388e2f58Installer sample hash listed among the campaign indicators.

MITRE ATT&CK

T1003.001 · LSASS MemoryThe attacker attempted to dump LSASS memory using Procdump64.exe.T1003.003 · NTDSThe attacker used ntdsutil to create a copy of the NTDS database for credential access.T1016 · System Network Configuration DiscoveryThe attacker used ipconfig /all, netstat -ano, and arp -a to gather network configuration and connectivity information.T1018 · Remote System DiscoveryThe attacker used net share and directory listings of administrative shares such as c$ to discover network resources.T1027 · Obfuscated Files or InformationSharkLoader used encrypted, compressed, and packed modules, including PE files with removed MZ headers.T1036 · MasqueradingDroppers were disguised as legitimate installers or applications, including Google Update and Cisco AnyConnect.T1053.005 · Scheduled TaskThe dropper created scheduled tasks to execute SystemSettings.exe, including a task configured to run every five minutes.T1057 · Process DiscoveryThe attacker ran tasklist commands to enumerate processes and search for the malware process.T1069.002 · Domain GroupsThe attacker queried Active Directory groups, including Domain Controllers and Enterprise Admins.T1082 · System Information DiscoveryThe attacker ran systeminfo to collect system information.T1105 · Ingress Tool TransferDroppers wrote SharkLoader components to victim systems; the researchers also suspected components were uploaded through a webshell.T1106 · Native APIThe malware used direct system calls and Windows APIs for process, memory, and loader operations.T1190 · Exploit Public-Facing ApplicationThe operators exploited internet-facing applications, including Microsoft Exchange, Openfire, and GeoServer, to gain access.T1547.001 · Registry Run Keys / Startup FolderIn a Hong Kong incident, the attacker created a registry Run key to launch SystemSettings.exe at user logon.T1574.001 · DLLLegitimate executables such as SystemSettings.exe were used to sideload malicious DLLs, including SystemSettings.dll.

CVE

People

Threat Actors

Malware

Products

Tools

Countries

Industries

Related Articles