Proxyagent

Overview

Executive Summary

Technical Architecture and Exploitation

• Silent Installation and Persistence: The malware installs itself as a hidden background service or injects its code into a legitimate network-facing process (like `svchost.exe`). It modifies Windows Firewall rules to allow inbound connections on a specific port chosen by the attacker.
• C2 Registration: The trojan registers the infected machine's IP address, bandwidth capacity, and open proxy port with a centralized command-and-control (C2) server. The infected machine is now part of a commercial proxy botnet (often sold on the dark web).
• Traffic Routing: The attacker routes arbitrary traffic through the infected host. This traffic may include credential stuffing attacks against other organizations, spam distribution, or illegal file sharing, all of which appear to originate from the victim's corporate network.

Threat Impact

Incident Response and Mitigation

• Network Anomaly Detection: Monitor edge firewalls for sustained, high-volume inbound and outbound traffic on non-standard ports, which is highly indicative of an active proxy relay.
• Endpoint Isolation: If a host is identified acting as a proxy, immediately isolate it from the network to halt the illicit traffic routing and prevent IP reputation damage.
• Forensic Review: A proxy trojan is rarely the only malware on a system. Conduct a full forensic review to identify the initial access vector (the dropper) and determine if other, more destructive payloads (like info-stealers) were also deployed alongside the ProxyAgent.

Known aliases

Threat reports may refer to this family under multiple names:

• Trojan.ProxyAgent
• Proxy.Botnet
• Win32/ProxyAgent

MITRE ATT&CK Techniques

This family has been observed using the following ATT&CK techniques: T1090.002 T1562.004 T1543.003

Generated Detections (Boilerplate)

These YARA and Sigma rules are auto-generated based on the family name and aliases. They must be heavily tuned before deployment in a production environment.

YARA Rule

rule MALWARE_WIN_PROXYAGENT {
    meta:
        description = "Detects Proxyagent (trojan)"
        author = "SystemHelpdesk Boilerplate Generator"
        date = "2026-07-06"
    strings:
        $s1 = "proxyagent" ascii wide nocase
        $s2 = "trojan.proxyagent" ascii wide nocase
        $s3 = "proxy.botnet" ascii wide nocase
        $s4 = "win32/proxyagent" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

Sigma Rule

title: Suspicious Proxyagent Activity
id: d0e98b4031996a98483cf131a651fb9c
status: experimental
description: Detects generic indicators of the proxyagent malware family.
logsource:
    category: process_creation
    product: windows
detection:
    selection:
        Image|endswith:
            - '\cmd.exe'
            - '\powershell.exe'
        CommandLine|contains:
            - "*proxyagent*"
            - "*trojan.proxyagent*"
            - "*proxy.botnet*"
            - "*win32/proxyagent*"
    condition: selection
level: medium

References & External Analysis

• Search "proxyagent" on VirusTotal (External Analysis)

Frequently Asked Questions

Related Families (Category: trojan)

Explore other malware families in the same category:

• Doser
• Clipbanker
• Bitter
• Findkeyxp
• Hostseditor

Machine-readable

Get this profile as JSON: https://jordan123234-malware-families-explorer.static.hf.space/api/proxyagent.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.