Harvester
Table of Contents
Overview
Executive Summary
Harvester (often detected as Spyware.Harvester or Trojan.Harvester) is a highly specialized info-stealer malware engineered specifically to target, aggregate, and extract sensitive data from compromised Windows endpoints. Unlike generic droppers, Harvester's primary objective is immediate espionage: it actively scrapes the file system and intercepts communications to harvest user credentials, financial information, and valuable intellectual property.Infection Vector and Technical Capabilities
Harvester is typically distributed via highly targeted spear-phishing campaigns containing weaponized attachments or delivered as a secondary payload by an initial access broker. Once executed, the malware focuses entirely on data aggregation:- Browser Profiling and Cookie Theft: Harvester aggressively targets nearly all modern web browsers (Chrome, Firefox, Edge). It extracts saved passwords, autofill data, credit card numbers, and critically, active session cookies (allowing attackers to bypass MFA).
- File System Scraping: The malware often includes a module to recursively scan the local hard drive and attached network shares for files matching specific extensions (e.g., `.docx`, `.pdf`, `.kdbx` for password vaults) or containing specific keywords (e.g., "password", "finance").
- Data Exfiltration: The stolen data is aggregated into hidden, encrypted ZIP archives on the local disk. It is then periodically transmitted back to the C2 server over standard web ports (HTTPS) or via FTP to evade deep packet inspection.
Threat Assessment
A Harvester infection is a critical security breach resulting in immediate and ongoing data loss. The exfiltrated credentials can be used to compromise the user's personal accounts, pivot laterally across the corporate network, or access sensitive cloud infrastructure without triggering brute-force alerts.Incident Response and Remediation
- Immediate Isolation: Sever the affected machine's network connection immediately to halt any active or pending data exfiltration.
- Comprehensive Credential Reset: Assume all credentials typed or saved on the infected machine since the time of infection are fully compromised. Initiate an immediate, organization-wide password reset for the affected user, and invalidate all active session tokens.
- Forensic Analysis: Conduct a forensic review of the endpoint to determine the initial vector of compromise and to ensure Harvester did not deploy secondary backdoors prior to detection.
Known aliases
Threat reports may refer to this family under multiple names:
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 |
|---|---|---|---|
T1056.001 | Keylogging | Credential Access | ATT&CK ↗ |
T1539 | Steal Web Session Cookie (Abusing active authenticated sessions to perform social media fraud) | Credential Access | ATT&CK ↗ |
T1048 | Exfiltration Over Alternative Protocol | Exfiltration | ATT&CK ↗ |
T1552.001 | Credentials In Files (Harvesting passwords and wallets from local storage) | Credential Access | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1056.001: Implement Endpoint Detection and Response (EDR) to monitor for suspicious API calls related to keystroke interception. Enforce Multi-Factor Authentication (MFA) to render stolen passwords useless.
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-NDF | Network Data Filtering | Isolate | T1048 | Inspect non-standard port traffic and block unauthorized ICMP or DNS tunneling protocols at the network perimeter. |
D3-MFA | Multi-factor Authentication | Harden | T1056.001 | Enforce FIDO2 / WebAuthn physical tokens to render keystroke-intercepted passwords useless. |
D3-FPA | File Permission Auditing | Harden | T1552.001 | Scan filesystem repositories for plaintext configuration files and restrict access via Least Privilege RBAC controls. |
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_HARVESTER_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Harvester"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "harvester" ascii wide nocase
$s2 = "trojan.harvester" ascii wide nocase
$s3 = "spyware.harvester" ascii wide nocase
$s4 = "pws.win32.harvester" 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 - Harvester (Trojan) Execution & Triage
id: b513638f-c108-509f-b70a-f32a927061b5
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Harvester 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/harvester
- https://malware-families-catalog.systemhelpdesk.com/defensive/downloader-dropper-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
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1056_001
- attack.t1539
- attack.t1048
- attack.t1552_001
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: mediumTier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_HARVESTER_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Harvester 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 = "harvester" 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.
- Sever network connectivity for the flagged endpoint to terminate persistent command-and-control (C2) communication channels and stop Harvester from retrieving secondary stage payloads.
- Capture process memory triage to detect and terminate malicious threads injected by Harvester into legitimate system processes such as explorer.exe or svchost.exe.
- Audit Windows Registry Run keys (HKCU\Software\Microsoft\Windows\CurrentVersion\Run) and Task Scheduler entries to locate and purge Harvester persistence hooks.
- Deploy updated enterprise EDR detection signatures and conduct an out-of-band endpoint scan to isolate dropped binaries and staged payloads.
- Rotate all credentials, domain user passwords, and session cookies active on the system during the Harvester execution timeframe.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not assume the incident is resolved simply because an antivirus tool removed the initial Harvester dropper; always verify that secondary payloads and persistence hooks have been eradicated.
- Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Harvester until memory triage is complete.
- Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.
References & External Analysis
- Search "harvester" on VirusTotal (External Analysis)
- Search "harvester" on Any.Run (Sandbox Sandbox)
- Search "harvester" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Harvester and what threat category does it belong to?
Harvester is classified as a Trojan. 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 Harvester establish persistence and evade defensive controls?
Harvester 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 Harvester compromise?
Security teams responding to Harvester 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 Trojan.Harvester?
Trojan.Harvester 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 Trojan.Harvester across enterprise endpoints?
Defenders should hunt for Trojan.Harvester 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 Harvester Trojan from Windows?
Manual removal of Harvester 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 Harvester a virus or a Trojan?
Harvester is classified as a Trojan. Unlike traditional viruses that infect files, modern malware like Harvester typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Harvester infection?
Symptoms of Harvester 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 Trojans
Want to prevent Harvester 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/harvester.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.