Mosquito is a Windows backdoor associated with Turla espionage operations. It is known for using per-user COM hijacking and Registry-based autorun entries to maintain persistence, including abuse of COM class registrations and rundll32-mediated startup of its launcher and backdoor components. The malware stores configuration data in the Windows Registry, executes DLL and EXE payloads through native process creation and library-loading APIs, and can launch PowerShell scripts as part of post-compromise activity.
Mosquito performs host reconnaissance by enumerating running processes and collecting local user and network information through commands such as tasklist, whoami, and ipconfig. It also checks the system and Registry for the presence of antivirus products, indicating security software discovery and defense-evasion awareness before or during execution. The malware has file-deletion capability for cleanup and anti-forensics, and its communications or protected data have been described as using a custom XOR-based stream cipher resembling Blum Blum Shub-derived output.
The malware is notable for stealth-oriented persistence and execution tradecraft rather than commodity crime functionality. Reported behavior supports classification as an espionage backdoor used for long-term access on compromised Windows systems.
Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.
2 distinct threat actors attributed by public researchers. Open in Mallory to see the full evidence chain and overlapping campaigns.
For Mosquito, they used Blum Blum Shub as the random number generator for their XOR byte stream.
In the wild, this trick was often used by groups such as APT 28, Turla, as well as Mosquito backdoor.
20 distinct techniques documented for this family, organized by ATT&CK tactic.
The content repeatedly describes threat actors and malware using WMI/WMIC/wmiexec for remote execution, lateral movement, discovery, persistence, and administrative actions; e.g., 'APT41 used WMI in several ways, including for execution of commands via WMIEXEC as well as for persistence via PowerSploit' and 'Scattered Spider used Windows Management Instrumentation (WMI) to move laterally via Impacket.'
The content repeatedly describes threat actors and malware using PowerShell to execute payloads, run commands, download additional malware, perform lateral movement, evade defenses, and execute scripts in memory. | Examples include: 'APT28 downloads and executes PowerShell scripts and performs PowerShell commands'; 'APT3 has used PowerShell on victim systems to download and run payloads after exploitation'; 'TA505 has used PowerShell to download and execute malware and reconnaissance scripts.'
ADVSTORESHELL is capable of setting and deleting Registry values. Agent Tesla can achieve persistence by modifying Registry key entries. APT41 used a malware variant called GOODLUCK to modify the registry in order to steal credentials.
Today I’ll write about the result of own research into another persistence trick: COM hijacking... COM has been employed in red teaming circumstances for persistence, lateral movement, and defense evasion... An attacker can employ a not-so-common but widely used technique to ensure silent persistence in a system
ADVSTORESHELL achieves persistence by adding itself to the HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run Registry key... APT28 has deployed malware that has copied itself to the startup directory for persistence... FIN7 malware has created Registry Run and RunOnce keys to establish persistence, and has also added items to the Startup folder.
Today I’ll write about the result of own research into another persistence trick: COM hijacking... COM has been employed in red teaming circumstances for persistence, lateral movement, and defense evasion... An attacker can employ a not-so-common but widely used technique to ensure silent persistence in a system
ADVSTORESHELL achieves persistence by adding itself to the HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run Registry key... APT28 has deployed malware that has copied itself to the startup directory for persistence... FIN7 malware has created Registry Run and RunOnce keys to establish persistence, and has also added items to the Startup folder.
The content repeatedly describes payloads, strings, configuration files, scripts, URLs, and binaries being obfuscated or encoded using Base64, XOR, RC4, AES, RSA, hex encoding, custom algorithms, and other methods across many malware families and threat actors.
Examples include 'Mosquito’s installer is obfuscated with a custom crypter,' 'PyDCrypt has been compiled and encrypted with PyInstaller, specifically using the --key flag,' and 'Threat Group-3390 malware is also obfuscated using Metasploit’s shikata_ga_nai encoder.'
The content repeatedly describes malware and threat actors deleting files, directories, droppers, logs, scripts, temporary files, exfiltrated archives, and uninstalling themselves to cover tracks or reduce forensic artifacts.
Adversaries may abuse rundll32.exe to proxy execution of malicious code. Using rundll32.exe, vice executing directly (i.e. Shared Modules), may avoid triggering security tools that may not monitor execution of the rundll32.exe process because of allowlists or false positives from normal operations.
AdFind can extract subnet information from Active Directory; actors used ipconfig /all, netsh.exe, ifconfig, arp, route, nbtstat, and related APIs/commands to gather IP, MAC, DNS, DHCP, gateway, proxy, routing, ARP, and adapter information.
The content repeatedly describes malware and threat actors collecting the username, identifying the current user, enumerating logged-on users, or running commands such as whoami, query user, and quser to determine user context on compromised systems.
Tasklist can be used to discover processes running on a system. Numerous malware families and threat groups are described as listing running processes, collecting PIDs, checking for specific process names, or enumerating loaded modules.
Many entries describe XOR, XOR/ADD, bitwise NOT and XOR, ROR plus XOR, hexadecimal encoding after encryption, and custom encoding/obfuscation of HTTP traffic or beacons.
49 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Turla backdoor/toolset reflecting a shift toward more generic tools in espionage operations.
Backdoor that runs whoami on the victim machine.
A named backdoor mentioned as having used COM hijacking for persistence in the wild.
Uses ipconfig to gather network configuration information.
Match every observed IP, domain, and hash against your live telemetry.
Named campaigns wielding this family, with evidence pinned to each claim.
CVEs this family uses for access and lateral movement.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Every documented technique, ranked by evidence weight.
Reddit, Mastodon, and CTI community discussion around this family.