Skip to content
Exploit the credentials present in files and memory
Branch: master
Clone or download
Latest commit 2642c51 Mar 17, 2017
Type Name Latest commit message Commit time
Failed to load latest commit information.
EYLR Power-Escalate 1.1 WIFI passwords Jan 8, 2017
GWMD Wanna dump in constrained mode Feb 14, 2016
PREZ InfoSecurity London 2016 talk Jun 10, 2016
PowerProcess PowerMemory 1.4.1 Jan 2, 2017
RECON Memory process file hashes Sep 17, 2016
RGPPP First commit Aug 29, 2015
RWMC PowerMemory 1.4.1 Jan 2, 2017
RWMCRS consolidation Jul 12, 2016
LICENSE PowerMemory added Jul 20, 2016
PowerMemory.ps1 PowerMemory 1.4.1 Jan 2, 2017 Create Mar 17, 2017

BlackHat Briefings 2017 BlackHat Arsenal 2016 License PowerShell Twitter


Exploit the credentials present in files and memory

PowerMemory levers Microsoft signed binaries to hack Microsoft operating systems.

What's New?

The method is totally new. It proves that it can be extremely easy to get credentials or any other information from Windows memory without needing to code in C-type languages. In addition, with this method we can modify the user land and kernel land behavior without being caught by antivirus or new defending techniques.

It can actually be done with 4GL language-type or with a script language like PowerShell which is installed everywhere.

With that being said, this technique implies that the detection is made hard due to the fact that we can do pretty much what we want by sending and receiving bytes.

User land attacks

  • Once the Debugger is initialized, PowerMemory interacts with it thanks to PowerShell.

User land deatures:

  • it's fully written in PowerShell
  • it can work locally as well as remotely
  • it can get the passwords of virtual machines without having any access to them (works for Hyper-V and VMware)
  • it does not use the operating system .dll to locate credentials address in memory but a Microsoft Signed Debugger
  • it does not use the operating system .dll to decipher passwords collected. PowerMemory maps the keys in the memory and cracks everything by itself (AES, TripleDES, DES-X)
  • it breaks undocumented Microsoft DES-X
  • it works even if you are on a different architecture than the target architecture
  • it leaves no trace in memory
  • a pull request is waiting to be integrated in PowerShell Empire (
  • it can manipulate memory to fool software and operating system
  • it can write the memory to execute shellcode without making any API call, it only sends bytes to write at specific addresses

Advanced shellcode writings

  • PowerMemory executes code by injecting bytes into a remote process and without help of API.

Hypervisor attacks

  • A hypervisor (VMWare or Microsoft Hyper-v) operator who does not own any rights into the Virtual Machines managed by the Hypervisor is, actually, the most powerful person in your organization. PowerMemory can get all the Virtual Machines passwords and lever the concept to get Domain Admin credentials.

Kernel land attacks

  • PowerMemory modifies Kernel structures to get advantages of the Operating System in order to achieve advanced persistence or elevate our privileges.

Real world – weaponization

  • You can use the module waiting to be integrated to leave Wonder Land and launch a crafted advanced attack with PowerShell Empire serving as the vector.
You can’t perform that action at this time.