Peed

Overview

Executive Summary

Infection Vector and Technical Capabilities

• Peer-to-Peer (P2P) C2 Infrastructure: Unlike traditional botnets that relied on a central C2 server (which could be easily taken down by law enforcement), Peed utilizes a decentralized P2P protocol (often Overnet). Infected machines communicate directly with each other to receive commands and updates, making the botnet incredibly difficult to dismantle.
• Aggressive Rootkit Evasion: Peed employs aggressive rootkit techniques (often utilizing `wincom32.sys`) to hide its files, registry keys, and active network connections from the user and traditional antivirus software. It actively attempts to disable local security services.
• Monetization (Spam and DDoS): The primary function of an infected node is to silently send massive volumes of spam (often pump-and-dump stock scams or pharmaceutical ads) or to participate in coordinated DDoS attacks against specific targets for extortion.

Threat Assessment

Remediation and Eradication

• Network Containment: Immediately isolate the infected machine from the network. Because the botnet relies on P2P communications, blocking standard P2P ports and monitoring for high volumes of outbound SMTP (Port 25) traffic is critical.
• Rootkit Removal (Bare-Metal Restore): Because Peed utilizes kernel-level rootkits, manual removal is highly unreliable. The only secure remediation is to completely format the hard drive and reinstall the operating system from a trusted image.
• Spam Blacklist Monitoring: If an infected machine successfully sent out spam, the organization's public IP address may be added to global DNS-based Blackhole Lists (DNSBLs), disrupting legitimate corporate email delivery.

Known aliases

Threat reports may refer to this family under multiple names:

• Trojan.Peacomm
• Worm.Storm
• Win32/Peed

MITRE ATT&CK Techniques

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

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_PEED_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Peed"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "peed" ascii wide nocase
        $s2 = "trojan.peacomm" ascii wide nocase
        $s3 = "worm.storm" ascii wide nocase
        $s4 = "win32/peed" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Peed (Advanced Threat) Execution & Triage
id: 4370fc4f-8086-5671-a3ed-5d8a24970255
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Peed malware family. Detects proxy execution, reflective DLL loading, and
  remote command injection associated with modular enterprise backdoors.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/peed
- https://malware-families-catalog.systemhelpdesk.com/defensive/backdoor-rat-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.advanced-threat
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1090_002
- attack.t1014
- attack.t1498
- attack.t1568
logsource:
  category: process_creation
  product: windows
detection:
  selection_process:
    Image|endswith:
    - \powershell.exe
    - \cmd.exe
    - \rundll32.exe
    - \regsvr32.exe
    CommandLine|contains:
    - DownloadString
    - IEX(
    - '/s /n /u /i:'
    - sc create
    - start-process
  condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: high

rule MALWARE_WIN_PEED_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Peed 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 = "peed" 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. Enforce forensic network isolation on all suspected endpoints while maintaining an out-of-band telemetry conduit to capture live Peed adversary activity.
2. Perform full memory dumps across identified staging nodes to extract memory-only implants, kernel rootkit hooks, and decrypted Peed C2 infrastructure IP/domain lists.
3. Review Active Directory domain controller authentication logs for anomalous Kerberos ticket requests (Pass-the-Ticket, Golden Ticket) and unauthorized DCSync operations associated with Peed.
4. Block all confirmed C2 domains, dynamic DNS endpoints, and proxy IP addresses across perimeter firewalls, proxies, and DNS security gateways.
5. Conduct an enterprise-wide sweep across surrounding subnets for secondary webshells, WMI event subscriptions, or remote execution tooling left behind by Peed operators.

What to Avoid

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

1. Do not assume the incident is resolved simply because an antivirus tool removed the initial Peed dropper; always verify that secondary payloads and persistence hooks have been eradicated.
2. Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Peed until memory triage is complete.
3. Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.

References & External Analysis

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

Frequently Asked Questions

Related Threats (Category: Advanced Threat)

Explore other documented threats in the same operational category:

• Nhopro
• Lineage
• Qqspy
• Kaymundler
• Shenzhen
• Cntads
• Wintaskad
• Somoto

Machine-readable

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