{
  "family": "eicardemo",
  "sample_count": 1,
  "category": "advanced_threat",
  "description": "<h3>Executive Summary</h3>\nEICAR Demo (or the EICAR Standard Anti-Virus Test File) is **NOT MALWARE**. It is a safe, standardized, and internationally recognized 68-byte text file developed by the European Institute for Computer Antivirus Research (EICAR) and the Computer Antivirus Research Organization (CARO). Its sole purpose is to safely test and verify the operational status, detection capabilities, and alerting mechanisms of antivirus (AV) software, Endpoint Detection and Response (EDR) solutions, and network security appliances without exposing the network to actual malicious code.\n\n<h3>Technical Capabilities (Safe Testing)</h3>\nThe EICAR test file is literally a short string of printable ASCII characters (`X5O!P%@AP[4\\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*`). It contains no malicious logic, cannot self-replicate, cannot access the network, and cannot harm the system in any way.\n\nHow it functions in a security context:\n<ul>\n<li><strong>Standardized Signature:</strong> All legitimate, commercial antivirus vendors have explicitly programmed their scanning engines to recognize this specific 68-byte string as a \"virus\" for testing purposes.</li>\n<li><strong>Validation of Defense in Depth:</strong> Security administrators deploy the EICAR file in various formats (e.g., plain text, compressed in a `.zip` archive, or embedded in an email) to verify that different layers of their security stack (email gateways, web proxies, endpoint AV) are functioning and successfully blocking malicious signatures.</li>\n<li><strong>Alerting Verification:</strong> It is frequently used during incident response drills to verify that when an endpoint detects malware, the alert successfully traverses the network and appears correctly in the centralized Security Information and Event Management (SIEM) dashboard.</li>\n</ul>\n\n<h3>Threat Assessment</h3>\nThere is absolutely **ZERO THREAT** posed by the EICAR test file itself. However, if an administrator downloads the EICAR file and the local antivirus solution fails to detect it, that represents a critical security failure, indicating the AV engine is broken, disabled, or misconfigured.\n\n<h3>Incident Response and Remediation</h3>\n<ul>\n<li><strong>No Remediation Required (For the File):</strong> If the antivirus successfully detects and quarantines the EICAR file, the system is working as intended. The file can be safely deleted or left in quarantine.</li>\n<li><strong>Investigate Lack of Detection:</strong> If the EICAR file is downloaded and *not* detected, immediate IT intervention is required to troubleshoot the endpoint security software and restore its protective capabilities.</li>\n</ul>",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [
    "EICAR_Test_File",
    "Test-File.EICAR",
    "Not-A-Virus:EICAR-Test-Signature"
  ],
  "enrichment_level": "expert-seo",
  "faq": [
    {
      "@type": "Question",
      "name": "What is Eicardemo and what threat category does it belong to?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Eicardemo 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 Eicardemo establish persistence and evade defensive controls?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Eicardemo 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 Eicardemo compromise?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Security teams responding to Eicardemo 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 EICAR_Test_File leverage in enterprise intrusions?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "EICAR_Test_File 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 EICAR_Test_File maintain covert communications and evade perimeter network monitoring?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "EICAR_Test_File 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": [
    "T1059.001",
    "T1055",
    "T1071.001",
    "T1027"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-10-15",
  "type": "Test File (Non-Malicious)",
  "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": "T1059.001",
      "name": "Command and Scripting Interpreter: PowerShell (Used in infection chain)",
      "tactic": "Execution"
    },
    {
      "id": "T1055",
      "name": "Process Injection",
      "tactic": "Defense Evasion"
    },
    {
      "id": "T1071.001",
      "name": "Application Layer Protocol: Web Protocols (C2 Communication)",
      "tactic": "Command and Control"
    },
    {
      "id": "T1027",
      "name": "Obfuscated Files or Information",
      "tactic": "Defense Evasion"
    }
  ],
  "containment_steps": [
    "Enforce forensic network isolation on all suspected endpoints while maintaining an out-of-band telemetry conduit to capture live Eicardemo adversary activity.",
    "Perform full memory dumps across identified staging nodes to extract memory-only implants, kernel rootkit hooks, and decrypted Eicardemo C2 infrastructure IP/domain lists.",
    "Review Active Directory domain controller authentication logs for anomalous Kerberos ticket requests (Pass-the-Ticket, Golden Ticket) and unauthorized DCSync operations associated with Eicardemo.",
    "Block all confirmed C2 domains, dynamic DNS endpoints, and proxy IP addresses across perimeter firewalls, proxies, and DNS security gateways.",
    "Conduct an enterprise-wide sweep across surrounding subnets for secondary webshells, WMI event subscriptions, or remote execution tooling left behind by Eicardemo operators."
  ],
  "what_to_avoid": [
    "Do not assume the incident is resolved simply because an antivirus tool removed the initial Eicardemo 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 Eicardemo 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 Server 2022",
    "Windows Server 2019"
  ]
}