All Projects → mandiant → flare-dbg

mandiant / flare-dbg

Licence: other
flare-dbg is a project meant to aid malware reverse engineers in rapidly developing debugger scripts.

Programming Languages

python
139335 projects - #7 most used programming language

Projects that are alternatives of or similar to flare-dbg

unicorn-libemu-shim
libemu shim layer and win32 environment for Unicorn Engine
Stars: ✭ 67 (-54.11%)
Mutual labels:  fireeye-flare
macOS-tools
No description or website provided.
Stars: ✭ 36 (-75.34%)
Mutual labels:  fireeye-flare
stringsifter
A machine learning tool that ranks strings based on their relevance for malware analysis.
Stars: ✭ 567 (+288.36%)
Mutual labels:  fireeye-flare
pycommands
PyCommand Scripts for Immunity Debugger
Stars: ✭ 35 (-76.03%)
Mutual labels:  fireeye-flare
flashmingo
Automatic analysis of SWF files based on some heuristics. Extensible via plugins.
Stars: ✭ 117 (-19.86%)
Mutual labels:  fireeye-flare
flare-wmi
No description or website provided.
Stars: ✭ 399 (+173.29%)
Mutual labels:  fireeye-flare
Flare Floss
FLARE Obfuscated String Solver - Automatically extract obfuscated strings from malware.
Stars: ✭ 2,020 (+1283.56%)
Mutual labels:  fireeye-flare
Commando Vm
Complete Mandiant Offensive VM (Commando VM), a fully customizable Windows-based pentesting virtual machine distribution. [email protected]
Stars: ✭ 5,030 (+3345.21%)
Mutual labels:  fireeye-flare
Flare Vm
No description or website provided.
Stars: ✭ 3,201 (+2092.47%)
Mutual labels:  fireeye-flare
flare-emu
No description or website provided.
Stars: ✭ 561 (+284.25%)
Mutual labels:  fireeye-flare
jitm
JITM is an automated tool to bypass the JIT Hooking protection on a .NET sample.
Stars: ✭ 27 (-81.51%)
Mutual labels:  fireeye-flare
remote lookup
Resolves DLL API entrypoints for a process w/ remote query capabilities.
Stars: ✭ 51 (-65.07%)
Mutual labels:  fireeye-flare
pivy-report
Poison Ivy Appendix/Extras
Stars: ✭ 16 (-89.04%)
Mutual labels:  fireeye-flare

Introduction

flare-dbg is a project meant to aid malware reverse engineers in rapidly developing debugger scripts.

Installation/setup

  1. Install the pykd windbg extension from: https://pykd.codeplex.com/releases
  2. Download the Bootstrapper dll.
  3. Add the Bootstrapper pykd.dll file into your winext directory. Something like %ProgramFiles%\Debugging Tools for Windows\winext.
  4. Install the latest 0.3.x version of pykd using pip install pykd.
  5. Ensure you can import pykd from within windbg: .load pykd.
  6. Install winappdbg
  7. pip install winappdbg
  8. Setup vivisect
  9. Install vivisect using one of the following options: 1. Install source using pip: pip install https://github.com/williballenthin/vivisect/zipball/master 2. Download and extract upstream vivisect and set PYTHONPATH to the extracted directory.
  10. Ensure you can import vivisect from a python shell: import vivisect.
  11. Setup flaredbg
  12. Install flaredbg using setup.py

Running scripts

There are two options for running scripts:

  1. Create a script directory and set PYTHONPATH to the newly created script directory and add your scripts here.
  2. Copy scripts to the root of your windbg directory. Something like: %ProgramFiles%\Debugging Tools for Windows\. Once your script path is setup, scripts are run from the windbg console as follows:
> .load pykd
> !py <script_name>

Installing and running plugins

The recommended way to install scripts is to add the plugins directory of this project to your PYTHONPATH. Another option is to follow the second option described above in the Running scripts section. Simply copy the plugin scripts to the root of your windbg directory.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].