Opencandy

Overview

OpenCandy (cataloged by Microsoft Defender as Adware:Win32/OpenCandy and PUA:Win32/CandyOpen) is a historic, commercial adware monetization framework and Potentially Unwanted Application (PUA) module active since 2008. Created by OpenCandy Inc., the software was designed as a dynamic third-party recommendation library (DLL) integrated into installation wizards for popular freeware products (such as DAEMON Tools, PDFCreator, CCleaner, and WinSCP). Upon executing a bundled installer, the OpenCandy module initiates background telemetry requests to affiliate servers (api.opencandy.com), gathering geolocation, operating system version, and system language parameters. The installer dynamically generates deceptive installation screens—often using pre-selected checkboxes or misleading multi-button prompts—to install sponsored partner toolbars, third-party browsers, and search hijackers without clear affirmative consent. While technically promoting commercial software, the aggressive Pay-Per-Install (PPI) monetization model, privacy harvesting, and residual browser modifications led major security vendors to flag OpenCandy as a persistent adware threat.

Known aliases

Threat reports may refer to this family under multiple names:

• Adware:Win32/OpenCandy
• PUA:Win32/CandyOpen
• OpenCandy
• Adware.OpenCandy
• Win32/OpenCandy

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: Early Pay-Per-Install Sdks

Known Derivatives & Downstream Variants: Opencandy Dll · Candyopen Framework

MITRE ATT&CK Techniques

Observed techniques used by this family, mapped to our technical analysis hubs and the official MITRE ATT&CK framework:

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):

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.

• 0b1c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c
• 1c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d

Delivery vectors

• Bundled inside third-party freeware installers and utility downloads
• Deceptive Pay-Per-Install monetization wrappers

Persistence mechanisms

• HKCU\Software\Microsoft\Windows\CurrentVersion\Run\OpenCandyUpdate
• Browser extension registration keys

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:

rule MALWARE_WIN_OPENCANDY_T1_ARTIFACT {
    meta:
        description = "Tier 1 Primitive Artifact: Raw string matches for Opencandy"
        tier = "T1 - Primitive Artifact"
        confidence = "Low-Medium (Fast Triage)"
        author = "SystemHelpdesk Threat Research Desk"
        date = "2026-10-14"
    strings:
        $s1 = "opencandy" ascii wide nocase
        $s2 = "adware:win32/opencandy" ascii wide nocase
        $s3 = "pua:win32/candyopen" ascii wide nocase
        $s4 = "opencandy" ascii wide nocase
        $s5 = "adware.opencandy" ascii wide nocase
        $s6 = "win32/opencandy" ascii wide nocase
    condition:
        uint16(0) == 0x5a4d and any of them
}

title: SystemHelpDesk Detection - Opencandy (Adware) Execution & Triage
id: 1db0836a-bffc-511d-bc91-3ac26dea9819
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
  with the Opencandy 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/opencandy
- 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.adware
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1189
- attack.t1204_002
- attack.t1105
- attack.t1176
- attack.t1112
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

rule MALWARE_WIN_OPENCANDY_T3_ATTRIBUTION {
    meta:
        description = "Tier 3 Attribution Fingerprint: Heuristic detection for Opencandy 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 = "opencandy" 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.

1. Identify and uninstall the parent freeware installer that introduced the OpenCandy bundleware library.
2. Deploy an enterprise adware cleaner (e.g., Malwarebytes) to locate and remove residual registry keys and staging DLLs.
3. Audit web browser extensions and default search engine settings across Chrome, Edge, and Firefox, restoring standard defaults.
4. Enforce application control policies to block unsigned installers or software bundles utilizing third-party advertising SDKs.

What to Avoid

Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.

1. Do not rapidly click 'Express' or 'Next' during freeware setup routines, as opt-outs for sponsored software are buried in custom menus.
2. Avoid downloading freeware utilities from third-party repackaged mirror websites that inject aggressive adware SDKs.

References & External Analysis

• Microsoft Defender Threat Encyclopedia - Adware:Win32/OpenCandy
• Huntress Threat Library - OpenCandy / CandyOpen Analysis
• Search "opencandy" on VirusTotal (External Analysis)
• Search "opencandy" on Any.Run (Sandbox Sandbox)
• Search "opencandy" on MalwareBazaar (Malware Samples)

Frequently Asked Questions

Related Threats (Category: Adware)

Explore other documented threats in the same operational category:

• Shyape
• Shipup
• Softpulse
• Trymedia
• Elex
• Browsefox
• Toggle
• Websearch

Machine-readable

Get this profile as JSON: https://malware-families-catalog.systemhelpdesk.com/api/opencandy.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.