{
  "family": "krepper",
  "sample_count": 3,
  "category": "trojan",
  "description": "Worm:Win32/Krepper is a highly virulent, self-replicating network worm designed to spread rapidly across vulnerable corporate environments. Unlike a trojan that relies on user interaction (like clicking an email link), Krepper actively scans the local network and the internet to find unpatched machines, exploiting known vulnerabilities or utilizing weak credentials to automatically infect new hosts and expand its botnet.<br><br><b>Understanding Krepper (Network Worms)</b><br>To an end-user, a Krepper infection might cause the computer to become sluggish or completely unresponsive, as the worm consumes all available CPU and network bandwidth trying to replicate. For a network administrator, Krepper is an immediate crisis. It can saturate internal network links (causing Denial of Service - `T1498`), overwhelm firewalls with outbound scanning traffic (`T1046`), and rapidly compromise all unpatched servers in a matter of minutes.<br><br><b>Execution and Propagation Mechanics</b><br>Krepper achieves Initial Access through the exploitation of remote services (`T1190`), often targeting legacy vulnerabilities like MS08-067 (similar to Conficker) or exposed SMB/RDP ports with weak passwords. Once it compromises a host, it drops its executable into the Windows system directory and establishes persistence via the Registry Run keys (`T1547.001`). It then generates random IP addresses and aggressively scans them for the same vulnerability (`T1046`), attempting to push its payload (`T1105`) to any responsive targets. Some variants also attempt to propagate via removable USB drives (`T1091`) by creating malicious `autorun.inf` files.<br><br><b>Indicators of Compromise & Impact</b><br>The impact is severe network disruption and widespread compromise. Network IoCs are the most prominent: an explosion of outbound traffic on specific ports (e.g., 445, 135) originating from infected internal hosts. Host-based IoCs include the presence of unexpectedly named executables in `C:\\Windows\\System32`, unauthorized modifications to the Windows Firewall, and the creation of hidden `autorun.inf` files on attached storage.",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [],
  "enrichment_level": "expert-seo",
  "faq": [
    {
      "@type": "Question",
      "name": "What is Krepper and what threat category does it belong to?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Krepper 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 Krepper establish persistence and evade defensive controls?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Krepper 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 Krepper compromise?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Security teams responding to Krepper 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 Krepper?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Krepper 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 Krepper across enterprise endpoints?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Defenders should hunt for Krepper 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": [
    "T1498",
    "T1190",
    "T1046",
    "T1091"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-06-09",
  "mitre_attack_detail": [
    {
      "id": "T1190",
      "name": "Exploit Public-Facing Application (Remote Code Execution)",
      "tactic": "Initial Access"
    },
    {
      "id": "T1046",
      "name": "Network Service Discovery (Aggressive port scanning)",
      "tactic": "Discovery"
    },
    {
      "id": "T1091",
      "name": "Replication Through Removable Media (USB Autorun)",
      "tactic": "Lateral Movement"
    },
    {
      "id": "T1498",
      "name": "Network Denial of Service (Traffic saturation during propagation)",
      "tactic": "Impact"
    }
  ],
  "containment_steps": [
    "Immediately segregate the infected network segments using VLAN ACLs or internal firewalls to stop the worm from spreading to critical infrastructure.",
    "Identify the specific vulnerability or credential set Krepper is exploiting and immediately push the corresponding patch or password reset enterprise-wide.",
    "Deploy an updated AV signature or custom EDR rule to isolate and terminate the worm's process on all affected endpoints.",
    "Disable `Autorun` globally via Group Policy to prevent USB-based propagation."
  ],
  "what_to_avoid": [
    "Do not simply clean one machine and reconnect it to an unpatched network; the worm will instantly reinfect it.",
    "Avoid performing a network-wide reboot; focus on patching and isolation first to prevent the worm from re-establishing a foothold upon startup."
  ],
  "target_industries": [
    "Global / Opportunistic"
  ],
  "motivation": "Opportunistic",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ],
  "attack_stage": [
    "execution",
    "persistence"
  ],
  "ecosystem": [
    "windows_pe"
  ],
  "is_emerging": false,
  "target_platforms": [
    "Windows 11",
    "Windows 10",
    "Windows 7"
  ]
}