{ "family": "whenu", "sample_count": 1, "category": "advanced_threat", "description": "

Executive Summary

\nWhenU (most famous for its \"SaveNow\" application) is one of the original, pioneering families of Adware. Highly prevalent in the early 2000s, WhenU established many of the deceptive bundling and behavioral tracking techniques still utilized by modern Potentially Unwanted Programs (PUPs). It was designed to monitor a user's web browsing in real-time to deliver highly targeted, contextual pop-up advertisements.\n\n

Distribution and Technical Behavior

\nWhenU was almost exclusively distributed via aggressive software bundling. It was famously packaged with early, highly popular peer-to-peer (P2P) file-sharing applications (like BearShare and Kazaa), meaning users inadvertently installed the adware when seeking out legitimate software.\n\nOnce executed, WhenU integrated deeply into the user's browsing experience:\n\n\n

Risk Assessment

\nWhile WhenU argued it was legitimate marketing software (and fought numerous legal battles regarding the definition of spyware), it was universally classified as Adware by security vendors. It caused immense system slowdowns, generated highly disruptive pop-ups, and represented a significant invasion of user privacy by tracking all web activity.\n\n

Mitigation and Removal Strategies

\n", "cta": "Published by the SystemHelpdesk team.", "aliases": [ "Adware.WhenU", "PUP.SaveNow", "Adware.WhenUSave" ], "enrichment_level": "expert-seo", "faq": [ { "@type": "Question", "name": "What is Whenu and what threat category does it belong to?", "acceptedAnswer": { "@type": "Answer", "text": "Whenu 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 Whenu establish persistence and evade defensive controls?", "acceptedAnswer": { "@type": "Answer", "text": "Whenu 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 Whenu compromise?", "acceptedAnswer": { "@type": "Answer", "text": "Security teams responding to Whenu 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.WhenU leverage in enterprise intrusions?", "acceptedAnswer": { "@type": "Answer", "text": "Adware.WhenU 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.WhenU maintain covert communications and evade perimeter network monitoring?", "acceptedAnswer": { "@type": "Answer", "text": "Adware.WhenU 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": [ "T1112", "T1566.002", "T1176" ], "cisa_advisory": null, "last_updated": "2026-10-15", "type": "Classic 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": "T1112", "name": "Modify Registry", "tactic": "Defense Evasion" }, { "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" } ], "containment_steps": [ "Enforce forensic network isolation on all suspected endpoints while maintaining an out-of-band telemetry conduit to capture live Whenu adversary activity.", "Perform full memory dumps across identified staging nodes to extract memory-only implants, kernel rootkit hooks, and decrypted Whenu 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 Whenu.", "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 Whenu operators." ], "what_to_avoid": [ "Do not assume the incident is resolved simply because an antivirus tool removed the initial Whenu 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 Whenu 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" ] }