Skip to content

Red teaming tool PoC to dump LSASS memory, bypassing common countermeasures.

License

Notifications You must be signed in to change notification settings

0xdea/blindsight

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

29 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

blindsight

"There's no such things as survival of the fittest.
Survival of the most adequate, maybe.
It doesn't matter whether a solution's optimal.
All that matters is whether it beats the alternative."

-- Peter Watts, Blindsight (2006)

Red teaming tool to dump LSASS memory, bypassing common countermeasures. It uses Transactional NTFS (TxF API) to transparently scramble the memory dump, to avoid triggering AV/EDR/XDR.

Blog post:

See also:

Cross-compiling (macOS example)

$ brew install mingw-w64
$ rustup target add x86_64-pc-windows-gnu
$ cargo build --release --target x86_64-pc-windows-gnu

Usage

Inside an Administrator's PowerShell window:

C:\> .\blindsight.exe [dump | file_to_unscramble.log]

Examples

Dump LSASS memory:

C:\> .\blindsight.exe

Unscramble memory dump:

C:\> .\blindsight.exe 29ABE9Hy.log

Tested on

  • Microsoft Windows 10 (x64)
  • Microsoft Windows 11 (x64)
  • Microsoft Windows 11 (ARM64)
  • Microsoft Windows Server 2016 (x64)
  • Microsoft Windows Server 2019 (x64)
  • Microsoft Windows Server 2022 (x64)

Note: Do not test on production servers, as accessing LSASS might cause system instability!

TODO

About

Red teaming tool PoC to dump LSASS memory, bypassing common countermeasures.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages