{ "family": "whiteclick", "sample_count": 1, "category": "ransomware", "description": "

Executive Summary

\nWhiteclick (often detected as Adware.Whiteclick or PUP.Whiteclick) is an intrusive Adware application and \"Clicker\" malware. It is designed to aggressively monetize a user's web browsing by injecting unsolicited advertisements and invisibly simulating user clicks on affiliate marketing links and banner ads, generating fraudulent revenue for the malware operators while severely degrading system performance.\n\n

Infection Vector and Technical Capabilities

\nWhiteclick is almost exclusively distributed via software bundling (pay-per-install networks). Users typically encounter this threat when downloading \"free\" software (like media converters or download managers) from untrustworthy third-party portals, where the adware is silently installed alongside the intended application.\n\nUpon execution, it deeply integrates into the operating system and web browsers:\n\n\n

Threat Assessment

\nWhile Whiteclick is not inherently destructive like ransomware, it is highly undesirable. The constant ad injection and invisible click fraud consume significant system bandwidth and resources. Furthermore, the injected advertisements often lead to deceptive technical support scams or \"malvertising\" networks that distribute severe secondary malware.\n\n

Remediation and Eradication

\n", "cta": "Published by the SystemHelpdesk team.", "aliases": [ "Adware.Whiteclick", "PUP.Whiteclick", "Trojan.Clicker" ], "enrichment_level": "expert-seo", "faq": [ { "@type": "Question", "name": "What is Whiteclick and what threat category does it belong to?", "acceptedAnswer": { "@type": "Answer", "text": "Whiteclick is classified as a Ransomware. 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 Whiteclick establish persistence and evade defensive controls?", "acceptedAnswer": { "@type": "Answer", "text": "Whiteclick 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 Whiteclick compromise?", "acceptedAnswer": { "@type": "Answer", "text": "Security teams responding to Whiteclick 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 cryptographic algorithms and file targeting techniques does Adware.Whiteclick employ during execution?", "acceptedAnswer": { "@type": "Answer", "text": "Adware.Whiteclick typically leverages hybrid cryptographic architectures combining symmetric stream or block ciphers (such as AES-256 or ChaCha20) for rapid file encryption with asymmetric algorithms (such as RSA-2048 or Curve25519) to securely protect the session keys. It aggressively targets sensitive file extensions including corporate documents, databases, virtual disks, and backups while systematically executing commands to delete Volume Shadow Copies (vssadmin delete shadows /all /quiet) and disable system recovery options." } }, { "@type": "Question", "name": "Are decryptors available for Adware.Whiteclick, and what is the recommended recovery procedure?", "acceptedAnswer": { "@type": "Answer", "text": "Decryption availability for Adware.Whiteclick depends on whether security researchers or law enforcement (such as the No More Ransom initiative) have recovered the master private keys or discovered flaws in its key generation routines. Victims should never pay the extortion demand, as payment fuels criminal operations without guaranteeing file restoration. The recommended recovery procedure entails isolating infected hosts, conducting forensic disk imaging, identifying the root access vector, and restoring validated systems from immutable offline backups." } } ], "faq_count": 5, "mitre_attack": [ "T1185", "T1176", "T1546.015" ], "cisa_advisory": null, "last_updated": "2026-10-15", "type": "Adware / Clicker", "target_industries": [ "Healthcare", "Critical Infrastructure", "Enterprise" ], "motivation": "Financial Extortion", "threat_actors": [ "Unknown / Cybercriminal" ], "target_geographies": [ "Global" ], "attack_stage": [ "defense_evasion", "impact" ], "ecosystem": [ "windows_pe" ], "is_emerging": false, "mitre_attack_detail": [ { "id": "T1185", "name": "Browser Session Hijacking (Ad injection and tracking)", "tactic": "Collection" }, { "id": "T1176", "name": "Browser Extensions", "tactic": "Persistence" }, { "id": "T1546.015", "name": "Event Triggered Execution: Component Object Model Hijacking", "tactic": "Privilege Escalation" } ], "containment_steps": [ "Immediately isolate affected host(s) from the internal network (disconnect physical Ethernet and disable Wi-Fi/Bluetooth) to prevent Whiteclick from spreading laterally or encrypting network-attached storage (NAS) and shared SMB volumes.", "Preserve volatile system memory (RAM capture) on a representative endpoint before attempting a reboot or power-down, as Whiteclick symmetric encryption keys or uncompiled payload components may still reside in memory.", "Audit process execution logs and terminate active scripting interpreters (e.g. PowerShell, CMD, WScript) or commands executing 'vssadmin.exe delete shadows' or 'wbadmin' used by Whiteclick to inhibit recovery.", "Investigate the initial compromise vector (such as exposed RDP instances, spearphishing attachments, or vulnerable edge gateways) and enforce an immediate credential reset for all compromised Active Directory accounts.", "Restore critical assets and databases exclusively from verified, air-gapped, or immutable offline backups once the Whiteclick binary and related persistence hooks are eradicated." ], "what_to_avoid": [ "Do not restart or power cycle infected systems prematurely; doing so destroys volatile RAM encryption keys and may trigger bootloader locking logic embedded in Whiteclick.", "Avoid negotiating or paying the extortion demand without prior forensic evaluation and consultation with incident response specialists, as payment does not guarantee data recovery.", "Do not connect clean backup drives or external storage to the affected network until Whiteclick eradication is completely verified." ], "target_platforms": [ "Windows 11", "Windows 10", "Windows Server 2022", "Windows Server 2019" ] }