Installer Packages

Executive Summary

Installer Packages (T1546.016) is a MITRE ATT&CK technique associated with Privilege Escalation, Persistence. Adversaries may establish persistence and elevate privileges by using an installer to trigger the execution of malicious content.

Why Attackers Use It

Attackers use Installer Packages because it provides a reliable way to advance their objective within the Privilege Escalation, Persistence tactic, often with a favorable balance of impact versus detectability on Linux, macOS, Windows environments. Defenders should assess this behavior in the context of the affected platform and adjacent activity rather than treating it as a standalone indicator.

MITRE Description

Adversaries may establish persistence and elevate privileges by using an installer to trigger the execution of malicious content. Installer packages are OS specific and contain the resources an operating system needs to install applications on a system. Installer packages can include scripts that run prior to installation as well as after installation is complete. Installer scripts may inherit elevated permissions when executed. Developers often use these scripts to prepare the environment for installation, check requirements, download dependencies, and remove files after installation.(Citation: Installer Package Scripting Rich Trouton)

Using legitimate applications, adversaries have distributed applications with modified installer scripts to execute malicious content. When a user installs the application, they may be required to grant administrative permissions to allow the installation. At the end of the installation process of the legitimate application, content such as macOS postinstall scripts can be executed with the inherited elevated permissions. Adversaries can use these scripts to execute a malicious executable or install other malicious components (such as a Launch Daemon) with the elevated permissions.(Citation: Application Bundle Manipulation Brandon Dalton)(Citation: wardle evilquest parti)(Citation: Windows AppleJeus GReAT)(Citation: Debian Manual Maintainer Scripts)

Depending on the distribution, Linux versions of package installer scripts are sometimes called maintainer scripts or post installation scripts. These scripts can include preinst, postinst, prerm, postrm scripts and run as root when executed.

For Windows, the Microsoft Installer services uses .msi files to manage the installing, updating, and uninstalling of applications. These installation routines may also include instructions to perform additional actions that may be abused by adversaries.(Citation: Microsoft Installation Procedures)

Attack Flow

1. Attacker gains the prerequisite access or context described below.
2. Attacker executes Installer Packages to achieve its tactical objective (Privilege Escalation, Persistence).
3. Resulting access/data/effect is leveraged to advance the broader attack chain (see Related Techniques).

Prerequisites

• Platform(s): Linux, macOS, Windows
• ATT&CK does not define one universal permission requirement for this technique. Establish the required access from the observed implementation and affected platform.

Common Tools

• Tool attribution is implementation-specific. Use ATT&CK procedure examples and local telemetry to identify the binaries, services, scripts, accounts, or cloud resources involved.

Commands

No universal command represents Installer Packages. Capture the exact command line, arguments, parent process, account, host, and execution time from the investigated environment; do not operationalize unverified examples.

Network Traffic

• Network observability is implementation-dependent. Review DNS, proxy, firewall, flow, authentication, and packet telemetry around the activity window, then correlate remote endpoints and protocol behavior with host evidence.

Windows Events

Sysmon Events

Detection Opportunities

No MITRE detection guidance published for this technique.

Relevant ATT&CK Data Sources: N/A

Sigma Rules

A universal Sigma rule would create unreliable results because this technique has no single guaranteed observable. Build detection logic from a documented behavior and supported data source, scope it to the affected platform, and validate it against benign administrative activity before deployment.

Splunk Queries

Start with the data sources named in the detection section. Scope searches by asset, identity, and time window; correlate the primary behavior with preceding access and subsequent actions. A portable query is intentionally not provided where the technique lacks a universal schema or observable.

Investigation Workflow

1. Confirm that the observed behavior is consistent with Installer Packages and rule out expected administrative or application activity.
2. Establish the first-seen time, initiating identity, source system, target system, and affected resources.
3. Collect relevant host, identity, network, cloud, and application telemetry for the surrounding time window.
4. Correlate parent and child activity, remote connections, file or configuration changes, and related ATT&CK techniques.
5. Determine scope by searching for the same observable across peer assets and identities.
6. Preserve volatile evidence and record confidence, assumptions, and telemetry gaps before containment.

Containment

1. Isolate affected host(s)/account(s) identified during investigation.
2. Revoke or rotate any credentials/tokens potentially exposed.
3. Apply the mitigations listed below where not already enforced.
4. Validate no related techniques (see Related Techniques) were chained against the same asset.

Mitigation

No MITRE mitigations mapped to this technique.

Related Techniques

• T1027
• T1041
• T1059.004
• T1071.001
• T1082
• T1218.007
• T1543.004
• T1546
• T1553.002