Deepscan
Table of Contents
Overview
Rogue:Win32/Deepscan (often operating under names like 'DeepScan Antivirus' or 'Security DeepScan') is a classic example of **Scareware** or a **Rogue Antivirus** program. Its primary objective is financial extortion. It infects a system, displays highly realistic but entirely fabricated security alerts claiming the computer is overrun with non-existent malware, and then demands the user pay for a 'premium' license to clean the machine.
Understanding the Deepscan Threat
To an end-user, Deepscan is terrifying. It frequently disables the Windows Task Manager, hides desktop icons, and constantly bombards the screen with flashing red warning messages mimicking the Windows Security Center. To an enterprise, it represents a severe productivity loss, a high risk of user-initiated credit card fraud, and a failure in endpoint application control.
Execution and Extortion Mechanics
Deepscan is typically distributed via malvertising (fake 'Your PC is Infected' pop-ups on streaming sites) or bundled with deceptive software (`T1189`). Upon execution (`T1204.002`), it heavily modifies the Windows Registry. Crucially, it uses Image File Execution Options (IFEO) (`T1546.012`) to intercept the launch of legitimate diagnostic tools (like `taskmgr.exe`, `regedit.exe`, and actual AV software) and instead launches its own warning screens. It runs a fake 'deep scan' animation that invariably finds dozens of 'critical threats'. When the panicked user clicks 'Fix All', they are directed to a payment portal (`T1592`). The software holds the system's usability hostage until the ransom is paid.
Indicators of Compromise & Impact
The impact is a completely unusable endpoint and potential financial theft. IoCs are glaringly obvious to the user: persistent, non-dismissible windows demanding payment for AV software they never installed. EDR logs will show the creation of the IFEO registry keys hijacking standard Windows utilities. The executable itself is often a brightly colored, unsigned file located in `%AppData%` or `%ProgramData%`.
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 (Fake AV pop-ups) | Initial Access | ATT&CK ↗ |
T1546.012 | Event Triggered Execution: Image File Execution Options Injection (Disabling Task Manager) | Privilege Escalation | ATT&CK ↗ |
T1491.001 | Defacement: Internal Defacement (Fake security alerts) | Impact | ATT&CK ↗ |
T1204.002 | User Execution: Malicious File | Execution | ATT&CK ↗ |
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-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-WIM | Web Interface Monitoring | Detect | T1491.001 | Deploy automated file integrity monitoring (FIM) and continuous HTTP checksum verification across public web roots. |
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_DEEPSCAN_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for Deepscan"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "deepscan" 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 - Deepscan (Advanced Threat) Execution & Triage
id: fceeba4f-b7e1-59ee-b309-3929076f8b98
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the Deepscan 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/deepscan
- 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.t1204_002
- attack.t1491_001
- attack.t1189
- attack.t1546_012
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_DEEPSCAN_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for Deepscan 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 = "deepscan" 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.
- Do not allow the user to enter their credit card information; the alerts are fake, and the 'license' does nothing.
- Boot the infected system into Windows Safe Mode; this bypasses the Rogue AV's autostart mechanisms and allows access to diagnostic tools.
- Use an enterprise anti-malware tool (like Malwarebytes) in Safe Mode to locate and remove the executable and the hijacked IFEO registry keys.
- If the user submitted payment information, advise them to immediately contact their bank to cancel the card and report fraud.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Avoid paying the ransom; it funds criminal operations and does not guarantee the malware will actually remove itself.
- Do not assume the machine actually has the secondary viruses Deepscan is reporting; the scan results are hardcoded strings.
References & External Analysis
- Search "deepscan" on VirusTotal (External Analysis)
- Search "deepscan" on Any.Run (Sandbox Sandbox)
- Search "deepscan" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is Deepscan and what threat category does it belong to?
Deepscan 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 Deepscan establish persistence and evade defensive controls?
Deepscan 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 Deepscan compromise?
Security teams responding to Deepscan 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 Deepscan leverage in enterprise intrusions?
Deepscan 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 Deepscan maintain covert communications and evade perimeter network monitoring?
Deepscan 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 Deepscan from Windows?
Manual removal of Deepscan 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 Deepscan infection?
Symptoms of Deepscan 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 Deepscan 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/deepscan.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.