Spygate

Category: rat · Aliases: SpyGate, SpyGate-RAT, Backdoor.Spygate, Win32/Spygate, Spy-Net Fork · Sample count (EMBER 2018): 127 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: RatStatus: Automated SignaturePlatform: WINDOWS, X86, X64Stage: Initial-Access, Execution, Defense-Evasion, Credential-Access, Collection, Command-And-ControlFirst seen: 2014Actor: Middle Eastern Cybercrime GroupsActor: HacktivistsIndustry: government, military, telecommunications, consumers, activismMotivation: Surveillance, Credential Harvesting & Remote Access🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows Server 2022
Executive Summary
Backdoor:Win32/Spygate (widely known as SpyGate-RAT) is a prominent, commercial Remote Access Trojan builder developed in .NET and Visual Basic that emerged in 2014, architecturally derived from the leaked Spy-Net and njRAT (Bladabindi) codebases.

Table of Contents

Overview

Backdoor:Win32/Spygate (widely known as SpyGate-RAT) is a prominent, commercial Remote Access Trojan builder developed in .NET and Visual Basic that emerged in 2014, architecturally derived from the leaked Spy-Net and njRAT (Bladabindi) codebases. Marketed openly on cybercrime forums and YouTube tutorials, SpyGate became a staple weapon for hacktivists, cybercriminals, and Advanced Persistent Threat groups across the Middle East, North Africa, and Latin America. The malware client compiles compact, highly obfuscated executable payloads that communicate with attacker-controlled command servers over configurable TCP ports (typically 1200 or 1500) using custom delimiter-based plaintext and XOR-encoded commands. SpyGate equips operators with real-time keystroke logging, webcam and microphone spying, remote registry editing, file manager browsing, process termination, and password extraction from major web browsers, email clients, and messenger apps. It utilizes dynamic DNS providers (No-IP, DuckDNS) for resilient C2 resolution and employs process hollowing into svchost.exe and MSBuild.exe to evade host-based behavioral monitoring.

Known aliases

Threat reports may refer to this family under multiple names:

Threat Actor Attribution

Attribution is probabilistic, not a science. Each link below states its confidence level and the evidence behind it.

→ Explore all Threat Actor & APT Campaign Profiles

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: Spy-Net · Njrat

Known Derivatives & Downstream Variants: Spygate V0.2.6 · Spygate V2.9 · Spygate Pro Official

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-PHAProcess Hollowing AnalysisDetectT1055.012Inspect unbacked executable memory regions (PAGE_EXECUTE_READWRITE) for replaced PE image headers inside legitimate host processes.
D3-MFAMulti-factor AuthenticationHardenT1056.001Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless.
D3-WAFWeb Content Filtering & InspectionFilterT1071.001Block newly registered domains (NRDs) and inspect HTTP Host and URI headers for known C2 profiles.
D3-SDScreen Capture DetectionDetectT1113Monitor desktop graphics API calls (BitBlt, GetDC) triggered by non-standard background threads.
D3-HACHardware Device Access ControlIsolateT1125Enforce Group Policy hardware access restrictions on integrated webcams and microphones.
D3-CVHCredential Vault HardeningHardenT1555.003Enable DPAPI master key audit logging and isolate browser SQLite database files within virtualization-based security containers.

Exploited Vulnerabilities (CVEs)

This malware family is documented weaponizing the following common vulnerabilities and exposures:

Command & Control (C2) and Network Profile

How this family talks to its operators. C2 traffic can often identify a family even when its code and configuration are hard to analyse. Ports and patterns are historical and change between campaigns, so use them as hunting leads rather than block-only rules.

ProtocolsTCP, Custom-Binary
Observed ports1200, 1500, 5555
Identifiable from traffic aloneHigh

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_SPYGATE_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Spygate"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "spygate" ascii wide nocase
        $s2 = "spygate" ascii wide nocase
        $s3 = "spygate-rat" ascii wide nocase
        $s4 = "backdoor.spygate" ascii wide nocase
        $s5 = "win32/spygate" ascii wide nocase
        $s6 = "spy-net fork" 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 - Spygate (Rat) Execution & Triage
id: e0f871e3-b3ef-50b8-9e4e-0c469f8b5a45
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Spygate malware family. Detects unauthorized persistence creation via Windows
  Registry Run keys, scheduled tasks, and privilege escalation indicative of RAT installations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/spygate
- 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.rat
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1055_012
- attack.t1056_001
- attack.t1125
- attack.t1113
- attack.t1071_001
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \reg.exe
    - \schtasks.exe
    - \cmd.exe
    - \powershell.exe
    CommandLine|contains:
    - \CurrentVersion\Run
    - /create /tn
    - bypass -enc
    - net user /add
    - net localgroup administrators
  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_SPYGATE_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Spygate 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 = "spygate" 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. Terminate hollowed processes (svchost.exe, MSBuild.exe) spawned from user-writable directories.
  2. Block outbound TCP connections to dynamic DNS providers (No-IP, DuckDNS) on non-standard ports.
  3. Reset browser and email credentials accessed from compromised workstations.
  4. Apply security patches for Microsoft Office equation editor vulnerabilities CVE-2017-0199 and CVE-2017-11882.

What to Avoid

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

  1. Do not allow outbound TCP connections on high non-standard ports from client endpoints.
  2. Avoid opening unverified email attachments promising financial or geopolitical updates.
  3. Never disable endpoint detection and response (EDR) agents to run unverified software.

References & External Analysis

Frequently Asked Questions

What is the SpyGate RAT?

SpyGate is a commercial remote access trojan builder based on .NET that provides keylogging, webcam spying, and browser credential theft.

What malware families is SpyGate derived from?

SpyGate was architecturally derived from the leaked source code of Spy-Net and shares significant protocol similarities with njRAT (Bladabindi).

Where was SpyGate heavily utilized?

SpyGate has been widely documented in cybercrime campaigns and targeted geopolitical surveillance across the Middle East, North Africa, and Latin America.

How does SpyGate maintain command and control?

SpyGate uses dynamic DNS services like No-IP and DuckDNS to connect back to operator control consoles over custom TCP ports.

What vulnerabilities were used to stage SpyGate?

SpyGate was delivered via spear-phishing emails exploiting Microsoft Office vulnerabilities including CVE-2017-0199 and CVE-2017-11882.

How do I remove the Spygate Rat from Windows?

Manual removal of Spygate 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 Spygate a virus or a Rat?

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

What are the main symptoms of a Spygate infection?

Symptoms of Spygate 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 Rats

Want to prevent Spygate 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 team.

Machine-readable

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