Tenga

Category: file_infector · Aliases: Virus:Win32/Tenga, Win32/Tenga.A, Virus.Win32.Gat.a, W32.Gat, Win32/Tenga · Sample count (EMBER 2018): 50 · Enrichment: curated_sourced · Updated: 2026-10-15
Category: File_InfectorStatus: Automated SignaturePlatform: WINDOWS_PEStage: Execution, PersistenceFirst seen: 2005Actor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Parasitic Infection & Botnet Propagation🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows XP, Windows 2000, Windows Server 2003
Executive Summary
Tenga (cataloged across antivirus vendors under signatures including Virus:Win32/Tenga, Win32/Tenga.A, and Virus.Win32.Gat.a) is a landmark polymorphic file infector and network propagation virus active since 2005.

Table of Contents

Overview

Tenga (cataloged across antivirus vendors under signatures including Virus:Win32/Tenga, Win32/Tenga.A, and Virus.Win32.Gat.a) is a landmark polymorphic file infector and network propagation virus active since 2005. Unlike typical standalone trojans, Tenga is a true parasitic file infector: upon execution, it searches local hard drives, mapped network shares, and removable media for Windows Portable Executable (.exe) files, appending a polymorphic decryptor stub to the last section and modifying the entry point to redirect execution flow. Simultaneously, Tenga incorporates an aggressive worm propagation engine that scans random IP addresses across Class B subnets on TCP port 135, weaponizing the historic Microsoft Windows RPC DCOM vulnerability (MS03-026 / CVE-2003-0352) to inject malicious shellcode into remote unpatched systems, open a listening backdoor on TCP port 2005, and download additional malicious payloads.

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: Polymorphic Pe Viral Engine

Known Derivatives & Downstream Variants: Tenga.A · Tenga.B · Gat.A

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-NBANetwork Behavioral AnalysisDetectT1021.002Enforce SMB message signing, disable legacy SMBv1, and restrict administrative share access (C$, ADMIN$) to dedicated PAM bastion hosts.
D3-BDABinary De-obfuscation & UnpackingAnalyzeT1027.001Utilize memory dump scanners and entropy inspection to unpack encrypted stagers during process creation.
D3-RMCRemovable Media Access ControlHardenT1091Enforce Group Policy settings disabling Windows autorun and block execution permissions on removable USB storage media.
D3-NTINetwork Traffic InspectionDetectT1105Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols.
D3-WORMImmutable Backup StorageHardenT1485Store primary backups in Write-Once-Read-Many (WORM) cloud repositories protected by multi-party out-of-band credentials.

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

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_TENGA_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Tenga"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "tenga" ascii wide nocase
        $s2 = "virus:win32/tenga" ascii wide nocase
        $s3 = "win32/tenga.a" ascii wide nocase
        $s4 = "virus.win32.gat.a" ascii wide nocase
        $s5 = "w32.gat" ascii wide nocase
        $s6 = "win32/tenga" 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 - Tenga (File Infector) Execution & Triage
id: bd9a8af9-751e-5338-a902-8b7048d789f8
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Tenga 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/tenga
- https://malware-families-catalog.systemhelpdesk.com/defensive/ransomware-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.file-infector
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1055
- attack.t1210
- attack.t1027
- attack.t1105
- attack.t1082
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_TENGA_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Tenga 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 = "tenga" 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. Instantly sever the infected endpoint from the network to halt the rapid SMB propagation and prevent the corruption of central file shares.
  2. Enforce strict network segmentation, immediately blocking lateral SMB (TCP 445) traffic between workstation subnets.
  3. Do NOT attempt to simply delete the infected files; because Tenga infects legitimate system binaries, deleting them will destroy the OS.
  4. Deploy specialized antivirus 'disinfection' routines (if available) to strip the appended virus code, otherwise, a complete OS rebuild is mandatory.

What to Avoid

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

  1. Do not execute any files from a network share while Tenga is active; you will instantly execute the virus on your local machine.
  2. Avoid assuming standard file deletion works; the virus code is physically merged into the legitimate applications.

References & External Analysis

Frequently Asked Questions

What is Virus:Win32/Tenga (Gat)?

Tenga is a classic polymorphic file infector virus that infects Windows executables and spreads via network vulnerabilities.

How does Tenga infect local executable files?

It appends polymorphic viral code to the last section of PE .exe files and alters the entry point address.

What remote vulnerability is exploited by Tenga to spread across networks?

It exploits the MS03-026 Windows RPC DCOM buffer overflow (CVE-2003-0352) on TCP port 135.

What listening ports are opened by Tenga?

It opens a listening backdoor on TCP port 2005 to receive remote shell commands and payload downloads.

How do antivirus engines clean systems infected with Tenga?

Antivirus disinfection routines excise the viral code from infected PE files, restore original entry points, and patch MS03-026.

How do I remove the Tenga File_Infector from Windows?

Manual removal of Tenga 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 Tenga a virus or a File_Infector?

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

What are the main symptoms of a Tenga infection?

Symptoms of Tenga 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 File_Infectors

Want to prevent Tenga and similar threats from compromising your organization? Read our comprehensive defensive guide: Think You've Been Hacked? What To Do First.

📣 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/tenga.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.