Feedarch

Overview

Executive Summary

Distribution and Technical Behavior

• Browser Hijacking: Feedarch aggressively alters the browser's default search engine, homepage, and new tab settings. All search traffic is redirected through an affiliate-linked search portal controlled by the adware operators, allowing them to generate illicit pay-per-click revenue.
• Traffic Interception: The software frequently installs a local proxy server or malicious browser extensions to intercept unencrypted web traffic. It overlays legitimate websites with disruptive pop-ups, pop-unders, and sponsored in-text hyperlinks.
• System Alteration: To ensure it remains active, Feedarch creates persistent Scheduled Tasks and modifies the Windows Registry to automatically launch its components upon system boot.

Risk Assessment

Mitigation and Removal Strategies

• Endpoint Scanning: Utilize a reputable enterprise-grade anti-malware solution to perform a deep system scan, targeting the Feedarch executables, hidden scheduled tasks, and persistent registry keys.
• Browser Remediation: Manually inspect and remove any unknown or unauthorized extensions from all installed web browsers. Perform a complete factory reset of the browsers to clear the hijacked proxy and search settings.
• Application Control: Enforce strict application whitelisting policies to prevent standard users from executing unapproved software installers that are the primary vector for this adware.

Known aliases

Threat reports may refer to this family under multiple names:

• Adware.Feedarch
• PUP.Feedarch
• BrowserModifier:Win32/Feedarch

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:

• T1566.002: Inspect email links for known malicious domains and use link-rewriting services for time-of-click analysis.

MITRE D3FEND™ Defensive Countermeasures

Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):

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:

rule MALWARE_WIN_FEEDARCH_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Feedarch"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "feedarch" ascii wide nocase
        $s2 = "adware.feedarch" ascii wide nocase
        $s3 = "pup.feedarch" ascii wide nocase
        $s4 = "browsermodifier:win32/feedarch" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Feedarch (Ransomware) Execution & Triage
id: 8976e772-d6ac-513e-8096-7047fd96d371
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Feedarch malware family. Detects volume shadow copy deletion, boot status
  tampering, and recovery inhibition characteristic of modern ransomware operations.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/feedarch
- 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.ransomware
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1566_002
- attack.t1176
- attack.t1112
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \vssadmin.exe
    - \wmic.exe
    - \wbadmin.exe
    - \bcdedit.exe
    CommandLine|contains:
    - delete shadows
    - shadowcopy delete
    - resize shadowstorage
    - recoveryenabled no
    - ignoreallfailures
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: critical

rule MALWARE_WIN_FEEDARCH_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Feedarch 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 = "feedarch" 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.

1. Immediately isolate affected host(s) from the internal network (disconnect physical Ethernet and disable Wi-Fi/Bluetooth) to prevent Feedarch from spreading laterally or encrypting network-attached storage (NAS) and shared SMB volumes.
2. Preserve volatile system memory (RAM capture) on a representative endpoint before attempting a reboot or power-down, as Feedarch symmetric encryption keys or uncompiled payload components may still reside in memory.
3. Audit process execution logs and terminate active scripting interpreters (e.g. PowerShell, CMD, WScript) or commands executing 'vssadmin.exe delete shadows' or 'wbadmin' used by Feedarch to inhibit recovery.
4. Investigate the initial compromise vector (such as exposed RDP instances, spearphishing attachments, or vulnerable edge gateways) and enforce an immediate credential reset for all compromised Active Directory accounts.
5. Restore critical assets and databases exclusively from verified, air-gapped, or immutable offline backups once the Feedarch binary and related persistence hooks are eradicated.

What to Avoid

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

1. Do not restart or power cycle infected systems prematurely; doing so destroys volatile RAM encryption keys and may trigger bootloader locking logic embedded in Feedarch.
2. Avoid negotiating or paying the extortion demand without prior forensic evaluation and consultation with incident response specialists, as payment does not guarantee data recovery.
3. Do not connect clean backup drives or external storage to the affected network until Feedarch eradication is completely verified.

References & External Analysis

• Search "feedarch" on VirusTotal (External Analysis)
• Search "feedarch" on Any.Run (Sandbox Sandbox)
• Search "feedarch" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Ransomware)

Explore other documented threats in the same operational category:

• Burnwoo
• Etap
• Minggy
• Obfusransom
• Pepm
• Webhat
• Cryptojoker
• Golroted

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/feedarch.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.