Reconyc

Category: trojan_generic · Aliases: None known · Sample count (EMBER 2018): 222 · Enrichment: expert-seo · Updated: 2026-06-09

Overview

TrojanDownloader:Win32/Reconyc is a highly obfuscated, persistent trojan designed specifically to breach endpoint defenses and securely deliver secondary, high-severity payloads such as ransomware, banking trojans, and botnet agents.

Understanding Reconyc
To an end-user, a Reconyc infection is typically invisible until the devastating secondary payload executes. For threat intelligence analysts, Reconyc is a critical staging mechanism. It functions as an 'Initial Access Broker' tool. Its primary objective is to securely bypass endpoint defenses, profile the infected machine to ensure it is not a sandbox, and reach out to a Command-and-Control (C2) server to pull down the final, destructive payload.

Execution and Evasion Strategies
Reconyc is commonly distributed via massive malspam campaigns containing weaponized attachments (like ZIP files or Office macros) or through exploit kits. Upon execution, it utilizes heavy packing and dynamic API resolution to evade static antivirus signatures. It drops a randomized executable into the %Temp% directory. It establishes persistence by creating a hidden scheduled task or modifying the Registry Run keys. Reconyc frequently injects its downloading routine into legitimate system processes (like explorer.exe or svchost.exe) to mask its outbound network traffic.

Indicators of Compromise (IoCs)
Threat hunters should investigate EDR alerts related to 'Suspicious Process Injection' or 'Anomalous Child Process Spawning'. Network logs will often reveal Reconyc reaching out to compromised domains using encrypted HTTPS traffic. The presence of unexpected, hidden scheduled tasks designed to execute randomly named, highly entropic binaries in the user's profile is a strong IoC. Memory analysis is necessary to extract the injected downloader modules and determine what payloads were requested.

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to the MITRE ATT&CK framework:

TechniqueNameTactic
T1105Ingress Tool TransferCommand and Control
T1055Process InjectionDefense Evasion
T1497.001Virtualization/Sandbox Evasion: System ChecksDefense Evasion
T1566.001Phishing: Spearphishing AttachmentInitial Access
T1027Obfuscated Files or InformationDefense Evasion

Generated Detections (Boilerplate)

These YARA and Sigma rules are auto-generated based on the family name and aliases. They must be heavily tuned before deployment in a production environment.

YARA Rule

rule MALWARE_WIN_RECONYC {
    meta:
        description = "Detects Reconyc (trojan_generic)"
        author = "SystemHelpdesk Boilerplate Generator"
        date = "2026-07-06"
    strings:
        $s1 = "reconyc" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Sigma Rule

title: Suspicious Reconyc Activity
id: 22bf0267d05ad55de9726391553c2174
status: experimental
description: Detects generic indicators of the reconyc malware family.
logsource:
    category: process_creation
    product: windows
detection:
    selection:
        Image|endswith:
            - '\cmd.exe'
            - '\powershell.exe'
        CommandLine|contains:
            - "*reconyc*"
    condition: selection
level: medium

Containment & Response Steps

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

  1. Isolate the endpoint immediately to prevent Reconyc from downloading and executing its secondary payloads (e.g., ransomware).
  2. Audit the Windows Task Scheduler and Registry Run keys to identify and remove the Reconyc persistence mechanisms.
  3. Review firewall and proxy logs to identify the C2 domains Reconyc attempted to contact, and block them enterprise-wide.
  4. Capture a live memory image (RAM dump) to extract the injected Reconyc modules and identify the secondary payloads.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

  1. Do not close an incident simply because the initial Reconyc dropper was quarantined; always verify if secondary payloads were downloaded.
  2. Avoid relying solely on manual file deletion, as the injected processes will likely just recreate the dropped binaries.

References & External Analysis

Related Families (Category: trojan_generic)

Explore other malware families in the same category:

Need help with an active incident? Published by the SystemHelpdesk team.

Machine-readable

Get this profile as JSON: https://jordanricky1604-ship-it.github.io/malware-families-catalog/api/reconyc.json

Ecosystem & Interactive Environments

This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Replit, StackBlitz, CodeSandbox, and CodePen.