Mafalda is a Windows backdoor associated with the Metador espionage threat actor and appears to be an actively maintained, feature-rich interactive implant. It has been observed in operations targeting telecommunications providers, internet service providers, and universities in the Middle East and Africa as part of long-term access and intelligence collection activity. In Metador intrusions, Mafalda was deployed through an in-memory infection chain involving the companion malware metaMain, with persistence established via WMI event subscription and execution mediated through Microsoft debugging tooling to hinder analysis.
Mafalda supports a large command set and is designed for flexible post-compromise operations. Documented capabilities include discovery of security software and analysis tools, user and system information collection, registry enumeration and modification, execution of Windows command shell and PowerShell commands, local data collection and staging, and exfiltration of host data and files to command-and-control infrastructure. It can collect browser-related material including Chrome Local State data associated with browser encryption keys, and it has been linked to credential-access behaviors including access token manipulation, LSASS credential dumping, and collection of unsecured credentials such as private keys. Additional reported functions include screenshot capture, input capture, event log clearing, service-based execution, ingress tool transfer, and use of SSH from compromised hosts.
Mafalda uses HTTP and raw TCP for command and control, can encode data with Base64 prior to exfiltration, and newer variants incorporate substantial obfuscation and anti-analysis measures. Internal documentation and version progression indicate ongoing development, with later builds expanding command coverage and complicating reverse engineering. The malware has also been described as supporting collection workflows involving Linux systems through an auxiliary implant, but Mafalda itself is primarily a Windows malware platform.
Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.
1 distinct threat actor attributed by public researchers. Open in Mallory to see the full evidence chain and overlapping campaigns.
Metador has used unique malware in their operations, including metaMain and Mafalda.
31 distinct techniques documented for this family, organized by ATT&CK tactic.
metaMain... provides operators with extensive functionality... and the ability to execute arbitrary shellcode. ... The functionalities of the backdoor commands have a very broad scope and include credential theft, data and information theft, command execution...
The content repeatedly describes threat actors and malware using PowerShell scripts/commands for execution, download, staging, reconnaissance, persistence, credential access, lateral movement, and defense evasion; e.g., "Sandworm Team used PowerShell scripts to run a credential harvesting tool in memory to evade defenses."
During the 2016 Ukraine Electric Power Attack, Sandworm Team used the xp_cmdshell command in MS-SQL. During the 2025 Poland Wiper Attacks, the adversaries leveraged PsExec to run cmd.exe commands on multiple victim machines. Numerous malware families and groups are described as using cmd.exe, cmd /c, Windows command shell, or command-line interfaces to execute commands, payloads, reconnaissance, persistence, cleanup, and ransomware actions.
During the 2015 Ukraine Electric Power Attack, Sandworm Team modified in-registry Internet settings to lower internet security before launching rundll32.exe ... AADInternals can modify registry keys ... ADVSTORESHELL is capable of setting and deleting Registry values ... [many additional examples].
When the TCP KNOCK communication method is enabled, the metaMain and Mafalda implants can establish an indirect connection to the C2 server through another implant... metaMain and Mafalda authenticate themselves to Cryshell through a port-knocking and handshake procedure.
In this case, metaMain’s persistence relies on the abuse of WMI Event Subscriptions. The operators register an event consumer named hard_disk_stat. Five to six minutes after booting up, the event triggers the execution of a LOLbin, cdb.exe.
In this case, metaMain’s persistence relies on the abuse of WMI Event Subscriptions. The operators register an event consumer named hard_disk_stat. Five to six minutes after booting up, the event triggers the execution of a LOLbin, cdb.exe.
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 throughout the content include 'encrypted payloads decrypted and executed in memory,' 'encrypts its configuration file,' 'AES-encrypted resource,' 'RC4 encrypted embedded scripts,' and 'payload includes an encrypted main component.'
The content repeatedly describes malware and threat actors decoding, decrypting, deobfuscating, or unpacking payloads, strings, configuration data, commands, and C2 responses prior to execution or use.
When the TCP KNOCK communication method is enabled, the metaMain and Mafalda implants can establish an indirect connection to the C2 server through another implant... metaMain and Mafalda authenticate themselves to Cryshell through a port-knocking and handshake procedure.
Among them, we noticed the use of an unusual LOLbin, the Microsoft Console Debugger cdb.exe. CDB was the root of an intricate infection chain that would yield two in-memory malware platforms... The attackers used the following command line: cdb.exe -cf c:\windows\system32\cdb.ini c:\windows\system32\defrag.exe -module fcache13.db
During the 2015 Ukraine Electric Power Attack, Sandworm Team modified in-registry Internet settings to lower internet security before launching rundll32.exe ... AADInternals can modify registry keys ... ADVSTORESHELL is capable of setting and deleting Registry values ... [many additional examples].
The content repeatedly describes malware and threat actors querying, enumerating, opening, and reading Windows Registry keys and values, e.g., "APT41 queried registry values to determine items such as configured RDP ports and network configurations" and "Reg may be used to gather details from the Windows Registry of a local or remote system at the command-line interface."
The content repeatedly describes malware and threat actors using commands and APIs such as ipconfig /all, ifconfig, arp -a, route print, nbtstat, netsh, GetAdaptersInfo, and GetIpNetTable to gather IP addresses, MAC addresses, DNS, DHCP, gateways, routing tables, ARP cache, proxy settings, domains, and network adapter/interface details.
The content repeatedly describes malware and threat actors collecting usernames, identifying logged-in users, running whoami/query user/quser, checking whether the current user is an administrator, enumerating user sessions, and gathering account details from compromised hosts.
The content repeatedly describes malware and threat actors obtaining lists of running processes, using utilities such as tasklist, ps, WMI, Get-Process, CreateToolhelp32Snapshot, EnumProcesses, and similar APIs/commands to enumerate active processes on victim systems.
The content is a long ATT&CK-style listing of malware and threat actors that collect host details such as OS version, hostname, architecture, CPU, memory, BIOS, language, and other basic system characteristics; examples include use of commands like systeminfo, ver, uname, sw_vers, and WMI queries.
Multiple entries describe enumerating local, logical, or physical drives and disk/volume information, e.g., 'can enumerate local drives,' 'GetLogicalDrives,' 'fsutil fsinfo drives,' 'list drives,' and 'discover logical drive information including the drive type, free space, and volume information.'
The content repeatedly describes threat actors and malware collecting, stealing, identifying, copying, or staging files, documents, credentials, logs, databases, and other information from compromised hosts or local systems.
Mafalda also supports retrieval of data from Linux machines with another implant that sends data to the C2 as part of a packet with a name prefixed with loot_linux\.
That IP is utilized for command-and-control over either HTTP (metaMain, Mafalda) or raw TCP (Mafalda).
The content repeatedly describes threat actors and malware using HTTP and HTTPS for command and control, such as: "Sandworm Team used BlackEnergy to communicate between compromised hosts and their command-and-control servers via HTTP post requests."
‘Cryshell’– a custom implant used for bouncing connections in an internal network to external command-and-control servers... When the TCP KNOCK communication method is enabled, the metaMain and Mafalda implants can establish an indirect connection to the C2 server through another implant.
That IP is utilized for command-and-control over either HTTP (metaMain, Mafalda) or raw TCP (Mafalda). In addition to HTTP, external Mafalda C2 servers also support raw TCP connections over port 29029.
C2 traffic from ADVSTORESHELL is encrypted, then encoded with Base64 encoding... APT19 HTTP malware variant used Base64 to encode communications to the C2 server... APT33 has used base64 to encode command and control traffic.
When the TCP KNOCK communication method is enabled, the metaMain and Mafalda implants can establish an indirect connection to the C2 server through another implant... metaMain and Mafalda authenticate themselves to Cryshell through a port-knocking and handshake procedure.
2 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Full values are available in Mallory.
IPs, domains, and DNS infrastructure linked to this family.
50 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
... Mafalda ... (v1.1→v1.2) ...
Mafalda (v1.1→v1.2)
A Windows interactive backdoor/implant operated fully in memory. It supports 67 commands in newer variants, including credential theft, data theft, command execution, registry and file system manipulation, reconfiguration, and communication over HTTP or raw TCP. It is actively maintained and heavily obfuscated in newer builds.
Unique malware used in Metador operations.
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.