Icloader
Table of Contents
Overview
ICLoader (identified across vendor detection engines as PUA:Win32/ICLoader, Trojan:Win32/ICLoader, and PUP.Optional.InstallCore) is an aggressive software bundler and pay-per-install (PPI) loader linked to the InstallCore distribution network and analyzed by Microsoft Defender and Malwarebytes. Operating primarily through deceptive software distribution sites, ICLoader disguises itself as an official setup wizard for freeware applications, utility drivers, and media converters. Upon execution, the loader contacts central advertising servers to dynamically fetch an installer configuration manifest containing secondary promotional applications. Utilizing deceptive installation dialogs with pre-checked consent boxes and obscure rejection prompts, ICLoader downloads and executes unwanted third-party tools, browser extensions, adware components, and system cleaners. To ensure continued execution of deployed affiliate tools, ICLoader writes persistence keys to HKCU\Software\Microsoft\Windows\CurrentVersion\Run and schedules background Windows tasks. Its operations degrade endpoint performance, alter browser security configurations, and introduce substantial attack surface exposure.
Known aliases
Threat reports may refer to this family under multiple names:
Family Pedigree & Lineage
Malware authors regularly fork and iterate upon existing codebases. Observed upstream lineage and downstream variants for this family include:
Derived From / Upstream Ancestry: Installcore_Monetization_Framework
Known Derivatives & Downstream Variants: Installcore.Gen · Icloader.Variant
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:
| Technique | Name | Tactic | Official Spec |
|---|---|---|---|
T1189 | Drive-by Compromise | Initial Access | ATT&CK ↗ |
T1105 | Ingress Tool Transfer | Command and Control | ATT&CK ↗ |
T1204.002 | User Execution: Malicious File | Execution | ATT&CK ↗ |
T1053.005 | Scheduled Task/Job: Scheduled Task | Persistence | ATT&CK ↗ |
T1547.001 | Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder | Persistence | ATT&CK ↗ |
T1112 | Modify Registry | Defense Evasion | ATT&CK ↗ |
T1562.001 | Impair Defenses: Disable or Modify Tools | Defense Evasion | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1105: Implement network intrusion detection systems (NIDS) and host-based firewalls to block unauthorized inbound or outbound file transfers.
MITRE D3FEND™ Defensive Countermeasures
Defensive techniques mapped to counter the offensive tradecraft observed in this family (via the MITRE D3FEND matrix):
| D3FEND ID | Countermeasure Name | Tactic | Countered ATT&CK | Defensive Guidance |
|---|---|---|---|---|
D3-STM | Scheduled Task Creation Analysis | Detect | T1053.005 | Audit task creation targeting system and hidden service directories; verify task author credentials. |
D3-NTI | Network Traffic Inspection | Detect | T1105 | Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols. |
D3-RVM | Registry Value Modification Analysis | Detect | T1112 | Log Windows Event ID 4657 to monitor unauthorized modifications to system configuration and security settings. |
D3-RBI | Remote Browser Isolation | Isolate | T1189 | Execute untrusted web browsing sessions in disposable cloud containers to isolate drive-by exploits from local endpoints. |
D3-FEA | File Execution Analysis | Harden | T1204.002 | Enforce AppLocker and Windows Defender Application Control (WDAC) to block executable launches from temporary and user-writable directories. |
D3-RPM | Registry Persistence Monitoring | Detect | T1547.001 | Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management. |
D3-STA | Security Tool Anti-Tamper Enforcement | Harden | T1562.001 | Block unauthorized modification of antivirus registry flags and prevent stopping security agent services. |
Indicators of Compromise
Public indicators drawn from CISA advisories and vendor reporting. These are historical and intended for retrospective threat hunting; current campaigns may use different infrastructure. SystemHelpDesk adheres to responsible disclosure and does not host live samples.
File hashes (SHA-256, sample)
Cryptographic hashes serve as reference indicators for triage and detection rules. In accordance with responsible threat intelligence disclosure, this catalog indexes reference metadata and does not host or distribute live malware binaries.
2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b3c3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b3c4d
Delivery vectors
Deceptive freeware mirrors and fake software download landing pagesAffiliate marketing pay-per-install bundles disguised as media utilities
Persistence mechanisms
HKCU\Software\Microsoft\Windows\CurrentVersion\Run\ICLoaderTrayScheduled Task created via schtasks /create /tn 'ICLoaderMaintenance' /tr '%AppData%\ICLoader\icupd.exe'
Tiered Detection Rules (Cisco CAIRN Model)
Modern threat detection requires multi-layered rule engineering. We classify detections into three operational tiers based on signal fidelity:
Tier 1 Primitive Artifact Rule (Fast Triage)
Matches raw strings and file markers. Vulnerable to binary repacking and simple obfuscation.
rule MALWARE_WIN_ICLOADER_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Icloader"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "icloader" ascii wide nocase
$s2 = "pua:win32/icloader" ascii wide nocase
$s3 = "trojan:win32/icloader" ascii wide nocase
$s4 = "win32/icloader" ascii wide nocase
$s5 = "pup.optional.icloader" ascii wide nocase
$s6 = "installcore.icloader" ascii wide nocase
$s7 = "adware:win32/installcore" ascii wide nocase
condition:
uint16(0) == 0x5a4d and any of them
}
Tier 2 Behavioral Context Rule (Process Chains & Sigma)
Tracks parent-child process anomalies and suspicious scripting telemetry. Resilient against file renames.
title: SystemHelpDesk Detection - Icloader (Pua) Execution & Triage
id: 1f610ac7-a5ec-51a4-b468-6d4c452ec2fc
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Icloader malware family. Detects suspicious execution from temporary user
directories with hidden window flags and background transfer utilities.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/icloader
- https://malware-families-catalog.systemhelpdesk.com/defensive/ransomware-protection
- https://malware-families-catalog.systemhelpdesk.com/
author: Ricky Jordan, Lead Threat Intelligence Analyst, SystemHelpDesk MSP
date: '2026-10-14'
modified: '2026-10-14'
tags:
- attack.pua
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1189
- attack.t1105
- attack.t1204_002
- attack.t1053_005
- attack.t1547_001
logsource:
category: process_creation
product: windows
detection:
selection_process:
Image|endswith:
- \cmd.exe
- \powershell.exe
- \cscript.exe
- \wscript.exe
CommandLine|contains:
- AppData\Local\Temp
- -WindowStyle Hidden
- /e:jscript
- bitsadmin /transfer
condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: medium
Tier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_ICLOADER_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Icloader tradecraft"
tier = "T3 - Attribution Fingerprint"
confidence = "High (Confirmed Family Signature)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
// Core family identifier & heuristic payload signatures
$attrib_str = "icloader" ascii wide nocase
$pe_magic = "MZ" ascii
$net_marker = "http" ascii nocase
condition:
uint16(0) == 0x5a4d and ($attrib_str and $net_marker) and filesize < 15MB
}
Containment & Response Steps
Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.
- Quarantine the endpoint to halt ongoing background downloads of secondary adware packages.
- Audit the Windows Add/Remove Programs list and uninstall software installed during the exact timeframe of the ICLoader execution.
- Delete persistent scheduled tasks and registry Run keys associated with InstallCore / ICLoader.
- Run an enterprise endpoint antimalware scan to purge lingering browser hijackers and tracking adware.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not allow users to download utilities from third-party mirrors that use proprietary wrapper executables.
- Avoid relying on standard software uninstallation wizards provided by bundled applications, as they often leave persistent background updaters.
References & External Analysis
- Microsoft Defender Threat Encyclopedia - PUA:Win32/ICLoader Analysis
- Malwarebytes Labs Threat Intelligence - PUP.Optional.InstallCore / ICLoader
- NIST National Vulnerability Database - CVE-2015-1641 Overview
- Search "icloader" on VirusTotal (External Analysis)
- Search "icloader" on Any.Run (Sandbox Sandbox)
- Search "icloader" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is ICLoader?
ICLoader is a software bundler and installer loader tracked by Microsoft Defender that deploys potentially unwanted applications (PUAs) and adware alongside freeware.
How does ICLoader trick users during installation?
It uses deceptive user interface patterns such as obscured decline options and pre-selected checkboxes to bundle unwanted secondary software.
What system changes does ICLoader implement?
ICLoader modifies browser preferences, drops background adware processes into %ProgramFiles%, and sets auto-run registry keys.
Which CVE vulnerabilities have been associated with InstallCore loader droppers?
Distribution networks delivering ICLoader variants have historically utilized exploits such as CVE-2012-0158 and CVE-2015-1641.
What is the procedure to remove ICLoader from Windows?
Defenders should terminate rogue installer processes, delete startup registry entries, clear %Temp% installer folders, and run a full scan with Malwarebytes or Defender.
How do I remove the Icloader Pua from Windows?
Manual removal of Icloader is highly discouraged as it may leave persistence mechanisms intact. We recommend disconnecting the device from the internet and utilizing a professional incident response service or enterprise-grade EDR software to conduct a full forensic sweep.
Is Icloader a virus or a Pua?
Icloader is classified as a Pua. Unlike traditional viruses that infect files, modern malware like Icloader typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Icloader infection?
Symptoms of Icloader can include unexpected system slowness, unauthorized outbound network traffic to unknown IP addresses, disabled security software, and suspicious background processes running from AppData or Temp directories.
Protect Your Network Against Puas
Want to prevent Icloader and similar threats from compromising your organization? Read our comprehensive defensive guide: Think You've Been Hacked? What To Do First.
📣 Threat Intel Correction or Update?
Notice an outdated IOC, unlisted alias, or disputed attribution? Threat researchers are invited to propose an update on GitHub or contact the SystemHelpDesk research desk. All community revisions are credited in our public CHANGELOG.
Machine-readable
Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/icloader.json
Ecosystem & Interactive Environments
This profile is part of the Malware Families Catalog, a public dataset of 2,899 malware families. The catalog is also published across our ecosystem: Hugging Face, Kaggle, Zenodo, Replit, StackBlitz, CodeSandbox, and CodePen.