Hosts
Table of Contents
Overview
BrowserModifier:Win32/Hosts (or simply 'Hosts file hijacker') is a generic heuristic detection for malware or adware that maliciously modifies the Windows HOSTS file to redirect web traffic, block security updates, or facilitate phishing.
What is a HOSTS Hijack?
For general consumers, a modified HOSTS file results in bizarre browsing behavior: attempting to visit google.com might redirect to a fake search engine, or attempting to visit microsoft.com simply times out. For incident responders, HOSTS hijacking is a rudimentary but highly effective DNS override technique. The Windows OS checks the local HOSTS file (C:\Windows\System32\drivers\etc\hosts) before querying external DNS servers. Malware exploits this to sinkhole security traffic or redirect banking URLs to attacker-controlled phishing infrastructure.
Infection Vectors & Threat Hunting
Malware variants (ranging from simple adware to severe banking trojans) require local Administrator privileges to modify the HOSTS file. Upon execution, the malware appends hundreds of entries to the file. Commonly, it maps AV update domains (like liveupdate.symantec.com or update.microsoft.com) to 127.0.0.1 (localhost), effectively blinding the endpoint's security software. Alternatively, it maps financial domains (chase.com) to malicious IP addresses. Threat hunters can trivially detect this by monitoring the integrity and size of the HOSTS file.
Forensic Analysis & Impact
The impact ranges from simple annoyance (adware redirection) to severe financial loss (banking phishing) and compromised security posture. Incident responders should immediately open the HOSTS file in Notepad and review the entries. EDR tools frequently trigger alerts when processes other than svchost.exe or authorized admin tools attempt to write to the \drivers\etc\ directory.
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
| Technique | Name | Tactic | Official Spec |
|---|---|---|---|
T1562.001 | Impair Defenses: Disable or Modify Tools | Defense Evasion | ATT&CK ↗ |
T1112 | Modify Registry | Defense Evasion | ATT&CK ↗ |
T1566 | Phishing | Initial Access | ATT&CK ↗ |
T1584 | Compromise Infrastructure | Resource Development | ATT&CK ↗ |
T1498 | Network Denial of Service | Impact | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1566: Implement email filtering, Sender Policy Framework (SPF), DomainKeys Identified Mail (DKIM), and DMARC. Conduct user phishing awareness training.
MITRE D3FEND™ Defensive Countermeasures
Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-RVM | Registry Value Modification Analysis | Detect | T1112 | Log Windows Event ID 4657 to monitor unauthorized modifications to system configuration and security settings. |
D3-TR | Traffic Rate Limiting | Isolate | T1498 | Deploy BGP Flowspec and edge scrubbing proxies to automatically throttle volumetric SYN and UDP reflection attacks. |
D3-STA | Security Tool Anti-Tamper Enforcement | Harden | T1562.001 | Block unauthorized modification of antivirus registry flags and prevent stopping security agent services. |
D3-ESF | Email Sender Authentication & Filtering | Verify | T1566 | Enforce strict SPF, DKIM, and DMARC rejecting p=reject alongside real-time malicious link rewriting. |
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_HOSTS_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Hosts"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "hosts" 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 - Hosts (Trojan Generic) Execution & Triage
id: e67534b9-099c-522b-8158-644b47178a5a
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Hosts 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/hosts
- 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.trojan-generic
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1566
- attack.t1498
- attack.t1562_001
- attack.t1584
- attack.t1112
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_HOSTS_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Hosts 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 = "hosts" 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
}
Containment & Response Steps
Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.
- Open the Windows HOSTS file (<code>C:\Windows\System32\drivers\etc\hosts</code>) with administrative privileges and delete all unauthorized entries.
- Reset the HOSTS file to the Windows default (typically just comments and a localhost mapping).
- Investigate how the malware gained administrative privileges to modify the file in the first place; a larger infection is likely present.
- Run a full EDR sweep to identify the parent executable (often adware or a banking trojan) that orchestrated the modification.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not assume the endpoint is clean just by fixing the HOSTS file; the malware that modified it is almost certainly still active.
- Avoid deleting the HOSTS file entirely; while Windows can recreate it, it is best practice to restore it to the Microsoft default template.
References & External Analysis
- Search "hosts" on VirusTotal (External Analysis)
- Search "hosts" on Any.Run (Sandbox Sandbox)
- Search "hosts" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Hosts and what threat category does it belong to?
Hosts is classified as a Trojan Generic. Documented across security telemetry, it is engineered to execute unauthorized operations, establish persistent footholds on target endpoints, and facilitate malicious campaigns targeting enterprise and individual environments.
How does Hosts establish persistence and evade defensive controls?
Hosts typically establishes persistence through registry run keys, scheduled tasks, or service installations, while evading signature-based antivirus solutions through code obfuscation, memory injection, or anti-analysis sandbox checks.
What are the essential incident response steps for mitigating a Hosts compromise?
Security teams responding to Hosts should immediately isolate affected endpoints from the network, perform memory triage to capture volatile forensic artifacts, audit registry and startup persistence mechanisms, revoke exposed user credentials, and restore systems from verified, clean backups.
What secondary payloads and staging behaviors are commonly associated with Hosts?
Hosts frequently operates as a loader or dropper designed to establish a foothold before downloading and executing secondary high-impact malware payloads. Depending on the threat actor's objectives, these dropped modules can range from ransomware and banking injects to modular infostealers and remote management backdoors.
How can security operations teams effectively detect and hunt for Hosts across enterprise endpoints?
Defenders should hunt for Hosts by deploying behavioral endpoint detection and response (EDR) rules that monitor suspicious process spawning (such as cmd.exe or powershell.exe spawned from office documents or temporary directories), anomalous outbound network connections from non-browser binaries, and unauthorized modifications to Windows Run keys and scheduled task registries.
How do I remove the Hosts Trojan_Generic from Windows?
Manual removal of Hosts 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 Hosts a virus or a Trojan_Generic?
Hosts is classified as a Trojan_Generic. Unlike traditional viruses that infect files, modern malware like Hosts typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Hosts infection?
Symptoms of Hosts 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 Trojan_Generics
Want to prevent Hosts 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.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/hosts.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.