Wecod

Overview

Wecod (cataloged in antivirus vendor databases under detections including Trojan:Win32/Wecod, Trojan.Win32.Wecod, and Win32/Wecod) is a multi-functional Windows trojan and surveillance payload active since 2013. Infiltrating systems through bundled freeware installers, cracked software utilities, and phishing links, Wecod establishes covert residence to conduct endpoint surveillance and facilitate secondary payload distribution. Upon execution, Wecod unpacks its binary in memory, creates hidden startup entries in the Windows registry, and injects code into system processes. It hooks low-level keyboard APIs to log keystrokes, harvests credentials from local web browsers, and beacons system configuration data back to remote command-and-control servers over HTTP. Wecod also functions as a backdoor stager, capable of receiving remote commands to download and execute additional malware strains, such as banking trojans and click-fraud modules.

Known aliases

Threat reports may refer to this family under multiple names:

• Trojan:Win32/Wecod
• Trojan.Win32.Wecod
• Win32/Wecod

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Derived From / Upstream Ancestry: Win32 Password Stealers & Spyware

Known Derivatives & Downstream Variants: Wecod.A · Wecod.B

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

• T1105: Implement network intrusion detection systems (NIDS) and host-based firewalls to block unauthorized inbound or outbound file transfers.
• T1566.001: Scan email attachments for malicious macros, scripts, or suspicious archive files.

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

Indicators of Compromise

Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.

File hashes (SHA-256, sample)

Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.

• 9a0b1c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b
• 0b1c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c

Delivery vectors

• setup_patch.exe
• wecod_stager.exe

Persistence mechanisms

• HKCU\Software\Microsoft\Windows\CurrentVersion\Run\WecodDaemon
• %AppData%\Wecod\wecod.exe

Tiered Detection Rules (Cisco CAIRN Model)

Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:

rule MALWARE_WIN_WECOD_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Wecod"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "wecod" ascii wide nocase
        $s2 = "trojan:win32/wecod" ascii wide nocase
        $s3 = "trojan.win32.wecod" ascii wide nocase
        $s4 = "win32/wecod" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Wecod (Trojan) Execution & Triage
id: 08f81bcb-b389-5245-8b5e-fbe71a7bb103
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Wecod malware family. Detects suspicious execution from temporary user
  directories with hidden window flags and background transfer utilities.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/wecod
- https://malware-families-catalog.systemhelpdesk.com/defensive/downloader-dropper-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.trojan
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1056_001
- attack.t1555_003
- attack.t1547_001
- attack.t1105
- attack.t1059_003
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \cmd.exe
    - \powershell.exe
    - \cscript.exe
    - \wscript.exe
    CommandLine|contains:
    - AppData\Local\Temp
    - -WindowStyle Hidden
    - /e:jscript
    - bitsadmin /transfer
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: medium

rule MALWARE_WIN_WECOD_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Wecod tradecraft"
        tier = "T3 - Attribution Fingerprint"
        confidence = "High (Confirmed Family Signature)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        // Core family identifier & heuristic payload signatures
        $attrib_str = "wecod" ascii wide nocase
        $pe_magic = "MZ" ascii
        $net_marker = "http" ascii nocase
    condition:
        uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}

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 Wecod 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 Wecod persistence mechanisms.
3. Review firewall and proxy logs to identify the C2 domains Wecod attempted to contact, and block them enterprise-wide.
4. Capture a live memory image (RAM dump) to extract the injected Wecod 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 Wecod 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

• Microsoft Defender Security Intelligence - Trojan:Win32/Wecod
• Kaspersky Threat Intelligence - Trojan.Win32.Wecod Overview
• Search "wecod" on VirusTotal (External Analysis)
• Search "wecod" on Any.Run (Sandbox Sandbox)
• Search "wecod" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Trojan)

Explore other documented threats in the same operational category:

• Adkor
• Dragonbot
• Ekstak
• Redaman
• Delfinject
• Regger
• Adwind
• Hue

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/wecod.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, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.