Rodecap

Category: trojan · Aliases: Trojan:Win32/Rodecap.A, Trojan.Win32.Rodecap, TrojanDownloader:Win32/Rodecap, Adware:Win64/Redcap, Trojan.Win64.REDCAP · Sample count (EMBER 2018): 165 · Enrichment: curated_sourced · Updated: 2026-10-15
Category: TrojanStatus: Automated SignaturePlatform: WINDOWS_PEStage: Command And Control, Spam Distribution, Execution, PersistenceFirst seen: 2008Actor: Unknown / CybercriminalIndustry: Global / Opportunistic, Telecommunications, Web HostingMotivation: Spam Distribution🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 7
Executive Summary
Rodecap (cataloged by security vendors as Trojan:Win32/Rodecap.A, Trojan.Win32.Rodecap, TrojanDownloader:Win32/Rodecap, and Adware:Win64/Redcap) is an infamous high-volume spam-distributing trojan and botnet engine active since 2008.

Table of Contents

Overview

Rodecap (cataloged by security vendors as Trojan:Win32/Rodecap.A, Trojan.Win32.Rodecap, TrojanDownloader:Win32/Rodecap, and Adware:Win64/Redcap) is an infamous high-volume spam-distributing trojan and botnet engine active since 2008. Designed to commandeer host system and network resources for illicit spam monetization campaigns, Rodecap spreads through drive-by downloads, exploit kit landing pages, and secondary trojan droppers. Upon execution, the malware drops executable payloads into %APPDATA% disguised as legitimate Windows administrative binaries (such as sessmgr.exe or esentutl.exe), securing persistence via Registry Run keys. Rodecap establishes outbound C2 connections using spoofed HTTP Host headers to retrieve spam email message templates, target recipient lists, and subject lines. The trojan features a built-in multithreaded direct-to-MX SMTP engine operating over TCP port 25 to blast millions of unsolicited pharmaceutical and phishing emails directly from the host, or alternatively uploads malicious PHP scripts to compromised Content Management System (WordPress/Joomla) servers to bypass email reputation filters, frequently resulting in catastrophic IP address blacklisting for infected corporate networks.

Known aliases

Threat reports may refer to this family under multiple names:

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: Direct-To-Mx Smtp Spam Engine · Trojandownloader Framework

Known Derivatives & Downstream Variants: Rodecap.A · Rodecap.B · Rodecap.Gen

MITRE ATT&CK Techniques

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

→ Explore the complete 226-Technique ATT&CK Threat Matrix

Tactical Mitigations

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

MITRE D3FEND™ Defensive Countermeasures

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

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-PIADProcess Injection Analysis & DetectionDetectT1055Monitor cross-process thread creation (CreateRemoteThread) and asynchronous procedure calls (QueueUserAPC).
D3-NTINetwork Traffic InspectionDetectT1105Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols.
D3-TRTraffic Rate LimitingIsolateT1498Deploy BGP Flowspec and edge scrubbing proxies to automatically throttle volumetric SYN and UDP reflection attacks.
D3-RPMRegistry Persistence MonitoringDetectT1547.001Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management.
D3-URLRURL Rewriting & Time-of-Click InspectionFilterT1566.002Rewrite all external email links to force real-time URL reputation and DNS resolution at click time.

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.

Delivery vectors

Persistence mechanisms

SIEM / EDR Ingestion: Need these reference indicators for threat hunting?

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:

Tier 1 Primitive Artifact Rule (Fast Triage)

Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.

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

Tier 2 Behavioral Context Rule (Process Chains & Sigma)

Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.

title: SystemHelpDesk Detection - Rodecap (Trojan) Execution & Triage
id: 2ca79941-6906-50a4-be75-29381b3ec31d
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Rodecap 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/rodecap
- 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.t1566_002
- attack.t1547_001
- attack.t1105
- attack.t1055
- attack.t1498
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

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_RODECAP_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Rodecap 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 = "rodecap" 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
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

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

  1. Block outbound TCP port 25 (SMTP) traffic from user workstations at the perimeter firewall to halt spam blasts immediately.
  2. Inspect running processes for masqueraded system utility names (sessmgr.exe, esentutl.exe) executing outside System32.
  3. Delete persistent registry run entries located in HKCU\Software\Microsoft\Windows\CurrentVersion\Run.
  4. Perform a full endpoint antimalware scan and verify reputation status of corporate IP addresses with anti-spam monitoring services.

What to Avoid

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

  1. Do not permit unrestricted outbound SMTP (port 25) traffic from standard user workstation subnets.
  2. Avoid assuming a slow network is simply an ISP issue; high volume background spam generation is a common indicator of compromise.

References & External Analysis

Frequently Asked Questions

What is the Rodecap trojan family?

Rodecap is a spam-distributing trojan that commandeers infected endpoints and web servers to blast high-volume spam.

How does Rodecap send millions of spam emails?

It uses a built-in multithreaded direct-to-MX SMTP engine on port 25 and abuses compromised CMS web servers.

How does Rodecap disguise its executables on Windows?

It drops binaries into %APPDATA% mimicking legitimate Windows administrative utilities like sessmgr.exe or esentutl.exe.

What operational impact does a Rodecap infection have on an organization?

It causes severe network bandwidth exhaustion and public IP blacklisting on global anti-spam blocklists like Spamhaus.

How can Rodecap be detected and eradicated?

Block outbound TCP port 25 at the network perimeter, terminate spoofed administrative processes, and perform a full AV scan.

How do I remove the Rodecap Trojan from Windows?

Manual removal of Rodecap is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.

Is Rodecap a virus or a Trojan?

Rodecap is classified as a Trojan. Unlike traditional viruses that infect files, modern malware like Rodecap typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.

What are the main symptoms of a Rodecap infection?

Symptoms of Rodecap can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.

Protect Your Network Against Trojans

Want to prevent Rodecap and similar threats from compromising your organization? Read our comprehensive defensive guide: Banking Trojan Protection for Businesses.

📣 Threat Intel Correction or Update?

Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.

Need help with an active incident? Published by the SystemHelpdesk Threat Intelligence Team.

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/rodecap.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.