Fareit
Table of Contents
Overview
Fareit (widely recognized across the threat intelligence community as Pony or Pony Stealer) is one of the most influential and pervasive credential-harvesting implants in the history of cybercrime. First detected around 2011 and created by a Russian developer known as 'Guptill' (Pony Team), Fareit was crafted in native C and assembly to maximize speed and minimize memory overhead. Fareit's primary objective is the automated theft of stored passwords and digital keys: it scans the local host for credentials stored in over 100 applications, including web browsers, FTP clients (FileZilla, Total Commander), email programs (Outlook, Thunderbird), VPN clients, and early cryptocurrency wallets (Bitcoin, Litecoin). Following the public leak of the Pony 1.9/2.0 source code in late 2013, Fareit became a foundational building block across cybercrime syndicates, frequently serving as an initial access dropper that harvested corporate credentials before downloading heavier secondary payloads such as Gameover Zeus, Necurs, or CryptoLocker ransomware.
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.
- Pony Team / Leaked Source Community High confidence
Basis: Authored originally around 2011 by Russian-speaking developer 'Guptill' (Pony Team). Following the late 2013 leak of the complete Pony 1.9/2.0 source code, hundreds of independent threat actors adapted the builder for widespread credential harvesting and as the primary initial loader for Gameover Zeus and CryptoLocker. [source]
Family Pedigree & Lineage
Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:
Known Derivatives & Downstream Variants: Pony 1.9 · Pony 2.0 · Fareit Loader
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1105: Implement network intrusion detection systems (NIDS) and host-based firewalls to block unauthorized inbound or outbound file transfers.
- T1566.001: Scan email attachments for malicious macros, scripts, or suspicious archive files.
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-EAF | Egress Analysis and Filtering | Isolate | T1041 | Enforce perimeter TLS inspection and alert on anomalous outbound data volume ratios transmitting over active C2 channels. |
D3-NTI | Network Traffic Inspection | Detect | T1105 | Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols. |
D3-RPM | Registry Persistence Monitoring | Detect | T1547.001 | Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management. |
D3-FPA | File Permission Auditing | Harden | T1552.001 | Scan filesystem repositories for plaintext configuration files and restrict access via Least Privilege RBAC controls. |
D3-CVH | Credential Vault Hardening | Harden | T1555.003 | Enable DPAPI master key audit logging and isolate browser SQLite database files within virtualization-based security containers. |
D3-FS | File Sandboxing (Attachment Detonation) | Isolate | T1566.001 | Detonate macro-enabled documents, ISOs, and password-protected archives inside an isolated hypervisor. |
Exploited Vulnerabilities (CVEs)
This malware family is documented weaponizing the following common vulnerabilities and exposures:
- CVE-2017-0199 — In-depth exploitation analysis and catalog intelligence (NIST NVD ↗).
- CVE-2017-11882 — In-depth exploitation analysis and catalog intelligence (NIST NVD ↗).
- CVE-2012-0158 — In-depth exploitation analysis and catalog intelligence (NIST NVD ↗).
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.
| Protocols | HTTP, HTTPS |
|---|---|
| Observed ports | 80, 443 |
| Infrastructure model | PHP-based admin panels (typically gate.php or api.php) hosted on compromised Apache/Nginx web servers. |
| Encryption / encoding | Custom XOR, RC4, or gzip compression encoding exfiltrated credential lists into multipart HTTP POST request bodies. |
| Traffic fingerprint | Single-burst HTTP POST requests to /gate.php, /api.php, or /panel/ with user-agent strings mimicking older Internet Explorer versions or custom fixed strings. |
| Identifiable from traffic alone | High |
Network detection ideas
- Alert on HTTP POST requests to URI paths containing /gate.php or /api.php with high-entropy binary bodies
- Block outbound HTTP/HTTPS connections matching known Fareit/Pony C2 server feeds
- Monitor file system access to browser credential databases and FTP client configuration files (e.g. recentservers.xml)
Sources: MITRE ATT&CK S0103: Pony, CISA Alert AA20-302A
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.
0f1a92e4ab7d2c3e29f8f41e57c6b4f74d0e82c5f10b27b864a78456a287c800c53a74659f170423c91465d3ec62b1e7c53d51786ce45464fb5f4581da9e53be
Delivery vectors
Malicious spam emails disguised as shipping notices or payment advice with weaponized attachmentsDrive-by download compromises via exploit kits
Persistence mechanisms
Temporary execution from %TEMP% directory followed by self-deletion after credential harvestingRegistry Run key in HKCU\Software\Microsoft\Windows\CurrentVersion\Run for loader persistence
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_FAREIT_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Fareit"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "fareit" ascii wide nocase
$s2 = "fareit" ascii wide nocase
$s3 = "pony" ascii wide nocase
$s4 = "pony stealer" ascii wide nocase
$s5 = "pony loader" 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 - Fareit (Infostealer) Execution & Triage
id: 801ec755-9a5c-5b2a-b890-67aa11a0c27b
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Fareit malware family. Detects browser credential database harvesting,
master key queries, and DPAPI extraction routines typical of modern infostealers.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/fareit
- https://malware-families-catalog.systemhelpdesk.com/defensive/infostealer-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.infostealer
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1555_003
- attack.t1539
- attack.t1552_001
- attack.t1041
- attack.t1105
logsource:
category: process_creation
product: windows
detection:
selection_process:
Image|endswith:
- \cmd.exe
- \powershell.exe
- \rundll32.exe
CommandLine|contains:
- \Google\Chrome\User Data\Default\Login Data
- \AppData\Roaming\Mozilla\Firefox\Profiles
- \AppData\Local\Microsoft\Edge\User Data
- vaultcmd.exe /list
- dpapi
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_FAREIT_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Fareit 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 = "fareit" 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.
- Isolate the affected workstation from the corporate network immediately to prevent active exfiltration of harvested credentials, cookies, and tokens by Fareit.
- Force a global session invalidation and mandatory password reset for all cloud applications, corporate email, VPN accounts, and single sign-on (SSO) portals accessed from the machine.
- Inspect and clean local browser credential databases (e.g. SQLite storage in Google Chrome, Microsoft Edge, Mozilla Firefox) and cryptocurrency wallet directories targeted by Fareit.
- Capture endpoint memory to identify process injection and terminate rogue background processes executing credential scraping routines.
- Revoke and re-issue all multi-factor authentication (MFA) session cookies and client TLS certificates present on the compromised workstation.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not allow users to continue typing passwords or accessing sensitive corporate services on an endpoint actively flagged for Fareit.
- Avoid assuming credential compromise is limited to local files; all browser-stored cookies and passwords must be treated as exposed.
References & External Analysis
- Malwarebytes: Spyware.Pony
- CISA Advisory: CISA Alert AA20-302A (Top Routinely Exploited Vulnerabilities)
- Search "fareit" on VirusTotal (External Analysis)
- Search "fareit" on Any.Run (Sandbox Sandbox)
- Search "fareit" on MalwareBazaar (Malware Samples)
North American Authority Advisory (CISA / NIST)
The Cybersecurity and Infrastructure Security Agency (CISA) has published an official US federal advisory on this family, which can be mapped to NIST Cybersecurity Framework (CSF) incident response controls: CISA Alert AA20-302A (Top Routinely Exploited Vulnerabilities) ↗
Frequently Asked Questions
What is Fareit (Pony Stealer)?
Fareit (Pony) is a high-speed credential stealer and downloader written in C and assembly that harvests passwords from over 100 applications, including browsers, FTP clients, and cryptocurrency wallets.
Who created Fareit / Pony?
Fareit was created around 2011 by a developer known as Guptill (Pony Team). After its source code leaked in late 2013, it was adopted by cybercrime groups across the globe.
How does Fareit exfiltrate stolen credentials?
Fareit bundles harvested passwords into compressed, XOR/RC4 encrypted POST packets sent directly to PHP administrative panels (typically gate.php) on compromised web servers.
What role did Fareit play in major ransomware campaigns?
Fareit frequently functioned as a first-stage loader: after extracting all credentials from the victim machine, it downloaded secondary malware such as Gameover Zeus or CryptoLocker.
How can organizations defend against Fareit?
Enforce Multi-Factor Authentication (MFA) to render stolen static passwords useless, block outbound connections to known gate.php panels, and patch Office vulnerabilities like CVE-2017-11882.
How do I remove Fareit from Windows?
Manual removal of Fareit 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.
What are the main symptoms of a Fareit infection?
Symptoms of Fareit 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 Infostealers
Want to prevent Fareit and similar threats from compromising your organization? Read our comprehensive defensive guide: InfoStealer Protection & Remediation.
📣 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/fareit.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.