Skip to main content
Mallory
Back to malware
MalwareRansomwareUsed by 12 actors

PowerSploit

PowerSploit is a PowerShell-based offensive security and post-exploitation framework. The content states that its modules are written in and executed via PowerShell and that it is commonly associated with behaviors such as reflective PE injection, shellcode execution, memory manipulation, and reflective injection. Referenced capabilities include WMI-based code execution via Invoke-WmiCommand; privilege-escalation and discovery functions in the Privesc-PowerUp modules, including querying Registry keys and discovering or exploiting DLL hijacking opportunities in services and processes; persistence via New-UserPersistenceOption, including Scheduled Task/Job creation; exfiltration and credential-harvesting modules, including use of Mimikatz; script compression and encoding through ScriptModification modules; microphone audio capture via Get-MicrophoneAudio; and multiple modules that search the Windows Registry for stored credentials, including Get-UnattendedInstallFile, Get-Webconfig, Get-ApplicationHost, Get-SiteListPassword, Get-CachedGPPPassword, and Get-RegistryAutoLogon. The content also associates PowerSploit with credential dumping from LSASS, keylogging, screen capture, scheduled tasks, and Group Policy Preferences discovery. PowerSploit has been obtained or used by multiple threat actors and campaigns cited in the content, including APT41, APT40, and others testing customized versions of open-source frameworks alongside Metasploit and Cobalt Strike. APT41 is specifically noted as using PowerSploit for persistence and as one of several offensive tools it obtained and used. The framework appears in detection and hunting contexts as attacker tooling frequently observed in PowerShell-heavy intrusions.

Share:
For your environment

Hunt this family in your stack

Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.

THREAT ACTORS

Groups observed using it

12 distinct threat actors attributed by public researchers. Open in Mallory to see the full evidence chain and overlapping campaigns.

View more details
TA505

APT41 has obtained and used tools such as Mimikatz, pwdump, PowerSploit, and Windows Credential Editor.

via mitre attack websiteattack.mitre.org
APT41

APT41 has obtained and used tools such as Mimikatz, pwdump, PowerSploit, and Windows Credential Editor.

via mitre attack websiteattack.mitre.org
FIN7

APT41 has obtained and used tools such as Mimikatz, pwdump, PowerSploit, and Windows Credential Editor.

via mitre attack websiteattack.mitre.org
UNC2447

"...offensive security tools such as Cobalt Strike, PowerSploit, Mimikatz, and Impacket..."

via talos intelligence blogblog.talosintelligence.com
LAPSUS$

"...offensive security tools such as Cobalt Strike, PowerSploit, Mimikatz, and Impacket..."

via talos intelligence blogblog.talosintelligence.com
SVR

“…additional tools, such as port scanner and PowerSploit, which it launched into memory…”

via cisa advisoriescisa.gov
MITRE ATT&CK

Techniques & procedures

23 distinct techniques documented for this family, organized by ATT&CK tactic.

Resource Development

1 technique
T1588.002ToolEvidence1

The content repeatedly states that threat actors 'obtained,' 'acquired,' or 'used' publicly available, open-source, legitimate, or modified tools such as Mimikatz, Cobalt Strike, PsExec, Empire, Impacket, and many others.

Initial Access

1 technique
T1566.001Spearphishing AttachmentEvidence1

Often deployed via spear phishing, they are lightweight, have particular capabilities and are designed to facilitate system identification and lateral movement.

Execution

7 techniques
T1047Windows Management InstrumentationEvidence1

The content repeatedly describes threat actors and malware using WMI/WMIC/wmiexec for remote execution, lateral movement, discovery, persistence, and administrative actions; e.g., 'APT41 used WMI in several ways, including for execution of commands via WMIEXEC as well as for persistence via PowerSploit' and 'Scattered Spider used Windows Management Instrumentation (WMI) to move laterally via Impacket.'

T1053Scheduled Task/JobEvidence2

Windows operating systems provide a utility (schtasks.exe) which enables system administrators to execute a program or a script at a specific given date and time. This kind of behavior has been heavily abused by threat actors and red teams as a persistence mechanism.

T1053.005Scheduled TaskEvidence3

References https://attack.mitre.org/techniques/T1053/ ... The persistence technique of scheduled tasks can be implemented both manually and automatically.

T1059Command and Scripting InterpreterEvidence3

Alternatively PowerShell can be used to create schedule tasks that will executed either at logon of a user or at a specific time and date.

T1059.001PowerShellEvidence14

Tested variants: Original compiled into PowerShell (Invoke-Mimikatz) (Detected) PowerSploit – Invoke-Mimikatz (Detected)

T1574Hijack Execution FlowEvidence1

This malicious DLL needs to be dropped in one of the folders that windows are loading DLL files. As it can be see below when the service restarted a Meterpreter session opened with SYSTEM privileges through DLL hijacking.

T1574.001DLLEvidence1

If these DLL’s doesn’t exist or are implemented in an insecure way (DLL’s are called without using a fully qualified path) then it is possible to escalate privileges by forcing the application to load and execute a malicious DLL file.

Persistence

4 techniques
T1053Scheduled Task/JobEvidence2

Windows operating systems provide a utility (schtasks.exe) which enables system administrators to execute a program or a script at a specific given date and time. This kind of behavior has been heavily abused by threat actors and red teams as a persistence mechanism.

T1053.005Scheduled TaskEvidence3

References https://attack.mitre.org/techniques/T1053/ ... The persistence technique of scheduled tasks can be implemented both manually and automatically.

T1112Modify RegistryEvidence1

Across the content, malware repeatedly 'adds Registry Run keys', 'creates Registry entries', 'modifies the Windows Registry', or 'overwrites registry keys' to maintain persistence.

T1547.001Registry Run Keys / Startup FolderEvidence3

APT32 established persistence using Registry Run keys, both to execute PowerShell and VBS scripts... Cobalt Group ... set a Startup path to launch the PowerShell shell command and download Cobalt Strike. DownPaper uses PowerShell to add a Registry Run key in order to establish persistence. | The content repeatedly describes malware and threat actors establishing persistence by adding values under HKCU/HKLM\Software\Microsoft\Windows\CurrentVersion\Run or RunOnce, and by placing executables, scripts, .lnk files, or .bat files in the Windows Startup folder.

Privilege Escalation

6 techniques
T1053Scheduled Task/JobEvidence2

Windows operating systems provide a utility (schtasks.exe) which enables system administrators to execute a program or a script at a specific given date and time. This kind of behavior has been heavily abused by threat actors and red teams as a persistence mechanism.

T1053.005Scheduled TaskEvidence3

References https://attack.mitre.org/techniques/T1053/ ... The persistence technique of scheduled tasks can be implemented both manually and automatically.

T1055Process InjectionEvidence4

Memory Manipulation • Reflection.Assembly • VirtualAlloc • WriteProcessMemory • CreateThread Why it matters: They are used in reflective PE injection, shellcode execution, etc. (common in frameworks like PowerSploit)

T1055.002Portable Executable InjectionEvidence1

Turla has also used PowerSploit's Invoke-ReflectivePEInjection.ps1 to reflectively load a PowerShell payload into a random process on the victim system.

T1547.001Registry Run Keys / Startup FolderEvidence3

APT32 established persistence using Registry Run keys, both to execute PowerShell and VBS scripts... Cobalt Group ... set a Startup path to launch the PowerShell shell command and download Cobalt Strike. DownPaper uses PowerShell to add a Registry Run key in order to establish persistence. | The content repeatedly describes malware and threat actors establishing persistence by adding values under HKCU/HKLM\Software\Microsoft\Windows\CurrentVersion\Run or RunOnce, and by placing executables, scripts, .lnk files, or .bat files in the Windows Startup folder.

T1548Abuse Elevation Control MechanismEvidence1

In Windows environments when an application or a service is starting it looks for a number of DLL’s in order to function properly... then it is possible to escalate privileges by forcing the application to load and execute a malicious DLL file.

Stealth

7 techniques
T1027Obfuscated Files or InformationEvidence1

The code is heavily obfuscated, via the use of position-independence alongside other techniques.

T1055Process InjectionEvidence4

Memory Manipulation • Reflection.Assembly • VirtualAlloc • WriteProcessMemory • CreateThread Why it matters: They are used in reflective PE injection, shellcode execution, etc. (common in frameworks like PowerSploit)

T1055.002Portable Executable InjectionEvidence1

Turla has also used PowerSploit's Invoke-ReflectivePEInjection.ps1 to reflectively load a PowerShell payload into a random process on the victim system.

T1218System Binary Proxy ExecutionEvidence1

One of most significant recent developments in sophisticated offensive operations is the use of “Living off the Land” (LotL) techniques by attackers. These techniques leverage legitimate tools present on the system, such as the PowerShell scripting language, in order to execute attacks.

T1574Hijack Execution FlowEvidence1

This malicious DLL needs to be dropped in one of the folders that windows are loading DLL files. As it can be see below when the service restarted a Meterpreter session opened with SYSTEM privileges through DLL hijacking.

T1574.001DLLEvidence1

If these DLL’s doesn’t exist or are implemented in an insecure way (DLL’s are called without using a fully qualified path) then it is possible to escalate privileges by forcing the application to load and execute a malicious DLL file.

T1620Reflective Code LoadingEvidence3

Memory Manipulation • Reflection.Assembly... Why it matters: They are used in reflective PE injection, shellcode execution, etc. (common in frameworks like PowerSploit)

Defense Impairment

1 technique
T1112Modify RegistryEvidence1

Across the content, malware repeatedly 'adds Registry Run keys', 'creates Registry entries', 'modifies the Windows Registry', or 'overwrites registry keys' to maintain persistence.

Credential Access

2 techniques
T1552.001Credentials In FilesEvidence1

This issue with this is that frequently the password is stored in clear-text within the script (such as a vbs file) which is often in SYSVOL.

T1558.003KerberoastingEvidence1

The Kerberoasting technique can be used to target and crack weak passwords of service accounts... the PowerSploit framework’s Invoke-Kerberoast utility is being used.

Discovery

2 techniques
T1012Query RegistryEvidence1

The content repeatedly describes malware and threat actors querying, enumerating, searching, reading, or checking Windows Registry keys and values, e.g., "ADVSTORESHELL can enumerate registry keys," "APT41 queried registry values to determine items such as configured RDP ports and network configurations," and "Reg may be used to gather details from the Windows Registry of a local or remote system at the command-line interface."

T1057Process DiscoveryEvidence1

The content repeatedly describes malware and threat actors obtaining lists of running processes, using utilities such as tasklist, ps, WMI, Get-Process, CreateToolhelp32Snapshot, EnumProcesses, and similar APIs/commands to enumerate active processes on victim systems.

Collection

1 technique
T1005Data from Local SystemEvidence2

The content repeatedly describes threat actors and malware collecting, stealing, identifying, copying, or staging files, documents, credentials, logs, databases, and other information from compromised hosts or local systems.

Command and Control

1 technique
T1105Ingress Tool TransferEvidence2

Download a file from a specified URL, and save it under a specified filename;

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets match these IOCs, which detections are missing, which campaigns to expect next, and what to do in the next 30 minutes.
IOC matching

Match every observed IP, domain, and hash against your live telemetry.

Threat actor attribution12

Named campaigns wielding this family, with evidence pinned to each claim.

Exploited vulnerabilities

CVEs this family uses for access and lateral movement.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

MITRE ATT&CK mapping23

Every documented technique, ranked by evidence weight.

Researcher chatter

Reddit, Mastodon, and CTI community discussion around this family.