Hiddeninstall
Overview
Adware:Win32/Hiddeninstall (also detected as PUP.Optional.HiddenInstall) is a generic classification for software deployment wrappers that silently install Potentially Unwanted Programs (PUPs), Adware, and sometimes full-fledged malware without displaying a user interface or explicitly asking for consent (`T1189`).
Understanding Hiddeninstall (Silent Droppers)
To an end-user, Hiddeninstall is entirely invisible; they may think they downloaded a portable application or that an installation failed, only to later discover unwanted toolbars, changed homepages, and system sluggishness. For a security analyst, these silent installers are a significant vector for enterprise compromise, bypassing user awareness training entirely.
Execution and Evasion Mechanics
Hiddeninstall wrappers are often distributed via peer-to-peer networks, cracked software sites, or deceptive 'Download Now' buttons on file-sharing portals. The executable is typically a compiled script (like AutoIt or Inno Setup) configured to run in 'silent' or 'very silent' mode. Upon execution, it extracts its payload into the `%Temp%` directory (`T1027.009`) and uses command-line arguments (e.g., `/S` or `/quiet`) to force the installation of bundled applications without rendering any GUI windows. It often modifies the Registry (`T1112`) to suppress standard Windows UAC prompts if the user has disabled default security settings.
Indicators of Compromise & Impact
The primary impact is the stealthy installation of nuisance or malicious software. Host-based IoCs include EDR alerts for known installer framework executables (like `setup.exe` or `install.exe`) launching with silent command-line switches (`/S`, `/SILENT`, `/VERYSILENT`) and immediately dropping multiple, unrelated executables into the Temp directory. Network IoCs include sudden spikes in HTTP traffic to known adware affiliate networks as the silent installer 'phones home' to register the successful installation.
MITRE ATT&CK Techniques
Observed techniques used by this family, mapped to the MITRE ATT&CK framework:
| Technique | Name | Tactic |
|---|---|---|
T1189 | Drive-by Compromise (Initial distribution via deceptive downloads) | Initial Access |
T1059.003 | Command and Scripting Interpreter: Windows Command Shell (Using silent command line arguments for installation) | Execution |
T1027.009 | Obfuscated Files or Information: Embedded Payloads (Extracting the PUPs from the wrapper) | Defense Evasion |
Tactical Mitigations
Based on the techniques used by this family, consider the following defensive strategies:
- T1059.003: Restrict execution of Windows Command Shell (cmd.exe) and block unauthorized batch scripts.
Generated Detections (Boilerplate)
These YARA and Sigma rules are auto-generated based on the family name and aliases. They must be heavily tuned before deployment in a production environment.
YARA Rule
rule MALWARE_WIN_HIDDENINSTALL {
meta:
description = "Detects Hiddeninstall (advanced_threat)"
author = "SystemHelpdesk Boilerplate Generator"
date = "2026-07-06"
strings:
$s1 = "hiddeninstall" ascii wide nocase
condition:
uint16(0) == 0x5a4d and any of them
}Sigma Rule
title: Suspicious Hiddeninstall Activity
id: 221d287a439a89adda20c9b298afa3d4
status: experimental
description: Detects generic indicators of the hiddeninstall malware family.
logsource:
category: process_creation
product: windows
detection:
selection:
Image|endswith:
- '\cmd.exe'
- '\powershell.exe'
CommandLine|contains:
- "*hiddeninstall*"
condition: selection
level: mediumContainment & Response Steps
Ordered checklist for responders. Adapt to your environment and engage professional support for active incidents.
- Identify the source of the initial executable (e.g., a file downloaded via a web browser) and block the originating domain.
- Review the Windows Event Logs for recent application installations occurring concurrently with the execution of the suspicious file.
- Run an enterprise-grade anti-malware scan to clean up the adware and persistent registry hooks left behind by the silent installer.
- Implement Application Control (AppLocker) to strictly prevent the execution of untrusted binaries from the `%Temp%` directory.
What to Avoid
Common mistakes during response to this family that can destroy evidence, spread the infection, or worsen recovery.
- Do not assume a user intentionally installed the adware; Hiddeninstall specifically bypasses user interaction.
- Avoid relying solely on 'Add/Remove Programs' for cleanup, as silently installed adware often omits uninstaller entries to maintain persistence.
References & External Analysis
- Search "hiddeninstall" on VirusTotal (External Analysis)
Frequently Asked Questions
How do I remove the Hiddeninstall Advanced_Threat from Windows?
Manual removal of Hiddeninstall 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 Hiddeninstall a virus or a Advanced_Threat?
Hiddeninstall is classified as a Advanced_Threat. Unlike traditional viruses that infect files, modern malware like Hiddeninstall typically operates as a standalone payload designed to compromise systems, steal data, or deploy secondary stage implants.
What are the main symptoms of a Hiddeninstall infection?
Symptoms of Hiddeninstall 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.
Related Families (Category: advanced_threat)
Explore other malware families in the same category:
Protect Your Network Against Advanced_Threats
Want to prevent Hiddeninstall and similar threats from compromising your organization? Read our comprehensive defensive guide: Suspect an Infection? What to do.
Machine-readable
Get this profile as JSON: https://jordanricky1604-ship-it.github.io/malware-families-catalog/api/hiddeninstall.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.