High
Table of Contents
Overview
Executive Summary
The "High" classification is a generic risk severity indicator utilized by heuristic antivirus engines and threat intelligence platforms. It is not a specific malware family, but rather a definitive flag indicating that an analyzed file or process exhibits behaviors fundamentally dangerous to the security and integrity of a system.Behavioral Context and Detection Mechanisms
Security tools assign a "High" risk label when a file engages in activities that strongly correlate with destructive malware or advanced persistent threats (APTs), even if the file's static signature does not match a known database entry. Behaviors that trigger a "High" severity alert include:- Ransomware Indicators: Rapid, mass encryption of files in user directories, or attempts to delete Volume Shadow Copies (`vssadmin.exe delete shadows`).
- Privilege Escalation: Unauthorized attempts to exploit known local vulnerabilities (e.g., exploiting outdated drivers) to gain `SYSTEM` level access.
- Defense Evasion: Actively attempting to terminate security processes, disable Windows Defender, or unhook user-mode APIs used by EDR solutions.
Risk Assessment and Incident Triage
An alert classified as "High" requires immediate, critical incident response. Unlike generic adware labels, a "High" detection indicates an active attempt to compromise the network, steal data, or cause significant operational disruption.Response and Eradication Strategy
- Immediate Containment: The endpoint triggering the "High" alert must be instantly severed from the corporate network, either physically or via network isolation features within the EDR platform, to halt lateral movement.
- Forensic Capture: Capture a memory dump and disk image of the isolated endpoint for forensic analysis to determine the scope of the breach and identify the specific threat actor or malware family involved.
- Threat Hunting: Utilize the behavioral indicators that triggered the alert (e.g., specific command-line arguments, dropped file paths) to conduct a proactive threat hunt across the entire enterprise environment.
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 |
|---|---|---|---|
T1204 | User Execution (Relying on the user to bypass the heuristic warning) | Execution | ATT&CK ↗ |
T1055 | Process Injection | Defense Evasion | ATT&CK ↗ |
T1547.001 | Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder | Persistence | ATT&CK ↗ |
T1105 | Ingress Tool Transfer | Command and Control | ATT&CK ↗ |
T1082 | System Information Discovery | Discovery | ATT&CK ↗ |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1105: Implement network intrusion detection systems (NIDS) and host-based firewalls to block unauthorized inbound or outbound file transfers.
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-PIAD | Process Injection Analysis & Detection | Detect | T1055 | Monitor cross-process thread creation (CreateRemoteThread) and asynchronous procedure calls (QueueUserAPC). |
D3-SDA | System Discovery Analysis | Detect | T1082 | Alert on rapid enumerations of systeminfo, hostname, and registry hardware trees in short intervals. |
D3-NTI | Network Traffic Inspection | Detect | T1105 | Inspect deep packet payloads for anomalous staging binaries and unauthorized egress protocols. |
D3-EPP | Endpoint Policy & Execution Protection | Harden | T1204 | Configure AppLocker or Windows Defender Application Control (WDAC) to prevent unapproved binary execution. |
D3-RPM | Registry Persistence Monitoring | Detect | T1547.001 | Audit and restrict write privileges to user and machine-level Registry Run/RunOnce keys using Endpoint Privilege Management. |
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_HIGH_T1_ARTIFACT {
meta:
description = "Tier 1 Primitive Artifact: Raw string matches for High"
tier = "T1 - Primitive Artifact"
confidence = "Low-Medium (Fast Triage)"
author = "SystemHelpdesk Threat Research Desk"
date = "2026-10-14"
strings:
$s1 = "high" ascii wide nocase
$s2 = "highrisk" ascii wide nocase
$s3 = "risk.high" ascii wide nocase
$s4 = "generic.high" 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 - High (Generic Detection) Execution & Triage
id: 48af9171-4b5c-53f7-baf4-bf022326374b
status: production
description: Detects execution, defense evasion, and persistence behaviors associated
with the High 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/high
- https://malware-families-catalog.systemhelpdesk.com/defensive/ransomware-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.generic-detection
- author.ricky-jordan
- source.systemhelpdesk-mfc
- attack.t1204
- attack.t1055
- attack.t1547_001
- attack.t1105
- attack.t1082
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_HIGH_T3_ATTRIBUTION {
meta:
description = "Tier 3 Attribution Fingerprint: Heuristic detection for High 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 = "high" 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.
- Sever network connectivity for the flagged endpoint to terminate persistent command-and-control (C2) communication channels and stop High from retrieving secondary stage payloads.
- Capture process memory triage to detect and terminate malicious threads injected by High into legitimate system processes such as explorer.exe or svchost.exe.
- Audit Windows Registry Run keys (HKCU\Software\Microsoft\Windows\CurrentVersion\Run) and Task Scheduler entries to locate and purge High persistence hooks.
- Deploy updated enterprise EDR detection signatures and conduct an out-of-band endpoint scan to isolate dropped binaries and staged payloads.
- Rotate all credentials, domain user passwords, and session cookies active on the system during the High execution timeframe.
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 High 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 High 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 "high" on VirusTotal (External Analysis)
- Search "high" on Any.Run (Sandbox Sandbox)
- Search "high" on MalwareBazaar (Malware Samples)
Frequently Asked Questions
What is High and what threat category does it belong to?
High is classified as a Generic Detection. 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 High establish persistence and evade defensive controls?
High 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 High compromise?
Security teams responding to High 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 secondary payloads and staging behaviors are commonly associated with HighRisk?
HighRisk frequently operates as a loader or dropper designed to establish a foothold before downloading and executing secondary high-impact malware payloads. Depending on the threat actor's objectives, these dropped modules can range from ransomware and banking injects to modular infostealers and remote management backdoors.
How can security operations teams effectively detect and hunt for HighRisk across enterprise endpoints?
Defenders should hunt for HighRisk by deploying behavioral endpoint detection and response (EDR) rules that monitor suspicious process spawning (such as cmd.exe or powershell.exe spawned from office documents or temporary directories), anomalous outbound network connections from non-browser binaries, and unauthorized modifications to Windows Run keys and scheduled task registries.
How do I remove the High Generic_Detection from Windows?
Manual removal of High 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 High a virus or a Generic_Detection?
High is classified as a Generic_Detection. Unlike traditional viruses that infect files, modern malware like High typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a High infection?
Symptoms of High 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 Generic_Detections
Want to prevent High 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/high.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.