Neshta

Category: file_infector · Aliases: Virus.Win32.Neshta, Virus:Win32/Neshta, Virus:Win32/Neshta.A, W32.Neshta.A, Win32/Neshta · Sample count (EMBER 2018): 443 · Enrichment: curated_sourced · Updated: 2026-10-14
Category: File_InfectorStatus: Automated SignaturePlatform: WINDOWS_PEStage: Execution, PersistenceFirst seen: 2003Actor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Financial Theft🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 10, Windows 7, Windows XP
Executive Summary
Neshta (cataloged across cybersecurity authorities as Virus:Win32/Neshta.A, Virus.Win32.Neshta, and Win32/Neshta) is one of the most prolific, long-standing, and disruptive polymorphic parasitic file infectors in cyber threat history.

Table of Contents

Overview

Neshta (cataloged across cybersecurity authorities as Virus:Win32/Neshta.A, Virus.Win32.Neshta, and Win32/Neshta) is one of the most prolific, long-standing, and disruptive polymorphic parasitic file infectors in cyber threat history. Originally written in Delphi in Belarus in 2003, Neshta infects local fixed drives and removable media by prepending its ~41,472-byte viral code to Windows 32-bit portable executable (.EXE) host files. Crucially, Neshta establishes deep operating system persistence by forcefully modifying the Windows registry command association for all executable files: it alters HKCR\exefile\shell\open\command to '%SystemRoot%\svchost.com "%1" %*'. Consequently, every time any user or system program attempts to execute any .EXE file, the infected Neshta binary runs first, scans storage drives for uninfected executables, infects them, and only then executes the original host program from a decrypted temporary file.

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: Delphi Parasitic File Infector Engines

Known Derivatives & Downstream Variants: Neshta.A · Neshta.B · Win32/Neshta.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

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-BDABinary De-obfuscation & UnpackingAnalyzeT1027Utilize memory dump scanners and entropy inspection to unpack encrypted stagers during process creation.
D3-PIADProcess Injection Analysis & DetectionDetectT1055.002Monitor cross-process thread creation (CreateRemoteThread) and asynchronous procedure calls (QueueUserAPC).
D3-FDAFile Directory Access AuditingDetectT1083Audit and alert on high-frequency recursive directory queries executed by non-system and unclassified binaries.
D3-RVMRegistry Value Modification AnalysisDetectT1112Log Windows Event ID 4657 to monitor unauthorized modifications to system configuration and security settings.
D3-RPMRegistry Persistence MonitoringDetectT1547.001Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management.

Exploited Vulnerabilities (CVEs)

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

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_NESHTA_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Neshta"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "neshta" ascii wide nocase
        $s2 = "virus.win32.neshta" ascii wide nocase
        $s3 = "virus:win32/neshta" ascii wide nocase
        $s4 = "virus:win32/neshta.a" ascii wide nocase
        $s5 = "w32.neshta.a" ascii wide nocase
        $s6 = "win32/neshta" 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 - Neshta (File Infector) Execution & Triage
id: a090395c-b895-5265-8aa8-96a44e40897f
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Neshta 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/neshta
- 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_002
- attack.t1547_001
- attack.t1112
- attack.t1083
- attack.t1027
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_NESHTA_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Neshta 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 = "neshta" 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. Isolate affected endpoints immediately from network shares to stop cross-machine SMB file infection.
  2. Crucial: Restore the registry key HKCR\exefile\shell\open\command to '"%1" %*' before attempting to delete files, otherwise executables will fail to launch.
  3. Delete the dropped viral binary located at %SystemRoot%\svchost.com.
  4. Disinfect infected executables using specialized vendor removal utilities, or re-image systems from known-good golden images.

What to Avoid

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

  1. Never delete %SystemRoot%\svchost.com without first fixing the exefile registry command association, as this will break executable launching across Windows.
  2. Avoid executing clean binaries from mapped drives while connected to an infected workstation.

References & External Analysis

Frequently Asked Questions

What is the Neshta virus (Virus:Win32/Neshta.a)?

Neshta is a classic parasitic file infector virus (Win32/Neshta) first discovered in 2003 in Belarus. Unlike common Trojans or ransomware that drop standalone payloads, Neshta specifically targets and infects 32-bit Portable Executable (.exe) files across local drives and shared network storage. It appends its own compiled malicious code (approximately 41,472 bytes) to the front of legitimate executables, turning trusted host programs into propagation vectors.

How does Neshta hijack system execution and executable files?

When an infected program is launched, Neshta's code executes first. It copies a decrypted standalone virus payload to %SystemRoot%\svchost.com (41 KB) and modifies the critical Windows registry key HKCR\exefile\shell\open\command from "%1" %* to "%SystemRoot%\svchost.com "%1" %*". Because of this association hijack, whenever any .exe file on the system is launched, Windows runs svchost.com first, which infects additional binaries on the disk, decrypts the original host executable into a temporary file, and runs it so the user notices minimal interruption.

Can executable files infected by Neshta be cleaned or repaired?

Yes. Because Neshta is a prepending file infector that embeds the original uncorrupted host binary within itself, specialized cleaning tools (such as Kaspersky Virus Removal Tool, ESET Neshta Cleaner, or Sophos Clean) can strip the 41,472-byte viral header and restore the original executable back to its exact pre-infection state without corrupting the file or requiring complete reinstallation of all software.

Why does svchost.com appear in the Windows directory, and is it related to svchost.exe?

svchost.com is the core dropped binary of Neshta, located directly in C:\Windows\svchost.com. Threat actors deliberately chose this filename to masquerade as the legitimate Windows system process svchost.exe (Service Host). However, legitimate Windows system binaries never use the legacy .com extension and reside in System32. The presence of C:\Windows\svchost.com is a definitive indicator of compromise (IOC) for a Neshta infection.

How do I completely remove Neshta without breaking Windows .exe execution?

Extreme caution is required when cleaning Neshta. If you simply delete svchost.com without restoring the registry first, Windows will lose the ability to run any .exe file (resulting in 'Windows cannot find svchost.com' errors on every click). The safe remediation procedure is: (1) Boot the machine into Windows Safe Mode or a WinPE recovery environment; (2) Restore the registry value HKCR\exefile\shell\open\command and HKLM\SOFTWARE\Classes\exefile\shell\open\command to default "%1" %*; (3) Delete C:\Windows\svchost.com and temporary files in %TEMP%\3582-490\; (4) Run a dedicated disinfector (e.g., Kaspersky KVRT or ESET Neshta Disinfector) to systematically disinfect all prepended PE files across all local drives.

Does Microsoft Defender detect and clean Neshta?

Yes, Microsoft Defender Antivirus detects Neshta variants under the signature Virus:Win32/Neshta.A. When configured with cloud-delivered remediation, Defender's disinfection engine automatically repairs infected host binaries by stripping the injected malicious payload and restoring original registry associations.

What are the primary symptoms of a Neshta infection?

Core symptoms include: (1) Sluggish system performance and elevated disk activity as Neshta scans and infects executables across all drives; (2) Executable file sizes increasing by exactly 41,472 bytes; (3) Detection alerts from multiple programs simultaneously triggering AV file-reputation warnings; (4) The creation of C:\Windows\svchost.com and log files named directx.sys in the Windows folder; (5) Failure to launch .exe files if svchost.com was quarantined without registry repair.

Protect Your Network Against File_Infectors

Want to prevent Neshta 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/neshta.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.

🛡️ Verified Antivirus Support & Customer Assistance

Experiencing issues with unexpected malware infections, persistent adware popups, or security software licensing? Access our verified resolution guides and official customer support helplines:

→ View all 57 TotalAV Antivirus & Security Support Resources