{
  "family": "joke",
  "sample_count": 9,
  "category": "advanced_threat",
  "description": "Joke:Win32/Joke (or generic **Joke Program** heuristics) represents a classification for software that is technically non-destructive but is designed to startle, annoy, or prank the user. These programs simulate severe system failures, such as fake Blue Screens of Death (BSOD), making the mouse cursor run away from the user, or uncontrollably opening and closing the CD-ROM drive. While not technically malware, they are heavily flagged by security vendors due to the massive disruption they cause in enterprise environments.<br><br><b>Understanding Joke Programs</b><br>To an end-user, a Joke program is often terrifying, leading them to believe their computer is completely broken or heavily infected. For a security analyst or IT helpdesk, these programs are a massive nuisance that wastes valuable incident response time. While most are sent harmlessly among coworkers, advanced threat actors sometimes deploy Joke programs during a real breach as a diversionary tactic ('smokescreen') to overwhelm the SOC while data exfiltration occurs elsewhere.<br><br><b>Execution and Disruption Mechanics</b><br>Joke programs are usually executed manually by a user who was tricked into downloading a file (e.g., `funny_game.exe`) (`T1204.002`). They do not typically possess self-propagation capabilities or C2 channels. Upon execution, they utilize standard Windows APIs to disrupt the UI (`T1562`). For example, they might use the `SetCursorPos` API to constantly move the mouse, or draw a full-screen image of a BSOD over the desktop, disabling task manager access to prevent the user from closing the application easily.<br><br><b>Indicators of Compromise & Impact</b><br>The primary impact is severe productivity loss and a flooded IT helpdesk. The IoC is entirely host-based: a highly visible, disruptive process running on the desktop. EDR logs will flag the execution of an unknown, unsigned binary from a user-writable directory (like `%Downloads%` or `%Temp%`). There is rarely any anomalous network traffic associated with Joke programs.",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [],
  "enrichment_level": "expert-seo",
  "faq": [
    {
      "@type": "Question",
      "name": "What is Joke and what threat category does it belong to?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Joke is classified as a Advanced Threat. 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 Joke establish persistence and evade defensive controls?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Joke 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 Joke compromise?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Security teams responding to Joke 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 lateral movement and credential access tactics does Joke leverage in enterprise intrusions?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Joke frequently utilizes privileged account harvesting techniques such as LSASS memory dumping, Kerberoasting, and token impersonation to escalate privileges. Once administrative credentials are acquired, it pivots across the victim network utilizing living-off-the-land binaries (LOLBins) such as WMI, PowerShell remoting, and PsExec, or abuses remote desktop protocols (RDP) to reach critical internal repositories and domain controllers."
      }
    },
    {
      "@type": "Question",
      "name": "How does Joke maintain covert communications and evade perimeter network monitoring?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Joke often relies on multi-stage command and control (C2) architectures utilizing encrypted protocols over standard web ports (HTTPS/443 or DNS tunneling) to blend in with legitimate enterprise network traffic. Many variants incorporate proxy networks, domain fronting, or cloud services (such as Microsoft Graph API, Google Drive, or Telegram) to masquerade C2 channels, bypassing traditional signature-based egress filtering."
      }
    }
  ],
  "faq_count": 5,
  "mitre_attack": [
    "T1204.002",
    "T1562"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-06-09",
  "mitre_attack_detail": [
    {
      "id": "T1204.002",
      "name": "User Execution: Malicious File",
      "tactic": "Execution"
    },
    {
      "id": "T1562",
      "name": "Impair Defenses (Disabling Task Manager / UI manipulation)",
      "tactic": "Defense Evasion"
    }
  ],
  "containment_steps": [
    "If the UI is completely locked (e.g., a fake BSOD), restart the computer in Safe Mode to prevent the Joke program from launching.",
    "Use EDR or the Windows Task Manager (if accessible) to identify and terminate the anomalous executable causing the disruption.",
    "Locate and delete the executable file, usually found in the user's Downloads or Temp directory.",
    "Investigate the source of the file to determine if it was an internal prank or an external download, and educate the user accordingly."
  ],
  "what_to_avoid": [
    "Do not assume a major incident has occurred before verifying the nature of the disruption; fake BSODs are common scare tactics.",
    "Avoid ignoring the incident entirely; investigate *why* the user executed an unknown, untrusted binary on a corporate machine."
  ],
  "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 Server 2022",
    "Windows Server 2019"
  ]
}