YiBackdoor: A New Malware Family With Links to IcedID and Latrodectus

YiBackdoor: A New Malware Family With Links to IcedID and Latrodectus

Zscaler ThreatLabz identified a new backdoor family named YiBackdoor in June 2025 that can collect system information, capture screenshots, execute commands, and load plugins, and shows significant code overlap with IcedID and Latrodectus. The malware includes anti-analysis checks, injects into svchost.exe, persists via Run registry entries using regsvr32.exe, and communicates with C2 servers using dynamic TripleDES keys. #YiBackdoor #IcedID #Latrodectus

Keypoints

  • YiBackdoor was first observed in June 2025 and is likely in development or testing based on limited deployments and local C2 entries.
  • The malware can gather system info, take screenshots, execute commands (cmd/PowerShell), and load encrypted plugins that expand functionality.
  • ThreatLabz found notable code overlaps between YiBackdoor, IcedID, and Latrodectus, including similar decryption routines, GUID lists, and hashing/charset usage.
  • YiBackdoor uses anti-analysis techniques targeting virtualized environments: CPUID hypervisor checks, timing-based VM detection, runtime string decryption, and dynamic API resolution via ROR-based hashing.
  • Initialization includes mutex checks, DLL range checks to ensure injection, creating an svchost.exe process and hooking RtlExitUserProcess to transfer execution, then establishing persistence with a Run registry entry using regsvr32.exe and randomized names.
  • Network communication uses a decrypted configuration to build http(s)://C2/bot_id/uri1/uri2, sends Base64-encoded TripleDES-encrypted JSON in the X-tag header, and accepts JSON commands in responses.
  • Plugins are stored encrypted as random .bin files in the temp folder, decrypted with a per-plugin algorithm, and reloaded on each execution; command results are reported back via HTTP POST in JSON.

MITRE Techniques

  • [T1055] Process Injection – YiBackdoor injects into a newly created svchost.exe, allocates memory and copies its code, and hooks RtlExitUserProcess to redirect execution: ‘YiBackdoor creates a new svchost.exe process and injects its code into it… YiBackdoor patches the Windows API function RtlExitUserProcess… the malware’s code executes just as the target process is about to terminate.’
  • [T1547.001] Registry Run Keys / Startup Folder – Establishes persistence by copying the DLL to a random directory and adding a Run registry value using regsvr32.exe with a pseudo-random name: ‘YiBackdoor adds regsvr32.exe malicious_path in the registry value name (derived using a pseudo-random algorithm) and self-deletes.’
  • [T1204.002] User Execution: Malicious File – Uses regsvr32.exe in the Run key to execute the malicious DLL at startup (implied by persistence mechanism described above): ‘YiBackdoor adds regsvr32.exe malicious_path in the registry value name…’
  • [T1027] Obfuscated Files or Information – Decrypts strings at runtime by pushing encrypted strings onto the stack and XOR-ing with a unique 4-byte key for each string: ‘Decrypts strings at runtime by pushing an encrypted string onto the stack, which is then decrypted by performing an XOR operation with a 4-byte key (that is unique for each encrypted string).’
  • [T1497.001] Virtualization/Sandbox Evasion: System Checks – Uses CPUID with 0x40000000 and timing via rdtsc + CPUID loops to detect hypervisors and VMs, comparing results to known hypervisor values (VMWare, Xen, KVM, VirtualBox, Hyper-V, Parallels): ‘YiBackdoor utilizes the CPUID instruction with the parameter 0x40000000 to retrieve hypervisor information… the final calculated value must be greater than 20 to bypass the detection.’
  • [T1005] Data from Local System – Collects system information (Windows version, process list, network info), and executes system commands like whoami, ipconfig, net view to gather host data: ‘Collects the following system information: Windows version. List of process names. Network and miscellaneous system information by executing the system commands… chcp 65001 whoami /all arp -a ipconfig /all net view /all…’
  • [T1113] Screen Capture – Captures screenshots and reports them back to C2 (Base64-encoded): ‘Takes a screenshot of the compromised host’s desktop.’ and ‘Screenshot encoded in Base64 format.’
  • [T1105] Ingress Tool Transfer – Downloads and stores plugins received from C2 as encrypted .bin files in the Temp folder and decrypts them for execution: ‘YiBackdoor stores each plugin that is received locally in the Windows temporary folder using a random filename with the file extension .bin… Each plugin is stored in an encrypted format.’
  • [T1041] Exfiltration Over C2 Channel – Sends command outputs and status to C2 via HTTP POST with JSON, and uses encrypted data in the X-tag HTTP header for communication: ‘The encrypted output is then Base64-encoded and appended to the HTTP header X-tag, and sent in an HTTP GET request.’ and ‘YiBackdoor reports the output of each command to the C2 by sending an HTTP POST request.’

Indicators of Compromise

  • [File Hash] YiBackdoor sample SHA256 – af912f6f4bea757de772d22f01dc853fc4d7ab228dc5f7b7eab2a93f64855fbe
  • [Domain/IP] C2 Server – http://136.243.146[.]46:8898 (YiBackdoor C2)
  • [File Name Pattern] Plugin files – random .bin files stored in Temp (identified by YiBackdoor filename generation algorithm) – example: plugin_name-.bin (and other random .bin names)
  • [Registry] Persistence entry – Run key using regsvr32.exe with a pseudo-random registry value name derived by the malware (no specific name provided)


Read more: https://www.zscaler.com/blogs/security-research/yibackdoor-new-malware-family-links-icedid-and-latrodectus