Attackers are increasingly using counterfeit software installers, malicious installation packages, and legitimate deployment utilities to establish initial access, taking advantage of the elevated permissions and system changes that ordinarily accompany software installation.
Software installers represent an attractive attack surface for threat actors. Installing a legitimate application often involves executing multiple processes, extracting files into temporary directories, modifying registry entries, creating services, and occasionally requesting administrative privileges. These operations are expected during normal software deployment, giving attackers an opportunity to conceal malicious execution within activity that may initially appear legitimate.
Rather than exploiting a vulnerability in the operating system or targeting an exposed network service, an attacker can distribute a malicious installer disguised as familiar software and convince a user to execute it. The resulting installation may deploy the advertised application, execute an additional payload, or install legitimate administrative software configured to provide unauthorized remote access.
Recent investigations from Microsoft Threat Intelligence, Huntress, and Check Point Research demonstrate how this approach has developed into a repeatable initial-access method. Campaigns have used counterfeit software websites, modified installation packages, abused code-signing certificates, and legitimate installer frameworks to distribute information stealers, remote-access tools, and persistent malware.
Why Software Installers Make Effective Delivery Mechanisms
Windows supports several software installation formats, including Microsoft Installer (MSI) packages, executable installers, and MSIX application packages. Third-party frameworks such as Inno Setup, NSIS, and InstallShield provide developers with additional options for packaging applications, configuring installation behavior, and distributing software.
These capabilities create opportunities for malicious activity when an attacker controls the installation package.
MSI files, for example, are structured installation databases interpreted by the Windows Installer service. They contain information about application components, installation sequences, registry modifications, and other operations required to install software. Windows Installer also supports custom actions, allowing developers to execute additional programs, invoke dynamic-link libraries (DLLs), and run scripts during installation.
Custom actions are legitimate components of Windows Installer, but they can also be abused to execute malicious code. An attacker-controlled MSI could invoke an additional executable, load a malicious DLL, or establish persistence through operations performed during installation. Depending on the installation context, the permissions granted, and the custom action configuration, portions of this activity may execute with elevated privileges.
Microsoft’s Windows Installer documentation explicitly identifies security concerns associated with custom actions, particularly those that execute with elevated permissions or load untrusted external libraries.
Executable installers offer similar opportunities. An installer built using Inno Setup may extract components into a temporary directory before executing additional processes. Attackers can exploit this behavior to introduce malicious executables into the installation sequence, making their execution appear to originate from an ordinary setup program.
The use of an installer framework does not make a file malicious. The problem arises when an attacker modifies the installation workflow, adds unauthorized functionality, or distributes a counterfeit package that performs operations unrelated to the software the user intended to install.
Counterfeit Downloads and the Initial Infection Chain
The initial stage frequently begins before an installer reaches the endpoint.
Threat actors distribute malicious packages through search engine optimization poisoning, malicious advertisements, phishing messages, and websites impersonating established software vendors. These websites may reproduce a vendor’s branding, product descriptions, and download interfaces to make the installation package appear authentic.
A user searching for a legitimate application may encounter a fraudulent download page and retrieve an installer from attacker-controlled infrastructure. The downloaded file can retain the expected product name and installation interface, reducing the likelihood that the user will question its legitimacy.
In September 2026, Microsoft Defender Experts documented a campaign involving counterfeit software-download websites that impersonated products associated with Razer, Microsoft Edge, Kaspersky, Calibre, and other vendors.
In one documented case, a user visited a fraudulent Razer download page and retrieved a malicious ZIP archive from a separate delivery server. Microsoft’s telemetry identified two archives downloaded under the same filename within approximately 69 seconds, each containing different content.
This demonstrated that the delivery infrastructure could generate different installation packages between requests. The resulting variation complicates detection methods that depend exclusively on known malicious hashes.
Once executed, the counterfeit installer deployed additional components into randomized directories, including locations beneath C:\Users\Public and C:\Program Files (x86). Subsequent activity included scheduled-task persistence, attempts to weaken endpoint protections, process injection, and communication with command-and-control infrastructure.
The campaign illustrates an important distinction: the apparent source of a software download may have no relationship to the infrastructure delivering the executable, and the initial installation file may be only the first component of a larger execution chain.
Malicious Payloads Hidden Within Installer Workflows
An attacker does not necessarily need to replace an entire application’s functionality to distribute malware. A modified installer can preserve enough legitimate behavior to appear functional and execute additional components during the installation process.
One technique involves using an installation bootstrapper to launch secondary executables from temporary directories. These components may download additional payloads, execute scripts, or establish persistence without presenting another installation dialog.
In November 2026, Microsoft Threat Intelligence reported a fake-download campaign that distributed trojanized Inno Setup-style installers through websites advertising cracked applications, games, plugins, activators, and unofficial utilities.
After execution, the installers created temporary runners in directories matching %TEMP%\is-*.tmp\. These processes launched additional executable stages, including files with names matching eld*.exe, and communicated with remote infrastructure responsible for coordinating downstream installations.
The campaign used a callback structure containing parameters such as d=inno and r=offer_execution to track individual installation attempts. Different stages could download and deploy separate software packages during a single installation session.
Microsoft identified three confirmed monetization branches. One involved WorldProxyPool, which could route third-party network traffic through affected devices. Another deployed CharityEngine and BOINC components for distributed-computing activity. A third installed utility-style software associated with advertising monetization.
The installed components were not necessarily malicious applications in isolation. The security concern was their deployment through deceptive installers without informed user consent, alongside the unauthorized use of affected systems and resources.
This type of installer abuse demonstrates how a single user-initiated download can produce several independent installation events, each with its own executable files, network connections, and persistence mechanisms.
Abusing Msiexec and Silent Installation
The Windows Installer utility, msiexec.exe, is another component frequently encountered in installer-based intrusion chains.
As a legitimate Windows executable, msiexec interprets MSI packages and supports operations such as installing, modifying, repairing, and removing software. It also supports unattended installation through options such as /qn and /quiet, which suppress the usual installation interface.
Silent installation is standard behavior in enterprise software deployment. Administrators routinely use it through device-management platforms and automated provisioning workflows. Attackers can use the same functionality to deploy software without presenting additional prompts after the required execution context has been obtained.
MITRE ATT&CK identifies malicious use of msiexec as T1218.007: System Binary Proxy Execution. This technique covers the use of the trusted Windows Installer utility to execute attacker-controlled installation packages or other malicious components.
An installer may launch msiexec to process a secondary package, which then writes executables, creates application directories, or establishes persistence. The resulting activity can resemble ordinary software deployment, particularly in environments with frequent application updates.
The presence of msiexec or an unattended installation switch is not sufficient evidence of compromise. A stronger detection opportunity emerges when installation activity originates from an unexpected process, references an unapproved package source, creates executables in unusual directories, or initiates network activity unrelated to the intended application.
Monitoring these relationships is more reliable than treating every installation operation as suspicious.
Legitimate Installers Used to Establish Unauthorized Remote Access
Not every installer-based intrusion requires a modified or maliciously compiled installation package.
Threat actors can distribute legitimate remote monitoring and management (RMM) software that has been configured to connect affected systems to infrastructure under their control.
In September 2026, Microsoft reported phishing campaigns that distributed legitimate, digitally signed MSP360 RMM installers through deceptive meeting invitations, PDF-related messages, and software update prompts.
The downloaded executables used filenames suggesting familiar business applications or documents. After execution and user-approved elevation, the legitimate MSP360 installer established remote-management services on the affected endpoint.
The attackers then used the MSP360 deployment to download and install ConnectWise ScreenConnect, introducing a secondary remote-access channel. This provided additional access to compromised systems and supported subsequent information collection and credential-access activity.
Neither application needed to contain a malicious modification for the technique to succeed. The threat originated from unauthorized deployment and attacker control of legitimate administrative functionality.
This introduces a different detection problem from conventional malware distribution. An endpoint security product may recognize the executable as legitimate, verify its digital signature, and observe expected installation behavior. The malicious activity becomes apparent through the installation source, the identity of the deploying user, the remote-management configuration, or the subsequent actions performed through the installed software.
For organizations, an unexpected RMM installation should be investigated against approved software inventories, deployment records, and authorized management infrastructure rather than assessed solely through its executable signature.
DLL Sideloading and Signed Application Abuse
Installer-based attacks can also take advantage of the way Windows applications load executable dependencies.
DLL sideloading occurs when an attacker places a malicious library where a legitimate executable will load it through its normal dependency resolution behavior. The attacker can then execute malicious code within the context of a trusted application.
This technique is associated with MITRE ATT&CK T1574.001, which covers abuse of DLL loading behavior, including search-order hijacking.
The technique becomes particularly useful when a modified installer contains a legitimate signed executable alongside malicious supporting files. Security products may recognize the primary executable as trusted, yet the application can still load an attacker-controlled library during execution.
A 2026 Check Point Research investigation into Nimbus Manticore documented a trojanized Zoom installer that used a related .NET execution technique known as AppDomain hijacking.
The malicious archive contained a legitimate Microsoft-signed executable, a configuration file, malicious DLL components, and an original Zoom installer. When the user launched the setup executable, its configuration caused a malicious DLL to load.
The malware also launched the legitimate Zoom installer, allowing the expected installation to proceed. During this process, the attacker-controlled code monitored for a scheduled task associated with Zoom updates and modified it to execute a later-stage component.
This created a persistence mechanism connected to activity ordinarily associated with a legitimate application’s installation and update process.
The case demonstrates that successful installation of the advertised software does not establish that the original package was trustworthy. Malicious execution can occur alongside a functioning application, leaving fewer obvious signs that the downloaded installer contained unauthorized components.
Why Digital Signatures Are Not Sufficient
Code signing provides an important integrity and publisher-verification mechanism, but a valid signature does not establish that an executable is benign or originates from the vendor the user intended to contact.
Digital signatures associate software with a signing identity and allow verification that signed content has not been modified since signing. They do not independently establish the legitimacy of the publisher’s intentions.
In May 2026, Microsoft disclosed its investigation into Fox Tempest, a financially motivated threat actor operating a malware-signing-as-a-service offering.
The operation abused Microsoft Artifact Signing to obtain fraudulent, short-lived signing certificates that could be used to sign malicious executables. According to Microsoft, associated threat actors distributed software impersonating products such as Microsoft Teams, AnyDesk, PuTTY, and Webex.
Microsoft also documented Vanilla Tempest’s use of signed, trojanized Microsoft Teams installers distributed through malicious advertisements and fraudulent download pages.
In these cases, the presence of a valid digital signature could make a malicious executable appear more credible to users and interfere with defenses that relied too heavily on signed-file status.
For defenders, the relevant questions extend beyond whether a file is signed. The signing identity, expected publisher, file provenance, certificate history, installation behavior, and subsequent process activity all contribute to determining whether an installer is trustworthy.
A properly signed file can still execute attacker-controlled functionality, and a legitimate signed application can still be deployed for unauthorized purposes.
Detecting Installer-Based Intrusions
Detecting malicious installer activity requires visibility into the complete execution sequence rather than the installation package alone.
The first opportunity is often the download itself. Browser-origin telemetry, file creation events, download URLs, and referrer information can establish where an installation package originated. In Microsoft’s September 2026 counterfeit-installer investigation, download provenance helped associate fraudulent vendor pages with the infrastructure delivering malicious archives.
Process ancestry provides the next investigative layer. An analyst should be able to determine which process launched an installer, whether it executed additional programs, which files those processes created, and whether subsequent activity matched the installation’s expected behavior.
For example, an installer that launches a script interpreter, writes an unfamiliar executable beneath a user-writable directory, creates a recurring scheduled task, and establishes outbound communication to an unrelated domain warrants investigation. The combination is more informative than any individual event.
Windows telemetry provides several useful sources. Sysmon Event ID 1 records process creation, Event ID 3 captures network connections when configured, Event ID 7 records module loads, Event ID 11 captures file creation, Event ID 13 records registry value modifications, and Event ID 22 captures DNS queries. Windows Security Event ID 4698 can provide evidence of scheduled-task creation when the appropriate auditing is enabled.
These events can help reconstruct an installer-driven execution chain from the original user action through payload staging, persistence, and network communication.
Module-load telemetry can be particularly useful for identifying DLL sideloading. A trusted executable loading an unsigned or unexpectedly signed DLL from an unusual location may indicate that an attacker has manipulated its dependency-loading behavior. Collection should be filtered and tuned, since broad image-load logging can generate substantial event volume.
MSI-related process and command-line activity also deserves attention. MITRE’s DET0158 detection strategy recommends correlating msiexec execution with references to remote installation packages, unexpected DLL activity, and network connections to unfamiliar destinations.
Endpoint detection and response platforms can extend this analysis by correlating related events across a process tree. Analysts should prioritize installer executions that originate outside approved deployment workflows, produce suspicious child processes, create unexplained persistence mechanisms, or install remote-management applications that are not part of the organization’s authorized software inventory.
Static indicators, including file hashes and filenames, remain useful for confirming known activity. They are less dependable as the only detection method when attackers regenerate archives, modify payloads, or reuse ordinary installer frameworks.
Reducing Exposure to Malicious Installers
Preventing installer-based intrusions begins with establishing control over where software is obtained and how it is deployed.
Organizations can reduce exposure by directing employees to approved software repositories and distributing applications through managed deployment systems. Restricting unnecessary local administrator privileges can also limit the ability of unauthorized installers to make privileged changes, although applications running with standard-user permissions can still establish user-level persistence or access sensitive data.
Application control provides another layer of defense. Microsoft App Control for Business and AppLocker can restrict executable activity according to configured policies, including signer identity, file attributes, and authorized deployment methods.
App Control for Business also supports managed-installer configurations that permit software deployed by designated management solutions. These policies require careful configuration and testing, since overly broad trust rules and administrative access can undermine their intended restrictions.
Code-signing verification should be combined with checks against approved publishers, expected product identities, and application inventories. A valid signature from an unfamiliar publisher does not establish that an installer belongs to the software vendor being impersonated.
Organizations should also maintain visibility into newly installed services, scheduled tasks, startup entries, and RMM agents. Unauthorized remote-management software deserves particular attention due to its ability to establish persistent interactive access without requiring a conventional malware implant.
Endpoint controls such as attack surface reduction rules, tamper protection, reputation-based download protection, and behavioral detection can help interrupt malicious installation chains. Their effectiveness depends on the attack mechanism and the controls configured in the environment.
Equally important is preserving enough endpoint and network telemetry to investigate what occurred after an installer executed. A successful prevention alert may identify the initial file, but a complete investigation must determine whether additional components were installed or persistence was established before the alert.
Software Installation as an Initial-Access Problem
Software installers occupy a trusted position in endpoint operations. They are expected to create files, invoke additional processes, modify system configurations, and occasionally operate with elevated privileges. Threat actors take advantage of these expectations by placing malicious activity inside workflows that are common across enterprise environments.
Recent campaigns demonstrate several distinct methods of abuse. Some deliver counterfeit installers that execute malware directly. Others modify legitimate setup packages, distribute signed malicious executables, or deploy legitimate administrative software configured for unauthorized access. In certain cases, the advertised application installs successfully alongside the malicious components.
These distinctions matter during incident response. A counterfeit installer downloaded from a fraudulent website does not necessarily indicate that the legitimate software vendor was compromised. Similarly, the presence of a signed executable does not establish that its deployment was authorized.
The most reliable defensive approach is to examine installation activity as a connected sequence of events, beginning with the download source and continuing through execution, file creation, persistence, and network communication.
As attackers continue to use familiar applications and installation frameworks for malware delivery, the origin and behavior of software installation will remain important indicators of potential initial compromise.
How Can Netizen Help?
Founded in 2013, Netizen is an award-winning technology firm that develops and leverages cutting-edge solutions to create a more secure, integrated, and automated digital environment for government, defense, and commercial clients worldwide. Our innovative solutions transform complex cybersecurity and technology challenges into strategic advantages by delivering mission-critical capabilities that safeguard and optimize clients’ digital infrastructure. One example of this is our popular “CISO-as-a-Service” offering that enables organizations of any size to access executive level cybersecurity expertise at a fraction of the cost of hiring internally.
Netizen also operates a state-of-the-art 24x7x365 Security Operations Center (SOC) that delivers comprehensive cybersecurity monitoring solutions for defense, government, and commercial clients. Our service portfolio includes cybersecurity assessments and advisory, hosted SIEM and EDR/XDR solutions, software assurance, penetration testing, cybersecurity engineering, and compliance audit support. We specialize in serving organizations that operate within some of the world’s most highly sensitive and tightly regulated environments where unwavering security, strict compliance, technical excellence, and operational maturity are non-negotiable requirements. Our proven track record in these domains positions us as the premier trusted partner for organizations where technology reliability and security cannot be compromised.
Netizen holds ISO 27001, ISO 9001, ISO 20000-1, and CMMI Level III SVC registrations demonstrating the maturity of our operations. We are a proud Service-Disabled Veteran-Owned Small Business (SDVOSB) certified by U.S. Small Business Administration (SBA) that has been named multiple times to the Inc. 5000 and Vet 100 lists of the most successful and fastest-growing private companies in the nation. Netizen has also been named a national “Best Workplace” by Inc. Magazine, a multiple awardee of the U.S. Department of Labor HIRE Vets Platinum Medallion for veteran hiring and retention, the Lehigh Valley Business of the Year and Veteran-Owned Business of the Year, and the recipient of dozens of other awards and accolades for innovation, community support, working environment, and growth.
Looking for expert guidance to secure, automate, and streamline your IT infrastructure and operations? Start the conversation today.














You must be logged in to post a comment.