Candyopen
Table of Contents
Overview
Candyopen (classified in antivirus detection telemetry under designations including Trojan:Win32/Candyopen, Trojan.Win32.Candyopen, and Win32/Candyopen) is a multi-stage trojan engineered to disguise itself as legitimate software, execute unauthorized commands, and coordinate with external command-and-control infrastructure. Disseminated across enterprise networks and consumer workstations via social engineering, phishing attachments, malicious drive-by downloads, or weaponized software cracks, Candyopen executes an initial reconnaissance phase upon system ingress. The binary evaluates host privileges, detects active hypervisors and sandbox environments to evade behavioral analysis, and establishes resilient autostart persistence by configuring registry keys under HKCU\Software\Microsoft\Windows\CurrentVersion\Run or registering background Windows services. Operational mechanics characteristic of this family include deceptive executable masquerading, registry run key autostart, system telemetry gathering, and remote C2 beaconing. Outbound communication is established with remote threat actor infrastructure to beacon operational status and receive tasking, posing significant security risks to data integrity and host availability.
Known aliases
Threat reports may refer to this family under multiple names:
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 (Deceptive software bundling) | Initial Access | ATT&CK ↗ |
T1204.002 | User Execution: Malicious File (User running the wrapper) | Execution | ATT&CK ↗ |
T1036 | Masquerading (Disguising adware consent forms) | Defense Evasion | ATT&CK ↗ |
T1562.001 | Impair Defenses: Disable or Modify Tools (Browser hijacking) | Defense Evasion | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1036: Monitor for executable files running from unusual paths or with deceptive names. Use EDR to detect process masquerading.
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-PMA | Process Lineage & Masquerade Analysis | Detect | T1036 | Verify digital code-signing signatures and compare executable paths against known Windows binaries. |
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-STA | Security Tool Anti-Tamper Enforcement | Harden | T1562.001 | Block unauthorized modification of antivirus registry flags and prevent stopping security agent services. |
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_CANDYOPEN_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Candyopen"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "candyopen" ascii wide nocase
$s2 = "trojan:win32/candyopen" ascii wide nocase
$s3 = "trojan.win32.candyopen" ascii wide nocase
$s4 = "win32/candyopen" 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 - Candyopen (Trojan) Execution & Triage
id: fc3b934d-811e-508a-8c41-ff404fe1b114
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Candyopen 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/candyopen
- https://malware-families-catalog.systemhelpdesk.com/defensive/downloader-dropper-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.trojan
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1059_003
- attack.t1027
- attack.t1547_001
- attack.t1071_001
- attack.t1105
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_CANDYOPEN_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Candyopen 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 = "candyopen" 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.
- Use the Windows Control Panel to thoroughly uninstall the explicitly named adware programs that were dropped by the Candyopen wrapper.
- Run an enterprise-grade Adware/PUA removal tool (such as Malwarebytes) to strip the deep registry hooks and browser extensions left behind.
- Reset all installed web browsers (Chrome, Edge, Firefox) to their factory default settings to remove any lingering homepage or search engine hijackers.
- Review the user's internet history to identify the deceptive download portal that distributed the package, and block it via the corporate proxy.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not allow users local administrator privileges; standard users cannot typically install the system-level services required by aggressive adware bundles.
- Avoid relying solely on manual uninstallation, as PPI wrappers often drop 'watchdog' processes designed to reinstall the adware if it is removed.
References & External Analysis
- Microsoft Defender Threat Encyclopedia - Trojan:Win32/Candyopen
- Kaspersky Threat Intelligence - Trojan.Win32.Candyopen
- MITRE ATT&CK - Enterprise Techniques
- Search "candyopen" on VirusTotal (External Analysis)
- Search "candyopen" on Any.Run (Sandbox Sandbox)
- Search "candyopen" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Trojan:Win32/Candyopen?
Candyopen is a trojan threat designed to infiltrate Windows systems and execute unauthorized operations without user consent.
How does Candyopen compromise target systems?
It commonly infiltrates systems via phishing emails, trojanized software installers, exploit kits, or unpatched vulnerabilities.
What persistence mechanisms does Candyopen utilize?
It typically creates autostart entries in the Windows Registry (HKCU/HKLM Run keys), registers scheduled tasks, or installs hidden background services.
What risks does Candyopen pose to an enterprise?
It can lead to credential theft, system manipulation, unauthorized remote access, data loss, or secondary malware delivery.
How can administrators detect and eliminate Candyopen?
Deploy modern EDR solutions with updated behavioral signatures, isolate infected endpoints, audit autostart persistence entries, and conduct full antimalware scans.
How do I remove Candyopen from Windows?
Manual removal of Candyopen 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.
What are the main symptoms of a Candyopen infection?
Symptoms of Candyopen 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 Trojans
Want to prevent Candyopen and similar threats from compromising your organization? Read our comprehensive defensive guide: Banking Trojan Protection for Businesses.
📣 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/candyopen.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.