Bunitu

Category: trojan · Aliases: Trojan:Win32/Bunitu, Trojan.Win32.Bunitu, Trojan.Bunitu, Win32/Bunitu, Bunitu Proxy Bot · Sample count (EMBER 2018): 49 · Enrichment: curated_sourced · Updated: 2026-10-15
Category: TrojanStatus: Automated SignaturePlatform: WINDOWS_PEStage: Execution, PersistenceFirst seen: 2014Actor: Unknown / CybercriminalIndustry: Global / OpportunisticMotivation: Residential Proxy Monetization & Fraud Relaying🕸 Explore Relationship Graph⚙ API JSON⚡ Sigma Rule💾 YARA RuleOS: Windows 11, Windows 10, Windows 8.1
Executive Summary
Bunitu (cataloged across security intelligence feeds under signatures including Trojan:Win32/Bunitu, Trojan.Win32.Bunitu, and Trojan.Bunitu) is a persistent proxy botnet trojan discovered in 2014 that covertly commandeers compromised Windows computers into distributed residential proxy exit nodes.

Table of Contents

Overview

Bunitu (cataloged across security intelligence feeds under signatures including Trojan:Win32/Bunitu, Trojan.Win32.Bunitu, and Trojan.Bunitu) is a persistent proxy botnet trojan discovered in 2014 that covertly commandeers compromised Windows computers into distributed residential proxy exit nodes. Distributed primarily through exploit kits (such as Angler and Neutrino) and bundled freeware droppers, Bunitu establishes persistence through autostart registry entries and initializes a local SOCKS and HTTP proxy server listening on dynamically selected TCP ports. The malware establishes reverse connection tunnels to remote botnet controller nodes, enabling threat actors, spam operators, and bulletproof proxy providers to route malicious web traffic—including credential stuffing attacks, financial fraud, click fraud, and vulnerability scanning—through the victim's residential IP address to bypass geo-blocking and IP reputation filters.

Known aliases

Threat reports may refer to this family under multiple names:

Family Pedigree & Lineage

Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:

Derived From / Upstream Ancestry: Bunitu Proxy Bot Architecture

Known Derivatives & Downstream Variants: Bunitu.A · Bunitu.Socks

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

→ Explore the complete 226-Technique ATT&CK Threat Matrix

Tactical Mitigations

Based on the techniques used by this family, consider the following defensive strategies:

MITRE D3FEND™ Defensive Countermeasures

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

D3FEND IDCountermeasure NameTacticCountered ATT&CKDefensive Guidance
D3-PIADProcess Injection Analysis & DetectionDetectT1055Monitor cross-process thread creation (CreateRemoteThread) and asynchronous procedure calls (QueueUserAPC).
D3-OAAOutbound Network Traffic FilteringIsolateT1090Restrict outbound connections to known external proxy relays and enforce enterprise forward proxy authentication.
D3-NTINetwork Traffic InspectionDetectT1105Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols.
D3-RPMRegistry Persistence MonitoringDetectT1547.001Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management.
D3-STASecurity Tool Anti-Tamper EnforcementHardenT1562.001Block unauthorized modification of antivirus registry flags and prevent stopping security agent services.

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.

Delivery vectors

Persistence mechanisms

SIEM / EDR Ingestion: Need these reference indicators for threat hunting?

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_BUNITU_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Bunitu"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "bunitu" ascii wide nocase
        $s2 = "trojan:win32/bunitu" ascii wide nocase
        $s3 = "trojan.win32.bunitu" ascii wide nocase
        $s4 = "trojan.bunitu" ascii wide nocase
        $s5 = "win32/bunitu" ascii wide nocase
        $s6 = "bunitu proxy bot" 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 - Bunitu (Trojan) Execution & Triage
id: 449523f4-861d-56ef-81df-092dc981fdc4
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Bunitu 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/bunitu
- 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.t1090_001
- attack.t1547_001
- attack.t1071_001
- attack.t1562_001
- attack.t1082
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_BUNITU_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Bunitu 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 = "bunitu" 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
}
SOC & SIEM Rule Downloads: ⬇ Download YARA Rule (.yar) ⬇ Download Sigma Rule (YAML) ⬇ Download Sigma Rule (JSON) ⚙ Threat Profile API (JSON)

Containment & Response Steps

Home Users: If you suspect a malware infection on your personal device, disconnect from the internet immediately and run a full system scan with your antivirus software (see our TotalAV Antivirus & Security Support Guide). The steps below are intended for IT professionals responding to enterprise incidents.

Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.

  1. Immediately isolate the endpoint from the network to halt the relaying of malicious proxy traffic and prevent IP blacklisting.
  2. Enforce strict egress filtering at the corporate firewall, dropping all outbound connections on non-standard ports until the infection is cleared.
  3. Capture a forensic memory image to extract the active Bunitu configuration and identify the specific C2 servers coordinating the proxy network.
  4. Assume the endpoint is compromised; a clean OS rebuild is recommended to ensure all Winsock hooks and rootkit components are removed.

What to Avoid

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

  1. Do not ignore the infection as simply 'high bandwidth usage'; your infrastructure is actively participating in cyber attacks.
  2. Avoid relying solely on file deletion; the networking hooks must be cleared from memory.

References & External Analysis

Frequently Asked Questions

What is Trojan:Win32/Bunitu?

Bunitu is a proxy botnet trojan that turns infected Windows computers into residential proxy exit nodes for cybercriminals.

Why do attackers convert infected machines into proxy servers?

Residential IP addresses have high reputation scores, allowing attackers to bypass fraud filters and geo-restrictions.

How was Bunitu primarily distributed?

Through web exploit kits (Angler, Neutrino), drive-by compromise, and trojanized freeware software.

What protocols are supported by the Bunitu proxy engine?

It supports both HTTP and SOCKS4/SOCKS5 reverse proxy tunneling.

How can network administrators detect and remove Bunitu?

Monitor for anomalous outbound traffic on non-standard ports, isolate the infected system, and remove the startup registry keys.

What are the main symptoms of a Bunitu infection?

Symptoms of Bunitu 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 Bunitu 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.

Need help with an active incident? Published by the SystemHelpdesk Threat Intelligence Team.

Machine-readable

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