Plicker
Table of Contents
Overview
Executive Summary
Plicker is an intrusive adware family and Potentially Unwanted Program (PUP) designed to aggressively monetize infected systems. It hijacks web browsers, alters core system configurations, and bombards the user with unsolicited, often deceptive, advertisements, significantly degrading system performance and user privacy.Technical Analysis and Behavior
Plicker relies almost entirely on deceptive software bundling for distribution. Users inadvertently install the adware when downloading media players, file converters, or "free" utilities from low-reputation software aggregation websites. Upon execution, Plicker immediately attempts to establish persistence by creating registry run keys and hidden scheduled tasks. It installs malicious extensions across all detected web browsers (Chrome, Firefox, Edge) and frequently modifies system-wide proxy settings to route web traffic through servers controlled by the adware operators. This "man-in-the-middle" position allows Plicker to:- Inject Advertisements: Overlay pop-up ads, banners, and in-text hyperlinks onto legitimate, encrypted (HTTPS) websites.
- Hijack Searches: Redirect queries from default search engines to affiliate-controlled portals to generate ad revenue.
- Harvest Data: Track browsing history, search habits, and geolocation data, building comprehensive profiles that are sold to third-party marketing firms.
Risk Assessment
While Plicker is not categorized as destructive malware, its privacy implications are severe. The constant network activity slows down the endpoint, and the injected advertisements are frequently served by untrusted networks, greatly increasing the risk of exposure to exploit kits, tech support scams, and secondary malware infections.Eradication and Prevention Strategies
- Endpoint Protection Policies: Configure EPP/EDR solutions to aggressively detect and block the installation of Potentially Unwanted Programs (PUPs) and grayware.
- Browser Remediation: Manually remove any suspicious browser extensions associated with Plicker and perform a full browser reset to clear hijacked homepages and search engine settings.
- Application Control: Implement least-privilege access and utilize application whitelisting to prevent standard users from installing unverified software bundles.
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 |
|---|---|---|---|
T1566.002 | Phishing: Spearphishing Link (Social engineering to force the user to download the tool) | Initial Access | ATT&CK ↗ |
T1176 | Browser Extensions | Persistence | ATT&CK ↗ |
T1112 | Modify Registry | Defense Evasion | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1566.002: Inspect email links for known malicious domains and use link-rewriting services for time-of-click analysis.
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-RVM | Registry Value Modification Analysis | Detect | T1112 | Log Windows Event ID 4657 to monitor unauthorized modifications to system configuration and security settings. |
D3-BEA | Browser Extension Allowlisting | Harden | T1176 | Deploy enterprise browser policies via GPO or Intune to block unauthorized side-loaded extensions and add-ons. |
D3-URLR | URL Rewriting & Time-of-Click Inspection | Filter | T1566.002 | Rewrite all external email links to force real-time URL reputation and DNS resolution at click time. |
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_PLICKER_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Plicker"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "plicker" ascii wide nocase
$s2 = "adware.plicker" ascii wide nocase
$s3 = "pup.plicker" ascii wide nocase
$s4 = "win32/plicker" 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 - Plicker (Advanced Threat) Execution & Triage
id: 377d3950-7d20-5b3a-aa2a-a8bf4a91d4c7
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Plicker malware family. Detects proxy execution, reflective DLL loading,
and remote command injection associated with modular enterprise backdoors.
references:
- https://malware-families-catalog.systemhelpdesk.com/families/plicker
- https://malware-families-catalog.systemhelpdesk.com/defensive/backdoor-rat-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.advanced-threat
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1566_002
- attack.t1176
- attack.t1112
logsource:
category: process_creation
product: windows
detection:
selection_process:
Image|endswith:
- \powershell.exe
- \cmd.exe
- \rundll32.exe
- \regsvr32.exe
CommandLine|contains:
- DownloadString
- IEX(
- '/s /n /u /i:'
- sc create
- start-process
condition: selection_process
falsepositives:
- Legitimate enterprise administrative scripts during approved change windows
- Authorized IT software deployment utilities and backup management agents
level: highTier 3 Attribution Fingerprint Rule (High Fidelity)
Deep signature matching distinctive operational fingerprints and payload characteristics.
rule MALWARE_WIN_PLICKER_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Plicker 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 = "plicker" 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.
- Enforce forensic network isolation on all suspected endpoints while maintaining an out-of-band telemetry conduit to capture live Plicker adversary activity.
- Perform full memory dumps across identified staging nodes to extract memory-only implants, kernel rootkit hooks, and decrypted Plicker 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 Plicker.
- 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 Plicker operators.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not assume the incident is resolved simply because an antivirus tool removed the initial Plicker 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 Plicker until memory triage is complete.
- Do not delay host isolation; automated lateral movement and credential dumping can occur within minutes of initial execution.
References & External Analysis
- Search "plicker" on VirusTotal (External Analysis)
- Search "plicker" on Any.Run (Sandbox Sandbox)
- Search "plicker" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Plicker and what threat category does it belong to?
Plicker 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.
How does Plicker establish persistence and evade defensive controls?
Plicker 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.
What are the essential incident response steps for mitigating a Plicker compromise?
Security teams responding to Plicker 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.
What lateral movement and credential access tactics does Adware.Plicker leverage in enterprise intrusions?
Adware.Plicker 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.
How does Adware.Plicker maintain covert communications and evade perimeter network monitoring?
Adware.Plicker 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.
How do I remove the Plicker Advanced_Threat from Windows?
Manual removal of Plicker 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 Plicker a virus or a Advanced_Threat?
Plicker is classified as a Advanced_Threat. Unlike traditional viruses that infect files, modern malware like Plicker typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Plicker infection?
Symptoms of Plicker 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 Advanced_Threats
Want to prevent Plicker 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/plicker.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.