{
  "family": "sillyfdc",
  "sample_count": 2,
  "category": "advanced_threat",
  "description": "Worm:Win32/Sillyfdc is a prolific and persistent worm designed to propagate rapidly across networks by infecting removable drives (USB flash drives). First emerging in the mid-2000s, variants of Sillyfdc remain highly prevalent in environments that rely heavily on physical media transfer, such as industrial control systems (ICS), educational institutions, and offline networks. Its primary mechanism relies on abusing the Windows Autorun/Autoplay functionality (`T1091`).<br><br><b>Understanding Sillyfdc (USB Worms)</b><br>To an end-user, the infection is often noticed when their USB drive suddenly contains `.lnk` (shortcut) files instead of their actual folders, or when the drive behaves erratically. For a security administrator, a Sillyfdc outbreak is a nightmare, capable of bridging air-gapped networks and causing massive, noisy file modifications across the enterprise.<br><br><b>Execution and Propagation Mechanics</b><br>Sillyfdc spreads via Replication Through Removable Media (`T1091`). When an infected USB drive is plugged into a Windows machine, the worm executes (historically via `autorun.inf`, or modernly by tricking the user into clicking a malicious shortcut). Once on the host, it establishes persistence by copying itself to `%SystemRoot%` or `%AppData%` and creating a Registry Run key (`T1547.001`). The worm then monitors the system for new USB drives. When a clean drive is inserted, Sillyfdc immediately copies its executable to the drive, hides all legitimate user folders on the drive (`T1564.001`), and creates malicious `.lnk` shortcuts with the exact names of the hidden folders. When a user on a *different* machine clicks the shortcut to access their files, they inadvertently execute the worm first, spreading the infection.<br><br><b>Indicators of Compromise & Impact</b><br>The impact is widespread infection, potential data loss (if the worm malfunctions or includes a destructive payload), and a massive drain on IT resources to clean the environment. Host-based IoCs include the presence of hidden folders on USB drives replaced by `.lnk` files pointing to a hidden executable (e.g., `cmd.exe /c start hidden_worm.exe`). EDR alerts will trigger on executables launching from the root directory of removable media or making anomalous modifications to `autorun.inf`.",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [],
  "enrichment_level": "expert-seo",
  "faq": [
    {
      "@type": "Question",
      "name": "What is Sillyfdc and what threat category does it belong to?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Sillyfdc 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 Sillyfdc establish persistence and evade defensive controls?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Sillyfdc 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 Sillyfdc compromise?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Security teams responding to Sillyfdc 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 Sillyfdc leverage in enterprise intrusions?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Sillyfdc 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 Sillyfdc maintain covert communications and evade perimeter network monitoring?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Sillyfdc 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": [
    "T1547.001",
    "T1564.001",
    "T1091"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-06-09",
  "mitre_attack_detail": [
    {
      "id": "T1091",
      "name": "Replication Through Removable Media (The core propagation mechanism)",
      "tactic": "Lateral Movement"
    },
    {
      "id": "T1564.001",
      "name": "Hide Artifacts: Hidden Files and Directories (Hiding user files and the worm executable on the USB)",
      "tactic": "Defense Evasion"
    },
    {
      "id": "T1547.001",
      "name": "Boot or Logon Autostart Execution (Persistence on the host machine)",
      "tactic": "Persistence"
    }
  ],
  "containment_steps": [
    "Implement an enterprise-wide Group Policy Object (GPO) to completely disable Autoplay/Autorun for all removable media.",
    "Use EDR to isolate all infected machines and identify the specific executable name the worm is currently using.",
    "Instruct users to enable 'Show hidden files and folders' in Windows Explorer to identify if their USB drives have been compromised.",
    "Run a specialized script or AV tool across the fleet to delete the malicious `.lnk` files and unhide the legitimate user directories on USB drives."
  ],
  "what_to_avoid": [
    "Do not click on folders on a USB drive if they display a 'shortcut' arrow icon; these are almost certainly malicious links created by the worm.",
    "Avoid relying solely on host-based AV; if USB usage policies are not strictly enforced, the worm will continue to re-introduce itself."
  ],
  "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"
  ]
}