{
  "family": "iwin",
  "sample_count": 1,
  "category": "advanced_threat",
  "description": "<h3>Executive Summary</h3>\niWin (often detected as Adware.iWin or PUP.iWin) is a widespread family of Adware and Potentially Unwanted Programs (PUPs). It is historically associated with the bundled installation of \"free\" casual games from the iWin portal. While the games themselves may function, the bundled software aggressively monetizes the user's web browsing activity by injecting intrusive advertisements and altering browser configurations, degrading system performance and user privacy.\n\n<h3>Distribution and Technical Behavior</h3>\niWin adware is almost exclusively distributed via deceptive software bundling. When a user downloads a free game from the iWin portal or affiliated third-party sites, the installer uses pre-checked boxes and confusing EULAs to silently install secondary adware components.\n\nOnce executed, the iWin adware integrates with the operating system and web browsers. Its core behaviors include:\n<ul>\n<li><strong>Browser Hijacking:</strong> The adware forces changes to the browser's default search engine, homepage, and new tab settings. All search traffic is redirected through an affiliate-linked search portal (often heavily branded) controlled by the adware operators to generate illicit ad revenue.</li>\n<li><strong>Advertisement Injection:</strong> It installs browser extensions or local proxies to overlay legitimate websites with pop-ups, pop-unders, banner ads, and sponsored in-text hyperlinks, severely disrupting the user experience.</li>\n<li><strong>Data Harvesting:</strong> The adware continuously tracks the user's browsing history, search queries, and clickstreams, transmitting this telemetry to remote servers to serve highly targeted advertisements.</li>\n</ul>\n\n<h3>Risk Assessment</h3>\nWhile iWin adware does not actively encrypt files or steal banking credentials, it introduces significant operational friction in enterprise environments. Furthermore, the injected advertisements are frequently served by low-reputation ad networks, increasing the likelihood of \"malvertising\" attacks that can lead to severe secondary infections.\n\n<h3>Mitigation and Removal Strategies</h3>\n<ul>\n<li><strong>Endpoint Scanning:</strong> Utilize a reputable enterprise-grade anti-malware solution to perform a deep system scan, targeting the iWin executables, hidden scheduled tasks, and persistent registry keys used to maintain its hold on the browser.</li>\n<li><strong>Browser Remediation:</strong> Manually inspect and remove any unknown or unauthorized extensions from all installed web browsers. Perform a complete factory reset of the browsers to clear the hijacked proxy and search settings.</li>\n<li><strong>Application Control:</strong> Enforce strict application whitelisting policies to prevent standard users from downloading and executing unapproved casual games and their associated, untrusted software installers.</li>\n</ul>",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [
    "Adware.iWin",
    "PUP.iWin",
    "BrowserModifier:Win32/iWin"
  ],
  "enrichment_level": "expert-seo",
  "faq": [
    {
      "@type": "Question",
      "name": "What is Iwin and what threat category does it belong to?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Iwin 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 Iwin establish persistence and evade defensive controls?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Iwin 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 Iwin compromise?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Security teams responding to Iwin 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 Adware.iWin leverage in enterprise intrusions?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Adware.iWin 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 Adware.iWin maintain covert communications and evade perimeter network monitoring?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Adware.iWin 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": [
    "T1566.002",
    "T1176",
    "T1112"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-10-15",
  "type": "Adware",
  "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.002",
      "name": "Phishing: Spearphishing Link (Social engineering to force the user to download the tool)",
      "tactic": "Initial Access"
    },
    {
      "id": "T1176",
      "name": "Browser Extensions",
      "tactic": "Persistence"
    },
    {
      "id": "T1112",
      "name": "Modify Registry",
      "tactic": "Defense Evasion"
    }
  ],
  "containment_steps": [
    "Enforce forensic network isolation on all suspected endpoints while maintaining an out-of-band telemetry conduit to capture live Iwin adversary activity.",
    "Perform full memory dumps across identified staging nodes to extract memory-only implants, kernel rootkit hooks, and decrypted Iwin 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 Iwin.",
    "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 Iwin operators."
  ],
  "what_to_avoid": [
    "Do not assume the incident is resolved simply because an antivirus tool removed the initial Iwin 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 Iwin 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"
  ]
}