{
  "family": "feebs",
  "sample_count": 1,
  "category": "trojan",
  "description": "<h3>Executive Summary</h3>\nFeebs is a highly destructive and self-replicating polymorphic Worm and Trojan that gained significant notoriety in the mid-2000s. Designed to rapidly propagate via mass-mailing techniques and peer-to-peer networks, Feebs severely degrades network performance and compromises endpoint security. Its defining characteristic is its aggressive polymorphism, constantly altering its code structure to evade traditional, signature-based antivirus detection.\n\n<h3>Propagation and Execution Lifecycle</h3>\nFeebs relies on aggressive, largely automated propagation techniques:\n<ul>\n<li><strong>Mass-Mailing (Worm Capability):</strong> Upon execution, Feebs harvests email addresses from the victim's local files (address books, cached web pages, document files). It then utilizes its own built-in SMTP engine to spam copies of itself to those addresses, spoofing the \"From\" address to increase the likelihood the recipient will open the malicious attachment (often a ZIP file containing a disguised executable or `.scr` file).</li>\n<li><strong>Polymorphism:</strong> Every time Feebs sends a copy of itself, it alters its internal code structure and encrypts its payload differently. This ensures that the file hash is completely unique for every single victim, rendering static AV signatures useless.</li>\n<li><strong>System Sabotage:</strong> Once active, Feebs attempts to disable local antivirus and firewall software, modifies the Windows `HOSTS` file to block access to security vendor websites, and drops secondary trojans or backdoors to allow the attacker persistent access.</li>\n</ul>\n\n<h3>Threat Assessment</h3>\nA Feebs infection is a major security incident. Its mass-mailing behavior can rapidly overwhelm corporate mail servers, resulting in denial-of-service conditions and severe IP reputation damage (getting the organization blacklisted by spam filters). Furthermore, its ability to disable local security controls leaves the endpoint vulnerable to further exploitation.\n\n<h3>Eradication and Incident Response</h3>\n<ul>\n<li><strong>Aggressive Network Isolation:</strong> Infected machines must be immediately disconnected from the LAN to halt the outbound spam traffic and prevent lateral spread via network shares.</li>\n<li><strong>Mail Gateway Filtering:</strong> Implement aggressive filtering at the Secure Email Gateway (SEG) to block inbound and outbound executable attachments, even within ZIP archives.</li>\n<li><strong>Behavioral EDR:</strong> Because Feebs is highly polymorphic, defenses must rely on heuristic and behavioral EDR tools that detect its anomalous actions (e.g., an unknown process attempting to establish SMTP connections or modifying the `HOSTS` file).</li>\n</ul>",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [
    "Worm.Win32.Feebs",
    "W32/Feebs",
    "Trojan.Feebs"
  ],
  "enrichment_level": "expert-seo",
  "faq": [
    {
      "@type": "Question",
      "name": "What is Feebs and what threat category does it belong to?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Feebs is classified as a Trojan. Documented across security telemetry, it is engineered to execute unauthorized operations, establish persistent footholds on target endpoints, and facilitate malicious campaigns targeting enterprise and individual environments."
      }
    },
    {
      "@type": "Question",
      "name": "How does Feebs establish persistence and evade defensive controls?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Feebs typically establishes persistence through registry run keys, scheduled tasks, or service installations, while evading signature-based antivirus solutions through code obfuscation, memory injection, or anti-analysis sandbox checks."
      }
    },
    {
      "@type": "Question",
      "name": "What are the essential incident response steps for mitigating a Feebs compromise?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Security teams responding to Feebs should immediately isolate affected endpoints from the network, perform memory triage to capture volatile forensic artifacts, audit registry and startup persistence mechanisms, revoke exposed user credentials, and restore systems from verified, clean backups."
      }
    },
    {
      "@type": "Question",
      "name": "What secondary payloads and staging behaviors are commonly associated with Worm.Win32.Feebs?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Worm.Win32.Feebs frequently operates as a loader or dropper designed to establish a foothold before downloading and executing secondary high-impact malware payloads. Depending on the threat actor's objectives, these dropped modules can range from ransomware and banking injects to modular infostealers and remote management backdoors."
      }
    },
    {
      "@type": "Question",
      "name": "How can security operations teams effectively detect and hunt for Worm.Win32.Feebs across enterprise endpoints?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Defenders should hunt for Worm.Win32.Feebs by deploying behavioral endpoint detection and response (EDR) rules that monitor suspicious process spawning (such as cmd.exe or powershell.exe spawned from office documents or temporary directories), anomalous outbound network connections from non-browser binaries, and unauthorized modifications to Windows Run keys and scheduled task registries."
      }
    }
  ],
  "faq_count": 5,
  "mitre_attack": [
    "T1566.001",
    "T1562.001",
    "T1562.004"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-10-15",
  "type": "Worm",
  "target_industries": [
    "Global / Opportunistic"
  ],
  "motivation": "Opportunistic",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ],
  "attack_stage": [
    "execution",
    "persistence"
  ],
  "ecosystem": [
    "windows_pe"
  ],
  "is_emerging": false,
  "mitre_attack_detail": [
    {
      "id": "T1566.001",
      "name": "Phishing: Spearphishing Attachment",
      "tactic": "Initial Access"
    },
    {
      "id": "T1562.001",
      "name": "Impair Defenses: Disable or Modify Tools",
      "tactic": "Defense Evasion"
    },
    {
      "id": "T1562.004",
      "name": "Impair Defenses: Disable or Modify System Firewall (Closing SMB ports to protect its host from competing malware)",
      "tactic": "Defense Evasion"
    }
  ],
  "containment_steps": [
    "Sever network connectivity for the flagged endpoint to terminate persistent command-and-control (C2) communication channels and stop Feebs from retrieving secondary stage payloads.",
    "Capture process memory triage to detect and terminate malicious threads injected by Feebs into legitimate system processes such as explorer.exe or svchost.exe.",
    "Audit Windows Registry Run keys (HKCU\\Software\\Microsoft\\Windows\\CurrentVersion\\Run) and Task Scheduler entries to locate and purge Feebs persistence hooks.",
    "Deploy updated enterprise EDR detection signatures and conduct an out-of-band endpoint scan to isolate dropped binaries and staged payloads.",
    "Rotate all credentials, domain user passwords, and session cookies active on the system during the Feebs execution timeframe."
  ],
  "what_to_avoid": [
    "Do not assume the incident is resolved simply because an antivirus tool removed the initial Feebs dropper; always verify that secondary payloads and persistence hooks have been eradicated.",
    "Avoid logging in with Domain Admin or privileged credentials on a machine suspected of running Feebs until memory triage is complete.",
    "Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution."
  ],
  "target_platforms": [
    "Windows 11",
    "Windows 10",
    "Windows 7"
  ]
}