Shodi

Category: backdoor · Aliases: Backdoor:Win32/Shodi, Trojan:Win32/Shodi, BackDoor.Shohdi · Sample count (EMBER 2018): 76 · Enrichment: curated_sourced · Updated: 2026-10-15
Category: BackdoorStatus: Automated SignaturePlatform: WINDOWS_PEStage: Execution, PersistenceFirst seen: 2008Actor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Unauthorized Access🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 10, Windows 8.1, Windows 7
Executive Summary
Shodi (cataloged across security vendors under detections including Backdoor:Win32/Shodi, Trojan:Win32/Shodi, and BackDoor.Shohdi) is a classic Windows remote access trojan and backdoor active since 2008.

Table of Contents

Overview

Shodi (cataloged across security vendors under detections including Backdoor:Win32/Shodi, Trojan:Win32/Shodi, and BackDoor.Shohdi) is a classic Windows remote access trojan and backdoor active since 2008. Designed to establish persistent, covert remote control over compromised systems, Shodi opens an unauthenticated listening backdoor on dedicated network ports (most commonly TCP port 7352). This allows remote attackers to connect directly to the infected host, execute arbitrary command shell instructions, navigate the local filesystem, upload and download files, and terminate running processes. In addition, Shodi modifies system registry settings under Windows CurrentVersion\Run to ensure autostart across reboots and has been observed acting as a secondary staging platform for dropping ransomware precursors, keyloggers, and network scanning utilities.

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: Classic Win32 Remote Access Trojans

Known Derivatives & Downstream Variants: Shodi.A · Shohdi.B

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-NTINetwork Traffic InspectionDetectT1105Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols.
D3-RVMRegistry Value Modification AnalysisDetectT1112Log Windows Event ID 4657 to monitor unauthorized modifications to system configuration and security settings.
D3-BEABrowser Extension AllowlistingHardenT1176Deploy enterprise browser policies via GPO or Intune to block unauthorized side-loaded extensions and add-ons.
D3-RBIRemote Browser IsolationIsolateT1189Execute untrusted web browsing sessions in disposable cloud containers to isolate drive-by exploits from local endpoints.
D3-STASecurity Tool Anti-Tamper EnforcementHardenT1562.001Block unauthorized modification of antivirus registry flags and prevent stopping security agent services.

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_SHODI_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Shodi"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "shodi" ascii wide nocase
        $s2 = "backdoor:win32/shodi" ascii wide nocase
        $s3 = "trojan:win32/shodi" ascii wide nocase
        $s4 = "backdoor.shohdi" 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 - Shodi (Backdoor) Execution & Triage
id: 035a454d-73fe-5dae-8980-080860caf619
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Shodi malware family. Detects proxy execution, reflective DLL loading,
  and remote command injection associated with modular enterprise backdoors.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/shodi
- https://malware-families-catalog.systemhelpdesk.com/defensive/backdoor-rat-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.backdoor
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1059_003
- attack.t1547_001
- attack.t1105
- attack.t1082
- attack.t1057
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \powershell.exe
    - \cmd.exe
    - \rundll32.exe
    - \regsvr32.exe
    CommandLine|contains:
    - DownloadString
    - IEX(
    - '/s /n /u /i:'
    - sc create
    - start-process
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high

Tier 3 Attribution Fingerprint Rule (High Fidelity)

Deep signature matching distinctive operational fingerprints and payload characteristics.

rule MALWARE_WIN_SHODI_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Shodi 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 = "shodi" 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. Quarantine the endpoint to halt the active exfiltration of browsing telemetry and the downloading of further adware modules.
  2. Audit Windows Group Policies and the Registry to remove any forced extension installation policies (ExtensionInstallForcelist) created by the adware.
  3. Deploy an enterprise adware removal tool (e.g., AdwCleaner) to locate and strip the deeply embedded registry hooks and watchdog services.
  4. Force a complete reset of all installed web browsers to factory defaults to eradicate the rogue extensions and restore the homepage.

What to Avoid

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

  1. Do not rely solely on the browser's 'remove extension' button; Shodi frequently uses GPOs and watchdog services to immediately reinstall itself.
  2. Avoid ignoring the infection; adware tracking data is highly detailed and may expose corporate activities or access to internal portals.

References & External Analysis

Frequently Asked Questions

What is Backdoor:Win32/Shodi?

Shodi is a classic remote access backdoor that opens listening ports to allow attackers remote control over a PC.

Which network port is opened as a backdoor by Shodi?

Shodi commonly opens a listening backdoor on TCP port 7352 for unauthenticated remote administration.

What actions can an attacker execute through the Shodi backdoor?

They can execute terminal commands, upload and download sensitive files, modify the registry, and stage secondary malware.

How does Shodi infect user workstations?

Through malicious phishing attachments, pirated software downloads, and drive-by web exploits.

How should administrators remediate a Shodi infection?

Isolate the computer, close listening ports at the firewall, run a full offline antimalware scan, and change credentials.

How do I remove the Shodi Backdoor from Windows?

Manual removal of Shodi 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 Shodi a virus or a Backdoor?

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

What are the main symptoms of a Shodi infection?

Symptoms of Shodi 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 Backdoors

Want to prevent Shodi and similar threats from compromising your organization? Read our comprehensive defensive guide: Backdoor & RAT 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/shodi.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.