From Collaborative RCE Tool Library
Categorized by Target Type
| Tool name: | AdmiralDebilitate |
| ||
|---|---|---|---|---|
| Author: | Admiral | |||
| Website: | http://www.ring3circus.com/downloads/admiraldebilitate | |||
| Current version: | 0.2 | |||
| Last updated: | June 16, 2008 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free / Open Source | |||
| Description: | AdmiralDebilitate is a tool for removing .NET strong name signing, particularly suited for large projects consisting of multiple nested dependencies. The interface is fairly simple: open up all relevant executables simultaneously (or all PEs if late-binding is in use) and ‘mark’ those that are to be modified. AdmiralDebilitate will determine the minimal area of the dependency tree that requires fixing and execute things appropriately. Any mismatching references will be listed in the ‘Problem Areas’ pane. Please report any bugs, after reading the following list of notes and caveats: * All dependencies on mscorlib and System.* are ignored. I don’t see why this should be a problem, but bear it in mind if something isn’t working. * Only exe and dll files are supported. * The tool searches only the current folder for DLLs referenced by the seeding assemblies. If the system is relying on environment variables being set or suchlike, then AdmiralDebilitate will probably fail to load all the assemblies. A workaround is to temporarily place all the files in the same directory. Updates: * 17/06/08 - A silly little fencepost error was causing problems with assemblies having AssemblyRef as their last table. That’s fixed in version 0.2. Thanks go out to Dan Pistelli, without whose .NET specification this wouldn’t have happened. | |||
| Also listed in: | .NET Signature Changers, .NET Signature Removers, Dependency Analyzer Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Class Informer |
| ||
|---|---|---|---|---|
| Author: | Sirmabus | |||
| Website: | http://www.openrce.org/blog/view/1344/Class_Informer_IDA_plug-in | |||
| Current version: | 1.01 | |||
| Last updated: | April 2, 2009 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free | |||
| Description: | Scans an MSVC 32bit target IDB for vftables with C++ RTTI, and MFC RTCI type data. Places structure defs, names, labels, and comments to make more sense of class vftables ("Virtual Function Table") and make them read easier as an aid to reverse engineering. Creates a list window with found vftables for browsing. RTTI ("Run-Time Type Identification"): http://en.wikipedia.org/wiki/RTTI RTCI ("Run Time Class Information") the MFC forerunner to "RTTI": http://msdn.microsoft.com/en-us/library/fych0hw6(VS.80).aspx ------------------------------------------------------------ See also screenshot example of vftable info set by plug-in below. | |||
| Also listed in: | COM Tools, IDA Extensions | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | EDB Linux Debugger |
| ||
|---|---|---|---|---|
| Author: | Evan Teran | |||
| Website: | http://www.codef00.com/projects.php#Debugger | |||
| Current version: | 0.9.10 | |||
| Last updated: | July 8, 2009 | |||
| Direct D/L link: | http://www.codef00.com/projects/debugger-0.9.10.tgz | |||
| License type: | GPL | |||
| Description: | Features * Intuitive GUI interface * The usual debugging operations (step-into/step-over/run/break) * Conditional breakpoints * Debugging core is implemented as a plugin so people can have drop in replacements. Of course if a given platform has several debugging APIs available, then you may have a plugin that implements any of them. * Basic instruction analysis * View/Dump memory regions * Effective address inspection * The data dump view is tabbed, allowing you to have several views of memory open at the same time and quickly switch between them. * Importing of symbol maps * Plugins o Search for binary strings o Code Bookmarks o Breakpoint management o Check for updates o Environment variable viewer o Heap block enumeration o Opcode search engine plugin has basic functionality (similar to msfelfscan/msfpescan) o Open file enumeration o Reference finder o String searching (like strings command in *nix) One of the main goals of this debugger is isolation of the debugger core from the display you see. The interface is written in QT4 and thus source portable to many platforms. The debugger core is actually a plugin and the platform specific code is isolated to just a few files, porting to a new OS would require porting these few files and implementing a plugin which implements the "DebuggerCoreInterface" interface. Also, because the plugins are based on the QPlugin API, and do their work through the DebuggerCoreInterface object, they are almost always portable with just a simple recompile. So far, the only plugin I have written which would not port with just a recompile is the heap analysis plugin, due to it's highly system specific nature. | |||
| Also listed in: | Debuggers, Linux Debuggers, Ring 3 Debuggers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Fenris |
| ||
|---|---|---|---|---|
| Author: | lcamtuf | |||
| Website: | http://lcamtuf.coredump.cx/fenris | |||
| Current version: | 0.07-m2 build 3245 | |||
| Last updated: | July 11, 2004 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free / Open Source | |||
| Description: | Fenris is a suite of tools suitable for code analysis, debugging, protocol analysis, reverse engineering, forensics, diagnostics, security audits, vulnerability research and many other purposes. The main logical components are: * Fenris: high-level tracer, a tool that detects the logic used in C programs to find and classify functions, logic program structure, calls, buffers, interaction with system and libraries, I/O and many other structures. Fenris is mostly a "what's inside" tracer, as opposed to ltrace or strace, tracers intended to inspect external "symptoms" of the internal program structure. Fenris does not depend on libbfd for accessing ELF structures, and thus is much more robust when dealing with "anti-debugging" code. * libfnprints and dress: fingerprinting code that can be used to detect library functions embedded inside a static application, even without symbols, to make code analysis simplier; this functionality is both embedded in other components and available as a standalone tool that adds symtab to ELF binaries and can be used with any debugger or disassembler. * Aegir: an interactive gdb-alike debugger with modular capabilities, instruction by instruction and breakpoint to breakpoint execution, and real-time access to all the goods offered by Fenris, such as high-level information about memory objects or logical code structure. * nc-aegir: a SoftICE-alike GUI for Aegir, with automatic register, memory and code views, integrated Fenris output, and automatic Fenris control (now under development). * Ragnarok: a visualisation tool for Fenris that delivers browsable information about many different aspects of program execution - code flow, function calls, memory object life, I/O, etc (to be redesigned using OpenDX or a similar data exploration interface). * ...and some other companion utilities. | |||
| Also listed in: | Reverse Engineering Frameworks, Linux Disassemblers, Linux Debuggers, Tracers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | IDA Pro |
| ||
|---|---|---|---|---|
| Author: | Ilfak Guilfanov | |||
| Website: | http://www.hex-rays.com/idapro | |||
| Current version: | 5.5 | |||
| Last updated: | June 15, 2009 | |||
| Direct D/L link: | N/A | |||
| License type: | Commercial | |||
| Description: | The IDA Pro Disassembler and Debugger is an interactive, programmable, extendible, multi-processor disassembler hosted on Windows or on Linux. IDA Pro has become the de-facto standard for the analysis of hostile code, vulnerability research and COTS validation. There is also a free (crippled) version available (IDA Pro Free). See its own entry in the library for more info. As of January 7, 2007, the official IDA Pro website moved from the old URL (http://www.datarescue.com/idabase) to the one listed above. | |||
| Also listed in: | .NET Disassemblers, Disassemblers, IPhone Tools, Linux Debuggers, Linux Disassemblers, Mobile Platform Debuggers, Mobile Platform Disassemblers, Ring 3 Debuggers, Symbian Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | radare |
| ||
|---|---|---|---|---|
| Author: | pancake | |||
| Website: | http://www.radare.org | |||
| Current version: | 1.4.1 | |||
| Last updated: | November 3, 2009 | |||
| Direct D/L link: | http://radare.nopcode.org/get/radare-1.4.1.tar.gz | |||
| License type: | GPL | |||
| Description: | <nowiki>The radare project aims to provide a complete unix-like toolchain for working with binary files. It currently provides a set of tools to work with x86, arm and java with some ones powerpc. The core is a raw hexadecimal editor for commandline with scripting features and perl/python extensions that gets extended with IO plugins that hooks the open/read/write/close/system calls. The debugger and disassembler has a code analysis module for x86, mips, arm and java. This way it's possible to draw graphs using Cairo on a GTK window or store the flow execution of a program on a log file and use the information to diff't against another trace or binary. The toolchain provides assemblers and disasemblers for x86, arm, mips (Loongson2F), sparc, CSR, m68k, powerpc, msil and java. The disassembler has been enhaced to handle inline comments, code block detections and flag references (data pointers or so). The debugger is mainly developed on linux and {Net | |||
| Also listed in: | .NET Disassemblers, Assemblers, Binary Diff Tools, Code Injection Tools, Debuggers, Disassemblers, Hex Editors, Java Disassembler Libraries, Linux Debuggers, Linux Disassemblers, Linux Tools, Memory Dumpers, Memory Patchers, Process Dumpers, Reverse Engineering Frameworks, Ring 3 Debuggers, String Finders, Symbol Retrievers, SysCall Monitoring Tools, Tracers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Rebel.NET |
| ||
|---|---|---|---|---|
| Author: | Daniel Pistelli | |||
| Website: | http://ntcore.com/rebelnet.php | |||
| Current version: | 1.3.0.1 | |||
| Last updated: | February 19, 2009 | |||
| Direct D/L link: | http://ntcore.com/Files/RebelDotNET.zip | |||
| License type: | Free | |||
| Description: | Rebel.NET is a rebuilding tool for .NET assemblies which is capable of adding and replacing methods and streams. It's possible to replace only a limited number of methods or every method contained in a .NET assembly. The simplicity of Rebel.NET consists in the replacing process: one can choose what to replace. For instance, one may choose to replace only the method code, instead of its signature or method header. The interface of Rebel.NET is quite a simple one. As input it requires a .NET assembly to be rebuilded and a Rebel.NET rebuilding file. The Rebel.NET file contains the data that has to be replaced in the original assembly. Rebel.NET can also create a Rebel.NET file from a given assembly. This is a key functionality, since some times the data of the original assembly has to be processed first to produce a Rebel.NET file for the rebuilding of the assembly. This sort of "report" feature can also be used to analyze the methods of an assembly, since reading the original data from a .NET assembly isn't as easy as reading a Rebel.NET file. It's possible to choose what should be contained in the Rebel.NET file. All the Rebel.NET features can used through command line, which comes very handy when an automated rebuilding process is needed. Rebel.NET is, mainly, a very solid base to overcome every .NET protection and to re-create a fully decompilable .NET assembly. As such, Rebel.NET has to be considered a research project, not an encouragement to violate licensing terms. | |||
| Also listed in: | .NET Code Injection Tools, .NET Executable Editors | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Reflector for .NET |
| ||
|---|---|---|---|---|
| Author: | Lutz Roeder (current owner Red Gate Software) | |||
| Website: | http://www.red-gate.com/products/reflector | |||
| Current version: | 5.1.4.0 | |||
| Last updated: | July 18, 2009 | |||
| Direct D/L link: | http://downloads.red-gate.com/reflector.zip | |||
| License type: | Free | |||
| Description: | From website: "Reflector is a very powerful class browser, explorer, analyzer and documentation viewer for .NET. Reflector allows to easily view, navigate, search, decompile and analyze .NET assemblies in C#, Visual Basic and IL." This is one of the most powerful .NET decompilers that you can't buy - just download :) Many of the popular commercial tools achieving the same goal "suddenly" got a boost when this masterpiece of work saw a daylights (and besides that those are commercial, still have hard time with obfuscators). Just give it a try, it will last literally five minutes - load some well known assembly of yours, choose target .NET language (!) and let'em work. Then compare it with the original. You'll surely not forget this one. | |||
| Also listed in: | .NET Decompilers, .NET Disassemblers, Decompilers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | SWF Reader |
| ||
|---|---|---|---|---|
| Author: | schizoM | |||
| Website: | http://realswfreader.sourceforge.net | |||
| Current version: | 1.2 | |||
| Last updated: | April 13, 2009 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free / Open Source | |||
| Description: | Advanced analysis/unpacking tool for Flash (SWF) files. | |||
| Also listed in: | Flash Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | WibuEmu |
| ||
|---|---|---|---|---|
| Author: | Sab, deepzone & xor37h | |||
| Website: | N/A | |||
| Current version: | ||||
| Last updated: | June 29, 2008 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free / Open Source | |||
| Description: | 1. Run wkdumpers for cipher text. 2. Place into gk_feal.c in knCipher array. 3. Solve the key (it should say ok passed). 4. Place solved ciphertext into bruteforce solver. (could take up to 4 days). 5. Place brutesolver values into emulator. 6. Any decent coder can take this source and make it really nice and friendly. I hope some of the hasp guys on this forum update it for mass use. Note: I suggest using test vectors already existing in sources. The .h file has them. Formz dumpdng. has sample vectors for gk_feal.c first for steps 1-5 to make sure you do it correctly. This code is borland, but easily ports. Source is old as dirt but too lazy to give you all the newer cleaner stuff. Have fun. Code can be optimized plenty, especially the solver (we already did but you can do it for fun). Newer wibus can be solved to with the extra 0xFF keysize. Thats for you guys to figure out. | |||
| Also listed in: | Dongle Crypto Solver Tools, Dongle Emulation Tools, Wibu Dongle Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | CFF Explorer |
| ||
|---|---|---|---|---|
| Author: | Daniel Pistelli | |||
| Website: | http://www.ntcore.com/exsuite.php | |||
| Current version: | 7.4.0.1 | |||
| Last updated: | June 11, 2008 | |||
| Direct D/L link: | http://www.ntcore.com/Files/CFF_Explorer.zip | |||
| License type: | Freeware | |||
| Description: | The CFF Explorer was designed to make PE editing as easy as possible, but without losing sight on the portable executable's internal structure. This application includes a series of tools which might help not only reverse engineers but also programmers. It offers a multi-file environment and a switchable interface. Also, it's the first PE editor with full support for the .NET file format. With this tool you can easily edit metadata's fields and flags. If you're programming something that has to do with .NET metadata, you will need this tool. The resource viewer supports .NET image formats like icons, bitmaps, pngs. You'll be able to analyze .NET files without having to install the .NET framework, this tool has its own functions to access the .NET format. Also includes a cool new scripting engine! | |||
| Also listed in: | .NET Executable Editors, PE Executable Editors | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Explorer Suite |
| ||
|---|---|---|---|---|
| Author: | Daniel Pistelli | |||
| Website: | http://ntcore.com/exsuite.php | |||
| Current version: | III | |||
| Last updated: | August 19, 2009 | |||
| Direct D/L link: | http://ntcore.com/Files/ExplorerSuite.exe | |||
| License type: | Free | |||
| Description: | A freeware suite of tools including a PE editor called CFF Explorer and a process viewer. The PE editor has full support for PE32/64. Special fields description and modification (.NET supported), utilities, rebuilder, hex editor, import adder, signature scanner, signature manager, extension support, scripting, disassembler, dependency walker etc. First PE editor with support for .NET internal structures. Resource Editor (Windows Vista icons supported) capable of handling .NET manifest resources. The suite is available for x86, x64 and Itanium. Features: * Process Viewer * Windows Viewer * PE and Memory Dumper * Full support for PE32/64 * Special fields description and modification (.NET supported) * PE Utilities * PE Rebuilder (with Realigner, IT Binder, Reloc Remover, Strong Name Signature Remover, Image Base Changer) * View and modification of .NET internal structures * Resource Editor (full support for Windows Vista icons) * Support in the Resource Editor for .NET resources (dumpable as well) * Hex Editor * Import Adder * PE integrity checks * Extension support * Visual Studio Extensions Wizard * Powerful scripting language * Dependency Walker * Quick Disassembler (x86, x64) * Name Unmangler * Extension support * File Scanner * Directory Scanner * Deep Scan method * Recursive Scan method * Multiple results * Report generation * Signatures Manager * Signatures Updater * Signatures Collisions Checker * Signatures Retriever | |||
| Also listed in: | .NET Executable Editors, .NET Resource Editors, .NET Signature Removers, .NET Tools, Dependency Analyzer Tools, Exe Analyzers, Executable CRC Calculators, Hex Editors, Import Editors, Memory Dumpers, PE Executable Editors, Process Dumpers, Protection Identifiers, Resource Editors | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | .NET DeObfuscator |
| ||
|---|---|---|---|---|
| Author: | Kurapica | |||
| Website: | http://www.woodmann.com/forum/showthread.php?t=11810 | |||
| Current version: | 0.5 | |||
| Last updated: | June 11, 2008 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free | |||
| Description: | This is a tool to deobfuscate names only in Assemblies, It doesn't deobfuscate control-flow. This tool is supposed to make our life easier when exploring in Reflector, so the deobfuscated assembly in most cases won't run and it's meant to be used in Reflector for analysis only. What this tool does is that it renames Classes and other member of assembly like Procedures and Fucntion into more understandable names for easier analysis, for example it renames a Class of type Form to "Class10_Form" instead of "xhfkd9oekfpklgpf" as we see in assemblies obfuscated with xenocode or any other obfuscator, I didn't want it to release it at first, but when I added type detection to renaming process it became more useful. | |||
| Also listed in: | .NET Deobfuscation Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | .NET Generic Unpacker |
| ||
|---|---|---|---|---|
| Author: | Ntoskrnl | |||
| Website: | http://ntcore.com/netunpack.php | |||
| Current version: | 1.0.0.1 | |||
| Last updated: | ||||
| Direct D/L link: | http://ntcore.com/Files/NETUnpack.zip | |||
| License type: | ||||
| Description: | This is a program to dump .NET packed applications. Of course no serious .NET protection relies on packing. In fact, this software shows how easily you can unpack a protected assemly. This .NET Generic Unpacker was written in a couple of hours and despite of the fact that it's very simple, it might turn useful having it: otherwise you have to unpack manually, which is also very easy. | |||
| Also listed in: | .NET Unpackers, Automated Unpackers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | .NET Hook Library |
| ||
|---|---|---|---|---|
| Author: | shokshok | |||
| Website: | http://dotnethook.sourceforge.net | |||
| Current version: | 2.1 | |||
| Last updated: | May 30, 2002 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free / Open Source | |||
| Description: | .Net Hook Library is a library (with a sample tool) to manipulate functions in a .NET Assembly. It allows for insertion of arbitrary code at the beginning of each function called in a .NET assembly (whether executable or assembly). Also provides code that reads through metadata and dumps information on it. The download contains detailed documentation about how it works and what it is. I'm in the process of converting this from an executable to a library. That way, existing applications can use it to modify the .NET binaries (a.k.a assemblies). | |||
| Also listed in: | .NET Code Injection Tools, Code Injection Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Bastard |
| ||
|---|---|---|---|---|
| Author: | ||||
| Website: | http://bastard.sourceforge.net | |||
| Current version: | 0.16 | |||
| Last updated: | 2002 | |||
| Direct D/L link: | N/A | |||
| License type: | Free / Open Source | |||
| Description: | The Bastard is a disassembler -- or, more appropriately, a disassembly environment. The idea is that you have an interpreter, much as you would in Perl or Python, which allows you to load files, disassemble them, dump the disassembly, write/run macros, and various other operations. The x86 instruction disassembler written for this project has been packaged seperately as libdisasm, and is intended to be used in other open source projects. This interpreter can be used interactively, it can be fed commands via STDIN [just like a scripting interpreter], and it can be communicated with via a pair of FIFOs. Now, on top of this any number of UI front ends can be stacked -- ncurses console front ends, Gtk X front-ends, Tk front ends, etc. It is the reponsibility of the front-ends to display the information obtained by querying the disassembler, supplying syntax highlighting, displaying strings, xrefs, etc; however the disassembler will retain all of this information, do all of the 'brute' processing, and will provide any of the information when requested. The bastard currently runs on x86 Linux and FreeBSD [CVS version]. It can disassemble x86 ELF, a.out, and PE files as well as flat binary files [.com, .bin]. | |||
| Also listed in: | Disassemblers, Linux Disassemblers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Burndump |
| ||
|---|---|---|---|---|
| Author: | ByteRage | |||
| Website: | http://www.securiteam.com/tools/5BP0H0U7PQ.html | |||
| Current version: | 1.0 | |||
| Last updated: | July 13, 2002 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free / Open Source | |||
| Description: | Burndump is a LKM that strips off the TESO Burneye protection from encrypted executables. You must be able to run the executable. When the program is unwrapped, you do not need the host-fingerprint or the password anymore and the ELF file can be reverse engineered without the Burneye anti-debugger tricks. | |||
| Also listed in: | Linux Unpackers, Automated Unpackers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Burneye |
| ||
|---|---|---|---|---|
| Author: | TESO | |||
| Website: | https://teso.scene.at/releases.php | |||
| Current version: | 1.0.1 | |||
| Last updated: | December 24, 2002 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free / Open Source | |||
| Description: | Burneye ELF encryption program, with full source and docs. | |||
| Also listed in: | Packers, Linux Packers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | COMRaider |
| ||
|---|---|---|---|---|
| Author: | David Zimmer | |||
| Website: | http://labs.idefense.com/software/fuzzing.php#more_comraider | |||
| Current version: | ||||
| Last updated: | November 8, 2006 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free | |||
| Description: | COMRaider is a tool designed to fuzz COM Object Interfaces. It can also extract information about them and their interfaces etc. Features include: * Capability to easily enumerate safe for scripting objects * Ability to scan for COM objects by path, filename, or guid * Integrated type library viewer * Integrated debugger to monitor exceptions, close windows,log api * External vbs script allows you to easily edit fuzzer permutations * Built in webserver to test exploits on the fly * Enumerate and view controls with killbit set * Distributed auditing mode to allow entire teams to work together * Ability to upload crash files to central server for group analysis * Automation tools allowing you to easily fuzz multiple libraries, individual classes, or specific functions. | |||
| Also listed in: | COM Debugging Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | COMView |
| ||
|---|---|---|---|---|
| Author: | japheth | |||
| Website: | http://www.japheth.de/COMView.html | |||
| Current version: | 2.98 | |||
| Last updated: | July 2007 | |||
| Direct D/L link: | http://www.japheth.de/Download/COMView.zip | |||
| License type: | Free | |||
| Description: | COMView is a tool for viewing and handling COM (Component Objects Model) things. It is intended to be used by programers, although it might also be useful for experienced end users. The following functions are included: * Shows COM related entries in the registry * Build in registry editor to modify these entries * Consistency check of COM related registry information * Shows type library information * Can generate ASM include files from type libraries * "Dispatch helper" ASM includes may be generated to simplify using IDispatch and events. * COM objects can be created and interfaces exposed are shown * OLE container is implemented allowing to view and test OLE/ActiveX controls * Object properties may be edited and methods be executed. * Object model exposed by an application/control may be walked. * May connect to source interfaces and display events Please note: to get benefits from using COMView it is expected to be familiar with COM basics, there is no tutorial included in COMView. | |||
| Also listed in: | COM Debugging Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | CSharpFuscator |
| ||
|---|---|---|---|---|
| Author: | papanyquiL | |||
| Website: | http://portal.b-at-s.info/news.php | |||
| Current version: | 1.0 | |||
| Last updated: | June 24, 2009 | |||
| Direct D/L link: | http://portal.b-at-s.info/request.php?275 | |||
| License type: | Free | |||
| Description: | The CSharpFuscator tool scrambles .NET source code to make it very difficult to understand or reverse-engineer. This provides significant protection for source code intellectual property, and even provides protection against the all-too-disassembly of .NET object code. | |||
| Also listed in: | .NET Packers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | CoClassSyms |
| ||
|---|---|---|---|---|
| Author: | Matt Pietrek | |||
| Website: | http://www.microsoft.com/msj/0399/comtype/comtype.aspx | |||
| Current version: | 1.0 | |||
| Last updated: | March 1999 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free / Open Source | |||
| Description: | "CoClass" in the "CoClassSyms" name refers to the TKIND_COCLASS entries in the typelib from which the symbols are created. CoClassSyms is a command-line program that operates on executable files containing a type library. This can be an .OCX or some other DLL such as MSHTML.DLL (which is a core component of Microsoft Internet Explorer). The output from CoClassSyms is either a .MAP or .DBG file. The code included with this article only supports .MAP file generation. However, if you drop in the DLL from this month's Under the Hood column, CoClassSyms generates a .DBG file instead. In either case, the output file has the same root file name as the input executable. Thus, running CoClassSyms on MSHTML.DLL creates MSHTML.MAP or MSHTML.DBG. Regardless of whether you make a .MAP or .DBG file, you'll no doubt want to get the debugger to recognize and load the symbol information. If you generate a .DBG file, make sure it is in the same directory as the associated executable. In my experience, the Visual Studio 6.0 debugger automatically loads the .DBG file as needed. Using WinDBG, I had to explicitly load the .DBG file in the command window. I wasn't able to get Visual Studio 5.0 to load the .DBG file, but I couldn't determine the cause of the problem. If everything goes well and the debugger loads your generated .DBG file, you should be able to set breakpoints by name on the methods. (Hint: you may want to first generate a .MAP file to get an idea of the available method names.) Of course, since you likely don't have source code for the executable, you'll be in the assembly language view when the breakpoints hit. You should also see method names in the call stack. | |||
| Also listed in: | COM Debugging Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | D3DLookingGlass |
| ||
|---|---|---|---|---|
| Author: | Admiral | |||
| Website: | http://www.ring3circus.com/gameprogramming/d3dlookingglass-v01 | |||
| Current version: | 0.1 | |||
| Last updated: | May 5, 2008 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free / Open Source | |||
| Description: | The topic of debugging full-screen Direct3D applications came up a little while ago. If you’ve ever tried it on a single-monitor setup (or even multi-monitor if the app wasn’t designed to handle it) then you’ll know how much of a pain it is. Windows just can’t handle focus being stolen from a suspended exclusive-mode program. The solution’s exactly what you’d expect - to intercept the relevant window- and device-creation calls and coax the debuggee into running in a window. This works, but fiddling with the calls manually each time you restart the process quickly gets boring. So here’s my first attempt at a generic solution. D3DLookingGlass is a DLL which, if injected into a Direct3D process early enough, will make sure that all video devices are created in windowed mode, allowing the hosting process to coexist with a debugger without any bother. If you can inject this DLL into the target process before the first call to CreateWindow, then everything should go smoothly. I think. Any later than this and your mileage may vary. I’ve also written a ‘loader’ program that installs the DLL as a system-wide CBT hook, so that you don’t need to inject it manually. This kind of worked for my limited set of test-cases, but there seems to be no Windows-hooks method of injecting a DLL globally and beating the call to CreateWindow. Windows installs the DLL containing the hook at the latest possible moment for its function, and I can find no type of hook that needs to be around before a window is created. I’d love for somebody to prove me wrong (or suggest another way to install the DLL system-wide), but by the looks of things, my loader is of limited use. In particular, I recall a situation where the game (Call Of Duty 4 Demo, I think) creates a non-overlapped window, which works fine for full-screen mode, but causes problems when you try force the device to bind as windowed. This will still be a problem unless the call to CreateWindow can be intercepted (and a well-formed window induced), which means that D3DLookingGlassLoader will struggle. Confirmation would be nice. Here’s the small-print: * The DLL hooks CreateWindowExW and ShowWindow in its DLLMain. I think this is kosher in terms of loader-lock, but it’s obviously not too cool with regard to system stability. Especially if it’s being installed in every running process. If d3d9.dll isn’t found in the address-space then the hooks fall straight through, so that shouldn’t be too much of a problem. But if it is found then all attempts to create or show (or hide) a window will be overridden - possibly to the demise of the process if it’s doing anything but the basic behaviour. So in all cases, watch out, and make sure you aren’t running anything important in the background (in particular, I’ve noticed that it doesn’t play nice with Firefox). * The loader uses a system-wide hook, and you hate system-wide hooks. I trust that anybody who needs this tool has some degree of technical expertise and is aware of the stability concerns inherent in installing somebody else’s barely-tested system-wide hook. * This was harder to put together than I anticipated, and that’s probably evident from the slightly shabby code. Again, I intend for this only to be used for debugging purposes, so you’ll have to forgive me for the sub-production-quality code. * Despite my focus on Direct3D, I’m not really a gamer and I don’t actually have any commercial games installed on this machine. So I only got a chance to test this against my own programs. Obviously, there are several ways to skin the metaphorical Direct3D-initialisation cat, so please leave a comment when you find a game that this chokes on. | |||
| Also listed in: | DirectX Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | DESkey Analysis |
| ||
|---|---|---|---|---|
| Author: | Sab & xor37h | |||
| Website: | N/A | |||
| Current version: | ||||
| Last updated: | ||||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free / Open Source | |||
| Description: | Very good analysis / documentation of DESkey, its PRNGs and inner workings, including some code. | |||
| Also listed in: | DESkey Dongle Tools, Dongle Crypto Solver Tools, Dongle Documentation | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | DXWnd |
| ||
|---|---|---|---|---|
| Author: | Nightwolve | |||
| Website: | N/A | |||
| Current version: | 1.20 | |||
| Last updated: | ||||
| Direct D/L link: | Locally archived copy | |||
| License type: | Freeware | |||
| Description: | Quote from readme: "Want to force a game or application into windowed mode that doesn't support it through its own interface? Now you can, to an extent. Results will vary depending on how your DirectX application was written." DirectX (D3D) applications are usually written to use full screen mode for their display. This makes debugging and target analysis difficult due to specific DirectX considerations. DXWnd attempts to force a D3D app to use windowed mode, making it much easier for reversers to work with. This app can't always force a full screen D3D app into windowed mode, however it is quick and easy to try. If this tool fails for you it's still perfectly possible to manually force windowed mode in your target. Search the Woodmann forum for further information. | |||
| Also listed in: | DirectX Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Damn Vulnerable Linux |
| ||
|---|---|---|---|---|
| Author: | Zero | |||
| Website: | http://www.DamnVulnerableLinux.org | |||
| Current version: | Damn Vulnerable Linux 1.5 (Infectious Disease) | |||
| Last updated: | January 26, 2009 | |||
| Direct D/L link: | http://www.computerdefense.org/dvl/DVL_1.5_Infectious_Disease.iso | |||
| License type: | Creative Commons Attribution-Noncommercial-Share Alike 3.0 License | |||
| Description: | Release date: 01/26/2009. Fixed many bugs (e.g. wrong postgres path), added several tools. This release contains 99% of all available Linux RCE tools! Damn Vulnerable Linux (DVL) is a Linux-based tool for IT-Security. Damn Vulnerable Linux (DVL) is highly integrated into the community project crackmes.de (http://www.crackmes.de) and is frequently updated with new community provided lessons. Damn Vulnerable Linux (DVL) is your place either to get the latest Damn Vulnerable Linux (DVL) distribution, to get new lessons, or to submit own lessons based on the Damn Vulnerable Linux (DVL) training system. The constant website for Damn Vulnerable Linux (DVL) is located at http://www.damnvulnerablelinux.org . Damn Vulnerable Linux (DVL) is for educational purposes only! Actually, it is a perverted Linux distribution made to be as insecure as possible. It is collection of IT-Security tools. Additional it includes a fullscaled lesson based environment for Attack & Defense on/for IT systems for self-study or teaching activities during university lectures. It's a Live Linux Distro, which means it runs from a bootable CD in memory without changing the native operating system of the host computer. As well it can be run within virtual machine environments, such as qemu or vmware. There is no need to install a virtual machine if you use the embedded option. Its sole purpose in life is to put as many security tools at your disposal with as much training options as it can. It contains a huge ammount of lessons including lesson description - and solutions if the level has been solved by a community member at crackmes.de. Damn Vulnerable Linux (DVL) is meant to be used by both novice and professional security personnel but is not ideal for the Linux uninitiated. Damn Vulnerable Linux (DVL) assumes you know the basics of Linux as most of your work will be done from the command line. If you are completely new to Linux, it's best you stop playing with this system. | |||
| Also listed in: | Linux Tools, Reverse Engineering Frameworks | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Deblector |
| ||
|---|---|---|---|---|
| Author: | Felice Pollano, Matthew Yee | |||
| Website: | http://www.codeplex.com/deblector | |||
| Current version: | 1.0 | |||
| Last updated: | August 31, 2007 | |||
| Direct D/L link: | http://www.codeplex.com/Project/Download/FileDownload.aspx?ProjectName=deblector&DownloadId=18153 | |||
| License type: | Free / Open Source | |||
| Description: | Plug-in for .NET Reflector that allows you to debug .NET processes from within .NET Reflector. | |||
| Also listed in: | .NET Debuggers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Direct3D Hooking |
| ||
|---|---|---|---|---|
| Author: | Admiral | |||
| Website: | http://www.ring3circus.com/downloads/direct3d-hooking | |||
| Current version: | 1.1 | |||
| Last updated: | November 27, 2007 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free / Open Source | |||
| Description: | A sample for hooking a Direct3D 9 program and drawing on its viewport. Translating this to Direct3D 8 should be trivial. Notes: * Vista support added with version 1.1 * This is not safe for 64-bit consumption, though that should be obvious. * While there’s no reason it can’t be made to work with Unicode, I’ve written everything in ASCII, for simplicity. * By default, the DLL will increase its own reference count to prevent it being unloaded prior to termination of the host process. This is because there is a small risk of the DLL being unloaded by one thread, while a hooked function in another returns to the now dead memory. I figured that it’s best to waste a little bit of everybody’s memory than to crash unnecessarily. * The d3d9.dll function addresses (and prologues) are hard-coded, or at least their offsets are. While this may look very unprofessional and rather risky, I can assure you that it’s quite safe. The alternative would be to hack up some virtual-function tables and that’s a whole other story for a whole other post. * You may notice that the compiled DLL is dependent upon D3DX. This isn’t necessary for the hook itself, but I used ID3DXFont in my example for demonstrative purposes. The only reason I mention this is that there is no way to guarantee the existence of any D3DX DLLs on a DirectX 9 machine, and distributing them yourself is in violation of the DirectX Runtime EULA. So if you happen to need to distribute this code, you’ll either need to carry the huge runtime installer around, or avoid using D3DX altogether. * The soft-hooks used here will cause problems with PunkBuster if applied to any of its monitored functions. If you need to do this then you’ll have to be a bit cleverer. * The source assumes that the graphics device will never become invalid. If you suspect that this isn’t the case (which will be true for any full-screen game at a minimum) then you’ll need to add the appropriate sanity checks (see IDirect3DDevice9::TestCooperativeLevel) before attempting to render anything, lest you want to crash and burn. | |||
| Also listed in: | DirectX Tools, Code Injection Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | DisasMSIL |
| ||
|---|---|---|---|---|
| Author: | Daniel Pistelli | |||
| Website: | http://ntcore.com/Files/disasmsil.htm | |||
| Current version: | 1.0 | |||
| Last updated: | April 30, 2008 | |||
| Direct D/L link: | http://ntcore.com/Files/disasmsil/DisasMSIL.zip | |||
| License type: | Free / Open source | |||
| Description: | DisasMSIL is a free/open disasm engine for the Microsoft Intermediate Language (MSIL). You can use it any context you wish. There are no license restrictions. The only thing I ask you to do is to send me your bug fixes (if any). Note: Don't rely on the ECMA specification (Partition III: Common Language Infrastructure), since it's incomplete. Some new opcodes were introduced with the .NET Framework 2.0. | |||
| Also listed in: | .NET Disassembler Libraries | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | DotFuckScator v1.3 |
| ||
|---|---|---|---|---|
| Author: | LibX | |||
| Website: | http://www.reteam.org/tools.html | |||
| Current version: | v1.3 | |||
| Last updated: | May 9, 2009 | |||
| Direct D/L link: | http://reteam.org/tools/tf35.zip | |||
| License type: | Free | |||
| Description: | DotFuckScator.V1.3 DotFuckScator is a reversing engineering tool used to remove string encryption from dotfuscator protected files If the original file was strong name signed DotFuckScator will create a new keypair and re-sign the file with this pair, be carefull since file depending on this file will need to be edited manualy to support the new strong name signature. You can use RE-Sign for this and the editor of your choice Also if you like the file re-signed with a specific key place your key in the same folder as the file you are about to process and rename it to DotFuckScator.snk now DotFuckScator will use this key for the re-sign process. Hope this tool is of any use Changes: * v1.1 has a minor bugfix that prevented some strings from proper decrypting * v1.2 small bugfix in re-signing, added indicator to show the amount of strings decrypted so far * v1.3 Fixed royal fuck-up in string decryption code replacement function meaning the output will now run after string decryption removal ;x | |||
| Also listed in: | .NET Disassemblers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | DotNET Tracer |
| ||
|---|---|---|---|---|
| Author: | Kurapica | |||
| Website: | http://www.woodmann.com/forum/showthread.php?t=11859 | |||
| Current version: | 0.6 | |||
| Last updated: | June 15, 2009 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free | |||
| Description: | This is a simple tool that has a similar functionality to RegMon or FileMon but it's designed to trace events in .NET assemblies in runtime, many events can be reported so you can understand what's going on in the background. 1- Select the assembly you want to analyze 2- Set the Events Mask, i.e Events you want to catch 3- Click "Start" I hope it's useful and as always bug reports are welcome. | |||
| Also listed in: | .NET Tracers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | dotNet Protector Win32 |
| ||
|---|---|---|---|---|
| Author: | PV Logiciels | |||
| Website: | http://dotnetprotector.pvlog.com/Fonctions.aspx | |||
| Current version: | 5.4 | |||
| Last updated: | November 8, 2008 | |||
| Direct D/L link: | http://dotnetprotector.pvlog.com/downloads/dotnetprotector5/dotNetProtectorX86.msi | |||
| License type: | Commercial (with full featured trial) | |||
| Description: | dotNet Protector is a powerful .NET code protection system that prevents your assemblies from being decompiled. With dotNet Protector, your application is not simply obfuscated, but method bodies are encrypted. EXE DLL, ASPNET and SQL assemblies can be protected. You can protect a whole application (main exe, referenced dlls) in a single executable. Your .NET code will run entirely from memory, without temporary disk storage. Protection can be done interactively with an intuitive graphical interface, or automated, using the command-line functionalities of dotNet Protector. dotNet Protector includes a powerful hardware sensitive anti-piracy system and extensions to help you develop your own software activation system. dotNet Protector is self-protected and uses its internal software activation system. | |||
| Also listed in: | .NET Packers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | dotNet Sniffer Win32 |
| ||
|---|---|---|---|---|
| Author: | PV Logiciels | |||
| Website: | http://dotnetprotector.pvlog.com/Tools.aspx | |||
| Current version: | 2.0 | |||
| Last updated: | November 8, 2008 | |||
| Direct D/L link: | http://dotnetprotector.pvlog.com/downloads/dotNetSnifferWin32.msi | |||
| License type: | Free | |||
| Description: | dotNet Sniffer 2 uses the .NET profiler API to save assemblies loaded from memory. Once a module is handled by the .NET Framework, dotNet Sniffer saves it to disc if it was loaded from memory. Some tools are changing the module (decrypt methods ...) after loading; dotNet Sniffer allows you to save the module again during the execution of the first method (JIT). The profiler will be active only for the process to start; installing dotNet Sniffer will not affect the performance of other .NET programs. dotNet Sniffer 2 is available for 32-bit and 64-bit processors. 64-bit versions also install the 32-bit profiler and can save indifferently 32-bit and 64-bit processes. If you use 64-bit Windows, install only the 64-bit version suitable for your processor. | |||
| Also listed in: | .NET Tools, .NET Unpackers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | dotNetTools Win32 |
| ||
|---|---|---|---|---|
| Author: | PV Logiciels | |||
| Website: | http://dotnetprotector.pvlog.com/Tools.aspx | |||
| Current version: | 1.0 | |||
| Last updated: | November 8. 2008 | |||
| Direct D/L link: | http://dotnetprotector.pvlog.com/downloads/dotNetToolsWin32.msi | |||
| License type: | Free | |||
| Description: | dotNet Tools is a freeware suite that includes dotNet Sniffer, PvLog DeObfuscator and PvLog LicenseManagerKiller. dotNet Sniffer uses the .NET profiler API to save assemblies loaded from memory. PvLog Deobfuscator is a MSIL code optimizer that makes more readable obfuscated code. LicenseManagerKiller is a tool that removes LicenseProvider attributes in the assembly. | |||
| Also listed in: | .NET Deobfuscation Tools, .NET Tools, .NET Unpackers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Dotnet IL Editor (DILE) |
| ||
|---|---|---|---|---|
| Author: | zsozsop | |||
| Website: | http://sourceforge.net/projects/dile | |||
| Current version: | 0.2.6 | |||
| Last updated: | September 30, 2007 | |||
| Direct D/L link: | N/A | |||
| License type: | Free / Open Source | |||
| Description: | Dotnet IL Editor (DILE) is an editor program which helps modifying .NET assemblies. It is intended to be able to disassemble .NET assemblies, modify the IL code, recompile it and run inside a debugger. | |||
| Also listed in: | .NET Debuggers, .NET Disassemblers, .NET Executable Editors | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | ERESI Framework |
| ||
|---|---|---|---|---|
| Author: | The ERESI Project | |||
| Website: | http://www.eresi-project.org | |||
| Current version: | 0.8a23 | |||
| Last updated: | November 30, 2007 | |||
| Direct D/L link: | N/A | |||
| License type: | Free / Open Source | |||
| Description: | The ERESI Reverse Engineering Software Interface is a unified multi-architecture binary analysis framework targeting operating systems based on the Executable & Linking Format (ELF) such as Linux, *BSD, Solaris, HP-UX, IRIX and BeOS. ERESI is a general purpose hybrid framework : it includes both static analysis and runtime analysis capabilities. These features are accessed by primitives of the ERESI reverse engineering language which makes the framework more adaptable to the precise needs of her users. It brings an environment of choice for program analysis throught instrumentation, debugging, and tracing as it also provides more than ten exclusive major built-in features . ERESI can also be used for security auditing, hooking, integrity checking or logging binary programs. The project prones modularity and reusability of code and allows users to create their own project on top of the ERESI language interpreter in just a few lines. Among other features, the base code can display program graphs on demand using its automated flow analysis primitives. Our tools are enhanced for hardened or raw systems which have no executable data segments and no native debug API or even explicit program information. The ERESI framework includes: * The ELF shell (elfsh), an interactive and scriptable ERESI interpreter dedicated to instrumentation of ELF binary files. * The Embedded ELF debugger (e2dbg), an interactive and scriptable high-performance userland debugger that works without standard debug API (namely without ptrace). * The Embedded ELF tracer (etrace), an interactive and scriptable userland tracer that works at full frequency of execution without generating traps. * The Kernel shell (kernsh), an interactive and scriptable userland ERESI interpreter to inject code and data in the OS kernel, but also infer, inspect and modify kernel structures directly in the ERESI language. * The Evarista static analyzer, a work in progress ERESI interpreter for program transformation and data-flow analysis of binary programs directly implemented in the ERESI language (no web page yet). Beside those top-level components, the ERESI framework contains various libraries that can be used from one of the previously mentioned tools, or in a standalone third-party program: * libelfsh : the binary manipulation library on which ELFsh, E2dbg, and Etrace are based. * libe2dbg : the embedded debugger library which operates from inside the debuggee program. * libasm : the disassembly engine (x86 and sparc) that gives semantic attributes to instructions and operands. * libmjollnir : the code fingerprinting and graph manipulation library. * librevm : the Reverse Engineering Vector Machine, that contains the meta-language interpretor and the standard ERESI library. * libaspect : the type system and aspect library. It can define complex data-types to be manipulated ad-hoc by ERESI programs. * libedfmt : the ERESI debug format library which can convert dwarf and stabs debug formats to the ERESI debug format by automatically generating new ERESI types. | |||
| Also listed in: | Reverse Engineering Frameworks, Linux Debuggers, Linux Disassemblers, Tracers, Code Injection Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Eutron Smartkey Reader |
| ||
|---|---|---|---|---|
| Author: | cEnginEEr | |||
| Website: | N/A | |||
| Current version: | ||||
| Last updated: | July 21, 2007 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free | |||
| Description: | Here is a small utility I coded for reading some info of a smartkey dongle; 1. Type & Model 2. Label & Password 3. Serial number 4. IdCode (undocumented) 5. Scramble LFSR (undocumented) 6. Hidden signature (undocumented) | |||
| Also listed in: | Dongle Dumper Tools, SmartKey Dongle Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | FREN |
| ||
|---|---|---|---|---|
| Author: | LLXX | |||
| Website: | N/A | |||
| Current version: | 1.0 | |||
| Last updated: | July 27, 2007 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free | |||
| Description: | SWF Encrypt unprotector | |||
| Also listed in: | Automated Unpackers, Flash Unpackers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Flasm |
| ||
|---|---|---|---|---|
| Author: | Igor Kogan | |||
| Website: | http://flasm.sourceforge.net | |||
| Current version: | 1.62 | |||
| Last updated: | June 15, 2007 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free / Open Source | |||
| Description: | Flasm is a free command line assembler/disassembler of Flash ActionScript bytecode. It lets you make changes to any SWF. Flasm fully supports SWFs produced by Macromedia Flash 8 and earlier Flash versions. Flasm disassembles your entire SWF including all the timelines and events. Looking at disassembly, you learn how the Flash compiler works, which improves your ActionScript skills. You can also do some optimizations on the disassembled code by hand or adjust the code as you wish. Flasm then applies your changes to the original SWF, replacing original actions. It's also possible to embed Flasm actions in your ActionScript, making optimizing of large projects more comfortable. Flasm is not a decompiler. What you get is the human readable representation of SWF bytecodes, not ActionScript source. If you're looking for a decompiler, Flare may suit your needs. However, Flare can't alter the SWF. | |||
| Also listed in: | Flash Disassemblers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | GUID-Finder |
| ||
|---|---|---|---|---|
| Author: | Sirmabus | |||
| Website: | http://www.openrce.org/repositories/users/Sirmabus | |||
| Current version: | 1.0b | |||
| Last updated: | January 17, 2008 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free / Open Source | |||
| Description: | A GUID/UUID finding/fixing IDA plug-in. The COM side of RE'ing (at least with "dead listing") can be pretty elusive. With this you can at least partially glean what interfaces and classes a target is using. This plug-in scans the IDB for class and interfaces GUIDs and creates the matching structure with label. IDA can find these on it's own, but it often misses them, so this can fill in the gap. Plus this plug-in allows you to easily add custom declarations, and is handy to do a general audit for such GUIDs. This is based Frank Boldewin's IDA Python script that you can find here: http://www.openrce.org/downloads/details/250/ClassAndInterfaceToNames or off his home page: http://www.reconstructer.org/code/ClassAndInterfaceToNames.zip It's a great utility, I found me self using it regularly. But I wanted one that wasn't dependant on IDA Python, and one that might be a bit faster. I've made some enhancements too (see below). Some interesting reading: http://en.wikipedia.org/wiki/Globally_Unique_Identifier http://en.wikipedia.org/wiki/UUID [How to run it] Just invoke it using your selected IDA hot-key, or from "Edit->Plugins". Normally you will want to keep the ""Skip code segments for speed"" check box checked, because it can make a big difference in the run time. With unchecked, code segments are also scanned. You'll want to scan the code to if the target is a Delphi, or others where data tends to be code/.text segment, or if you just want to be more thorough. It might take some time to scan everything depending on the size of the IDB your computer, etc.. When it's done, you should see a list of interfaces and classes in the IDA log window. If you want to go look at a particular entry to RE (to look at xrefs, etc.) just click on the line and IDA will jump to it. [How it works] 1. Loads in GUID/UUID defs for the two text files "Interfaces.txt" and "Classes.txt". A little enhancement here over Frank's format, you can have blank lines and have comments prefixed with '#' (first char, whole line only. Not a very forgiving parser). In the source is "DumpLib", a utility I created to parse LIB files (like "uuid.lib") to gather more GUIDs. As of this build, it's a collection of Frank's original UUIDs plus all the ones to be found in VS2005 libraries along with DirectX 9.1,. There could be more explicitly created in header (.h/.hpp) files but have yet to make a utility to parse them. If you want to add custom GUID defines (from 3rd party software, etc.), just edit these text files manually. 2. After it loads in the defs, the plug-in iterates through all segments in your currently open IDB. By default it will skip code/".text" segments, and import/export segments for speed. Usually you find GUIDs in the ".rdata", and ".data" segments. I originally intended to sort all the GUIDs by similarity and search with partial wild cards for speed. If you take a look at the GUID defs you will see that many GUIDs share common numbers that often differ only be the least significant digits ("Data4"). At least in theory, searching for groups wild cards should make searching faster. Maybe next version.. [Known problems/issues/limitations] 1. If a given GUID 16byte def just so happens to match something that is not really a GUID, the plug-in will try to convert it to one regardless (another reason not to run it over code sections). So far I have not found this to be much of issue, although it could be. Could add a confirm dialog for each to let the user decide. 2. Some GUID set operations will fail. This is usually because something is bad/wrong at the particular address; like a partial code def, or incorrect xref. The plug-in will display most of these errors in the IDA log window for manual correction. 3. TODO: Other GUID times like "DIID", "LIBID", "CATID", usefull? | |||
| Also listed in: | COM Debugging Tools, IDA Extensions | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Key-lok II C++ library IDA Signatures |
| ||
|---|---|---|---|---|
| Author: | prt | |||
| Website: | N/A | |||
| Current version: | rev1 | |||
| Last updated: | July 5, 2007 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free | |||
| Description: | IDA Signature: Key-lok II C++ library version: rev1 | |||
| Also listed in: | Dongle IDA Signatures, IDA Signatures, KEYLOK Dongle Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | KeyLok Dumper & Seed Calculator |
| ||
|---|---|---|---|---|
| Author: | Sab | |||
| Website: | http://www.woodmann.com/forum/showthread.php?t=10331 | |||
| Current version: | ||||
| Last updated: | July 30, 2007 | |||
| Direct D/L link: | N/A | |||
| License type: | Free / Open Source | |||
| Description: | Here is some old hacked up code I found. I figured I would release it so I can be uber leet one day too. keylokdumper.cpp will dump memory contents, and klcalc will calculate codes for you. I included algo.txt which are the algos of the keylok dongle. Klcalc.exe if you're lazy (I think a bug in it?) and that should do it. I didn't bother making the code pretty, nice, user friendly, or even good. It is just some proof of concepts that can be modded into an elegant solution if you choose too. I do not care about bugs, suggestions, or alterations so don't bother me with them. I do take thanks, hellos and gifts though. Some people might find this useful, some might archive them since they are collectors. Anyways, I might release more stuff later on when bored. | |||
| Also listed in: | Dongle Crypto Solver Tools, Dongle Dumper Tools, KEYLOK Dongle Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | lida |
| ||
|---|---|---|---|---|
| Author: | Mario Schallner | |||
| Website: | http://lida.sourceforge.net | |||
| Current version: | 00.03.00 | |||
| Last updated: | December 5, 2004 | |||
| Direct D/L link: | N/A | |||
| License type: | Free / Open Source | |||
| Description: | lida is basically a disassembler and code analysis tool. It uses the bastards libdisasm for single opcode decoding (see http://bastard.sourceforge.net/libdisasm.html). It allows interactive control over the generated deadlisting via commands and builtin tools. Short Overview of (planned) features: * ELF, RAW file disassembly (generating stringtable, symboltable, crossreferences, ... ) * trace execution flow of binary * work with symbolic names: interactive naming of functions, labels, commenting of code * scan for known anti-debugging, anti-disassembling techniques * scan for user defined code sequences * integrated patcher * integrated cryptoanalyzer * handy ("intelligent") browsing * openssl support (customizeable "init values", apply to programs datablocks) Why lida? The project lida was initiated because of the lack of handy reverse engineering software for linux. Therefore it is designed to (and should) fit several needs of some typical reverse-engineering sessions. lida addresses people who like to work on deadlistings, and should be especially useful for people with previous experience in windows reverse engineering. lida should be a good "entry point" for examining the "new targets". A typical use is to run it while debugging your program and comment the deadlisting / name functions with the information gathered. So basically it is a disassembler. Why another one? :) Many disassemblers out there use the output of objdump - lida tries a more serious approach. The several limitations of objdump (see 3.1) are broken by using libdisasm (thx to HCUNIX!), and by tracing the execution flow of the program. Further, by having the control over the disassembly - more features can be included. Everybody who has already worked on some deadlisting will immediate feel a need to work interactive with the code - and be able to change it. Therefore lida will have an integrated patcher, resolves symbolic names, provides the ability to comment the code, serves efficient browsing methods, ... The more exotic features of lida should be on the analysis side. The code can be scanned for custom sequences, known antidebugging techniques, known encryption algorithms, ... also you will be able to directly work with the programs data and for example pass it to several customizable en-/decryption routines. This of course only makes limited sense as it is not a debugger. Tough often I really missed this functionality. | |||
| Also listed in: | Disassemblers, Linux Disassemblers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Linice |
| ||
|---|---|---|---|---|
| Author: | Goran Devic | |||
| Website: | http://www.linice.com | |||
| Current version: | 2.6 | |||
| Last updated: | July 28, 2005 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | GPL | |||
| Description: | What is Linice? Linice is an Intel x86-based, Linux source-level kernel debugger with the look and feel of SoftIce for MS Windows. Linice is designed to be used by the people who have SoftIce experience. Linice provides a major subset of SoftIce commands, and adds a few new ones. For that reason the documentation describing individual commands is not provided. There are a number of good resources on the Web that describe all SoftIce commands (Google "SoftIce" keyword.) What can I use it for? You can use Linice to debug a kernel module or a user application. You can also debug a Linux kernel. Kernel does not need to be recompiled or patched in any way. The debugger proper loads as a module into the running kernel and supports debugging using the following devices: local VGA frame buffer X-Window remote serial terminal monochrome monitor You can break into a running kernel at any time by a hotkey. Place breakpoints, single step, watch variables etc. Multiple international keyboard layouts are supported. | |||
| Also listed in: | Linux Debuggers, Ring 0 Debuggers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | MSIL Dumper |
| ||
|---|---|---|---|---|
| Author: | Kurapica | |||
| Website: | http://www.woodmann.com/forum/showthread.php?t=11809 | |||
| Current version: | 0.4 | |||
| Last updated: | December 12, 2008 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free | |||
| Description: | The idea of this tool is to achieve two objects: 1 - It will dump the body of every Method (Function, Procedure) called by the executable assembly you select, The dumping occurs whenever compiler enters that method, for example if you Click some button and this button calls method "CheckLicense" then you will find a file named "CheckLicense.txt" in the "\Dump" folder. 2 - It will show you in details the methods being called and also the modules that your application loads so it could be used as a simple tracing utility for .net assemblies. I wrote this tool to help me rebuild assemblies protected with JIT hooking technique, those assemblies can't be explored in Reflector because their methods' body is encrypted and only decrypted in runtime when the method is called so you will see no code in reflector, I assumed that I will have access to the encrypted MSIL code of the methods using Profiling APIs, there was a 50% chance of success but it turned out to be only useful against certain protections like the one that LibX coded which depends on System.Reflection.Emit.DynamicMethod to excute protected methods. you can find more on LibX protection here hxxp://www.reteam.org/board/showthread.php?t=799 | |||
| Also listed in: | .NET MSIL Dumpers, .NET Tracers, Tracers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Matrix Dongle 2.6.0 IDA Signatures |
| ||
|---|---|---|---|---|
| Author: | Sope | |||
| Website: | N/A | |||
| Current version: | ||||
| Last updated: | September 13, 2008 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | ||||
| Description: | Recently, while RE an target I had to create IDA signature file for Matrix Dongle ver 2.6.0 hence uploaded here. It will help you to identify many fucntions. | |||
| Also listed in: | Dongle IDA Signatures, Matrix Dongle Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Matrix Dongle C++ library IDA Signatures |
| ||
|---|---|---|---|---|
| Author: | prt | |||
| Website: | N/A | |||
| Current version: | rev1 | |||
| Last updated: | August 5, 2007 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free | |||
| Description: | IDA Signature: Matrix Dongle C++ library version: rev1 2007.08.05 rev1: Matrix SDK v2.60 | |||
| Also listed in: | Dongle IDA Signatures, IDA Signatures, Matrix Dongle Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | MetaPuck |
| ||
|---|---|---|---|---|
| Author: | y0da | |||
| Website: | http://y0da.cjb.net | |||
| Current version: | 1.0 | |||
| Last updated: | 2005 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free / Open Source | |||
| Description: | MetaPuck is a tool to spy the information, being hidden in the MetaData block inside the CLR (Common Language Runtime) Portable Executeable images of the .NET framework, and displays it in a well overlookable TreeView. It also parses .NET "typelibs". Included full source code. | |||
| Also listed in: | COM Debugging Tools, .NET Executable Editors | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | MicroGuard SDK |
| ||
|---|---|---|---|---|
| Author: | Micro Macro Technologies LTD | |||
| Website: | N/A | |||
| Current version: | 3.01 | |||
| Last updated: | 1998 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | ||||
| Description: | SDK for the MicroGuard dongle | |||
| Also listed in: | Dongle SDKs, MicroGuard Dongle Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Nemo 440 |
| ||
|---|---|---|---|---|
| Author: | Vadim Melnik | |||
| Website: | http://www.docsultant.com/nemo440 | |||
| Current version: | 1.0.5 | |||
| Last updated: | January 21, 2009 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free | |||
| Description: | Advanced ActionScript 3/ABC2/Flex 2/Flex 3/Flex 4/AIR disassembler. To continue learning Flex/AIR, to better understand how Flash engine and undocumented Flex classes works, and for fun, Nemo 440 tool has been created. It's free ABC code diassembler implemented as AIR-based application. This is my first experience with AIR platform. Nemo 440 can read SWF files compiled with Flex 2/Flex 3/Flex 4 and translates ActionScript 3 byte code to more understandable text dump. Actually similar tool was created year or so before by other people, I only added minor changes and started connecting these ideas with user interface. There are good programs like Flare and Flasm tools from Igor Kogan. Unfortunately with ActionScript 3/Flash 9/Flex 2 it doesn't work anymore. With Flex 3 Adobe provides Java "swfutils.jar" tool to disassemble SWF content. Gordon Smith published good article describing this functionality: Disassembling a SWF with swfdump . Interesting fact that for early Flex 2 builds (around alpha version), we used similar tool located in "swfkit.jar", but it had problem with parsing runtime and for 30% of classes in other libraries. With Flex 2 Beta version it started to work worse. Sounds like now Adobe again reborned this tool. Hope it will work well in future. Nemo 440 is free tool, USE IT AT YOUR OWN RISK, NO WARRANTIES ARE EXTENDED. It is not going to be commercial product in future. Ideally it would be nice to get something like Lutz Roeder's Reflector for .NET, disassembler, decompiler and more in one box, but for Flex. At this moment I am completely busy and probably won't do any good progress in these fields... Nemo 440 can load files from URL via HTTP or from disk ("Open URL..."/"Open File..." commands accordingly). Supported binary formats are: * Uncompressed SWF (*.swf), * Compressed SWF (*.swf), * ActionScript library (*.swc), * Raw ABC2 byte code (*.abc). | |||
| Also listed in: | Flash Disassemblers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | NetAsm |
| ||
|---|---|---|---|---|
| Author: | Alexandre Mutel | |||
| Website: | http://www.codeplex.com/netasm | |||
| Current version: | 1.0 | |||
| Last updated: | July 25, 2008 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free / Open Source | |||
| Description: | NetAsm provides a hook to the .NET JIT compiler and enables to inject your own native code in replacement of the default CLR JIT compilation. With this library, it is possible, at runtime, to inject x86 assembler code in CLR methods with the speed of a pure CLR method call and without the cost of Interop/PInvoke calls. NetAsm can be used to integrate optimized native code using CPU extended instructions (SSE,MMX) into your managed code. The NetAsmDemo sample provides two benchmarks that unveil the power of using native code injection with NetAsm. For more information about NetAsm, code injection techniques and recommendations, please consult the NetAsm-UserGuide. | |||
| Also listed in: | .NET Code Injection Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | OLE RE Tools |
| ||
|---|---|---|---|---|
| Author: | Joe Stewart | |||
| Website: | http://www.openrce.org/articles/full_view/17 | |||
| Current version: | 1.0 | |||
| Last updated: | September 12, 2005 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free / Open Source | |||
| Description: | Some utils to assist in reverse-engineering OLE applications. Use on Win32 may require addition of BINMODE. guidextract.pl - find and label OLE GUIDs in an executable guids.txt - list of GUIDs and interface names from my registry reg2guidlist.pl - make your own guids.list from a registry export file listmethods.pl - list interface methods and offsets in Vtbl | |||
| Also listed in: | COM Debugging Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | OLE/COM Object Viewer (OLEview) |
| ||
|---|---|---|---|---|
| Author: | Microsoft | |||
| Website: | http://www.microsoft.com/downloads/details.aspx?familyid=5233b70d-d9b2-4cb5-aeb6-45664be858b6 | |||
| Current version: | 1.00.0.1 | |||
| Last updated: | October 18, 2000 | |||
| Direct D/L link: | N/A | |||
| License type: | Free | |||
| Description: | Browses, configures, and tests Microsoft Component Object Model classes installed on a computer. | |||
| Also listed in: | COM Debugging Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | PEBrowse Professional |
| ||
|---|---|---|---|---|
| Author: | SmidgeonSoft | |||
| Website: | http://www.smidgeonsoft.prohosting.com/pebrowse-pro-file-viewer.html | |||
| Current version: | 10.0.1 | |||
| Last updated: | July 12, 2009 | |||
| Direct D/L link: | http://www.smidgeonsoft.com/download/PEBrowse.zip | |||
| License type: | Free | |||
| Description: | PEBrowse Professional is a static-analysis tool and disassembler for Win32/Win64 executables and Microsoft .NET assemblies produced according to the Portable Executable specifications published by Microsoft. For Microsoft Windows Vista, Windows XP, Windows 2000, and others. (We have received reports that the software also works on other OSes, including Wine (!) and Windows CE.) With the PEBrowse disassembler, one can open and examine any executable without the need to have it loaded as part of an active process with a debugger. Applications, system DLLs, device-drivers and Microsoft .NET assemblies are all candidates for offline analysis using PEBrowse. The information is organized in a convenient treeview index with the major divisions of the PE file displayed as nodes. In most cases selecting nodes will enable context-sensitive multiple view menu options, including binary dump, section detail, disassembly and structure options as well as displaying sub-items, such as optional header directory entries or exported functions, that can be found as part of a PE file unit. Several table displays, hex/ASCII equivalents, window messages and error codes, as well as a calculator and scratchpads are accessible from the main menu. While the binary dump display offers various display options, e.g., BYTE, WORD, or DWORD alignment, the greatest value of PEBrowse comes when one disassembles an entry-point. An entry-point in PEBrowse is defined as: * Module entry-point * Exports (if any) * Debug-symbols (if a valid PDB, i.e., program database file, is present) * Imported API references * Relocation addresses * Internal functions/subroutines * Any valid address inside of the module Selecting and disassembling any number of these entry-points produces a versatile display rich in detail including upper/lowercase display, C/Pascal/Assembler suffix/prefixing, object code, color-coded statements, register usage highlighting, and jump/call target preview popups. Additional information, such as variable and function names, will also be present if one has access to a valid PDB file. Disassembly comes in two flavors: linear sweep (sequential disassembly from a starting address) and recursive traversal, aka, analysis mode (disassembly of all statements reachable by non-call statements - extended analysis disassembles all internal call statements as well). The latter mode also presents local variables with cross-referencing, highlighting, and renaming options. If one adds/changes variable name or adds comments to specific lines, these can be displayed in a session file which will record and save all currently opened displays. PEBrowse Professional will decompile type library information either embedded inside of the binary as the resource "TYPELIB" or inside of individual type libraries, i.e., .TLB or .OLB files. PEBrowse Professional also displays all metadata for .NET assemblies and displays IL (Intermediate Language) for .NET methods. It seamlessly handles mixed assemblies, i.e., those that contain both native and managed code. Finally, PEBrowse can be employed as a file browse utility for any type of file with the restriction that the file must be small enough that it can be memory-mapped. | |||
| Also listed in: | .NET Disassemblers, .NET Tools, COM Tools, Delphi Tools, Disassemblers, Exe Analyzers, Memory Dumpers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | PIX with callstack patch |
| ||
|---|---|---|---|---|
| Author: | arc_ | |||
| Website: | http://www.woodmann.com/forum/showthread.php?t=12696 | |||
| Current version: | ||||
| Last updated: | July 3, 2009 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free | |||
| Description: | MSDN describes the DirectX tool "PIX" as follows (at http://msdn.microsoft.com/en-us/library/bb173085(VS.85).aspx): "PIX is a debugging and analysis tool that captures detailed information from a Direct3D application as it executes. PIX can be configured to gather data, such as the list of Direct3D APIs called, timing information, mesh vertices before and after transformations, screenshots, and select statistics. PIX can also be used for debugging vertex and pixel shaders, including setting breakpoints and stepping through shader code." Thus, a highly useful tool right from the MS DirectX SDK for e.g. finding the cause of a rendering problem: for any captured frame, you can click through the executed DX API functions and see how the frame is being built up, eventually finding out what part is to blame. But what about reversing a closed source application's renderer? PIX does not store a call stack; it merely logs *what* DX functions are called, but not from *where*. Therefore it is not very useful for reversing by default. I didn't want to let such a great tool go to waste. After some reversing work I ended up patching PIX to log and show (part of) the call stack for each DirectX call that the target program makes. Each call stack entry has both the virtual address and the module name. Example usage of the resulting modified tool is finding out about and messing with a game's renderer, or more simply locating the HUD rendering code and quickly finding the data that it represents (e.g. health, money) rather than having to resort to memory scanning. | |||
| Also listed in: | API Monitoring Tools, DirectX Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | PgcEdit |
| ||
|---|---|---|---|---|
| Author: | r0lZ | |||
| Website: | http://download.videohelp.com/r0lZ/pgcedit/index.html | |||
| Current version: | 8.6 | |||
| Last updated: | January 12, 2008 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free / Open Source | |||
| Description: | PgcEdit is a DVD IFO and Menu editor designed to allow the modification of the navigation commands and parameters of an already authored DVD structure. PgcEdit is also an excellent tool to learn how a DVD works, with his powerful Trace function. Since v0.6.0, PgcEdit is also the first program able to burn a Double Layer DVD-Video on DL DVD+R or DL DVD-R, with an interactive interface (including a preview), to select the position of the layer break. See e.g. this for a little introduction: http://www.woodmann.com/forum/showthread.php?t=11188 Many more third-party guides are linked from the homepage though. | |||
| Also listed in: | DVD Movie Logic Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Phoenix Protector |
| ||
|---|---|---|---|---|
| Author: | Daniel Pistelli | |||
| Website: | http://ntcore.com/phoenix.php | |||
| Current version: | 1.3.0.1 | |||
| Last updated: | June 2, 2008 | |||
| Direct D/L link: | http://ntcore.com/Files/Phoenix_Protector.msi | |||
| License type: | Free | |||
| Description: | The Phoenix Protector was created to protect .NET assemblies and it's the ideal solution for every .NET developer, due to its support of every kind of project and compatibility with every version of the .NET framework. It has all common obfuscation features to secure your code. It provides obfuscation features like Name, String and Control Flow Obfuscation. The last feature is particularly important since it prevents the .NET assembly from being decompiled into an understandable language. The Name Obfuscation is provided with an exclusion list. I first wrote the core of the Phoenix Protector for a company when I was 19. That project didn't work out for internal reasons not related to the quality of the product itself. I then wrote the Phoenix Protector, which was basically a new GUI for the now improved core. However, during the years (one has to consider that I was quite young when I developed the .NET obfuscator) I became ever more conscious that I didn't want to spend my life writing protections and also that I was not convinced by protections for the .NET technology in the first place. That's partly why I wrote Rebel.NET. By combining Rebel.NET with the DisasMSIL engine it is very easy to write a code obfuscator for .NET assemblies. The only thing which would be missing is name obfuscation and string encryption, which are even easier as protections. That's why I'm releasing the Phoenix Protector for free: nowadays, writing a commercial obfuscator doesn't make much sense to me. The code obfuscation provided by the Phoenix Protector is quite good when compared to other commercial obfuscators. I noticed that most obfuscators provide a very easy to reverse code obfuscation scheme. I'm not saying that the Phoenix Protector's code obfuscation can't be reversed. Every .NET code obfuscation scheme can be reversed somehow and the rebuilding task becomes very easy through Rebel.NET. | |||
| Also listed in: | .NET Packers, Packers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | PvLog DeObfuscator Win32 |
| ||
|---|---|---|---|---|
| Author: | PV Logiciels | |||
| Website: | http://dotnetprotector.pvlog.com/Tools.aspx | |||
| Current version: | 1.0 | |||
| Last updated: | November 8, 2008 | |||
| Direct D/L link: | http://dotnetprotector.pvlog.com/downloads/DeObfuscatorWin32.zip | |||
| License type: | Free | |||
| Description: | PvLog Deobfuscator is a MSIL code optimizer. One side effect of the optimizer is that it can make more readable obfuscated code. PvLog DeObfuscator can also rename the types and names of members to further improve readability. This tool does not require installation: you just need to run the executable. DeObfuscator is also available in 32 and 64 bit, but we recommend you use the version that corresponds to the architecture of the assembly to optimize. The assembly generated by Deobfusctator may not always run because of protective measures implemented in the assembly (protection against code modification), but should be able to load in reflector. NOTE: the attribute that prevents ILDASM is not removed by DeObfuscator... but it could ! | |||
| Also listed in: | .NET Deobfuscation Tools, .NET Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | PvLog LicenseManagerKiller Win32 |
| ||
|---|---|---|---|---|
| Author: | PV Logiciels | |||
| Website: | http://dotnetprotector.pvlog.com/Tools.aspx | |||
| Current version: | 1.0 | |||
| Last updated: | November 8, 2008 | |||
| Direct D/L link: | http://dotnetprotector.pvlog.com/downloads/LicenseManagerKillerWin32.zip | |||
| License type: | Free | |||
| Description: | The purpose of PvLog LicenseManagerKiller is to warn against the inefficiency of managing licenses in 100% managed code. LicenseManagerKiller is a tool that removes LicenseProvider attributes in the assembly. This tool is rudimentary and releases only most naive protections, but you can imagine that PvLog DeObfuscator and Reflector would allow a determined attacker to remove more sophisticated license controls. | |||
| Also listed in: | .NET Tools, .NET Unpackers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | RE-Sign |
| ||
|---|---|---|---|---|
| Author: | LibX | |||
| Website: | http://www.reteam.org/tools.html | |||
| Current version: | 0.1 | |||
| Last updated: | March 20, 2007 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free | |||
| Description: | RE-Sign is a tool to help u re-sign .NET assemblys with your own StrongName key, and no need todo any manual patching anymore and no need to have sn.exe installed If u don't have a StrongName keypair file u do need sn.exe to generate one, but i will include a keypair file generator in the next version. | |||
| Also listed in: | .NET Signature Changers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | REZiriz |
| ||
|---|---|---|---|---|
| Author: | LibX | |||
| Website: | http://www.reteam.org/tools.html | |||
| Current version: | 2.0 | |||
| Last updated: | August 28, 2007 | |||
| Direct D/L link: | http://www.reteam.org/tools/tf33.zip | |||
| License type: | Free | |||
| Description: | REZiriz is a unpacker for Eziriz .NET Reactor > v3.1.x.x Also added support to remove NecroBits protection that prevents the decompilation of unpacked assemblys And support to unpack v3.3.1.1 of Eziriz .NET Reactor Unpacker features: --------------------------- [*] Unpacking Eziriz .NET Reactor v3.3.1.1 [*] Unpacking Eziriz .NET Reactor v3.3.0.1 [*] Unpacking Eziriz .NET Reactor v3.2.4.6 [*] Unpacking Eziriz .NET Reactor v3.2.0.6 [*] Unpacking Eziriz .NET Reactor v3.2.0.0 [*] Unpacking Eziriz .NET Reactor v3.1.0.0 [*] Versions < v3.1.0.0 are not supported [*] Added NecroBit Protection Remover | |||
| Also listed in: | Automated Unpackers, .NET Unpackers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Resourcer for .NET |
| ||
|---|---|---|---|---|
| Author: | Lutz Roeder | |||
| Website: | http://www.aisto.com/roeder/dotnet/ | |||
| Current version: | 1.0 | |||
| Last updated: | ||||
| Direct D/L link: | N/A | |||
| License type: | Free | |||
| Description: | Resourcer is an editor for .resources binaries and .resX XML file formats used with the .NET platform. Resourcer allows editing of name/string pairs, import of bitmaps/icons and and merging of resources from different sources. | |||
| Also listed in: | .NET Resource Editors | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Rockey4 2.x Dongle C++ library IDA Signatures |
| ||
|---|---|---|---|---|
| Author: | prt | |||
| Website: | N/A | |||
| Current version: | rev1 | |||
| Last updated: | July 5, 2007 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free | |||
| Description: | IDA Signature: Rockey4 v2.x C++ library version: rev1 2007.07.05 rev1: Add Rockey4 v2.05 Add Rockey4 v2.06 | |||
| Also listed in: | Dongle IDA Signatures, IDA Signatures, Rockey Dongle Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Rockey4ND 1.x Dongle C++ library IDA Signatures |
| ||
|---|---|---|---|---|
| Author: | prt | |||
| Website: | N/A | |||
| Current version: | rev2 | |||
| Last updated: | October 11, 2007 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free | |||
| Description: | IDA Signatures: Rockey4ND v1.x C++ library 2007.07.05 rev1: Add Rockey4ND v1.20 2007.10.11 rev2: Add Rockey4ND v1.15 Add Rockey4ND v1.16 | |||
| Also listed in: | Dongle IDA Signatures, IDA Signatures, Rockey Dongle Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | SNSRemover |
| ||
|---|---|---|---|---|
| Author: | Ntoskrnl | |||
| Website: | http://www.ntcore.com/utilities.php | |||
| Current version: | 1.0 | |||
| Last updated: | November 29, 2005 | |||
| Direct D/L link: | http://www.ntcore.com/Files/SNSRemover.zip | |||
| License type: | Free | |||
| Description: | This tool removes the Strong Name Signature from .NET Assemblies. | |||
| Also listed in: | .NET Signature Removers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | SWF Quicker |
| ||
|---|---|---|---|---|
| Author: | Sothink | |||
| Website: | http://www.sothink.com/product/swfquicker | |||
| Current version: | 3.0 | |||
| Last updated: | May 24, 2007 | |||
| Direct D/L link: | N/A | |||
| License type: | Commercial (with demo) | |||
| Description: | Probably the most powerful Flash decompiler/editor there is, very advanced graphical interface. | |||
| Also listed in: | Flash Decompilers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Safenet Sentinel Hardware Keys 1.x C++ library IDA Signatures |
| ||
|---|---|---|---|---|
| Author: | prt | |||
| Website: | N/A | |||
| Current version: | rev1 | |||
| Last updated: | November 15, 2006 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free | |||
| Description: | New sentinel dongle: http://www.safenet-inc.com/products/sentinel/hardware_keys.asp IDA Signature: Safenet Sentinel Hardware Keys v1.x C++ library version: rev1 2006.11.15 rev1: Sentinel Hardware Keys v1.0.2 | |||
| Also listed in: | Dongle IDA Signatures, IDA Signatures, Sentinel Dongle Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Sentinel SuperPro 6.x Dongle C/C++ library IDA Signatures |
| ||
|---|---|---|---|---|
| Author: | prt | |||
| Website: | N/A | |||
| Current version: | rev7 | |||
| Last updated: | April 17, 2007 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free | |||
| Description: | IDA Signature: Sentinel SuperPro v6.x C/C++ library version: rev7 2007.04.11 rev7: Fixed some Sentinel obfuscated functions. (Thanks to Meteo) 2007.03.01 rev6: Fixed Sentinel obfuscated functions. (Thanks to Meteo) 2006.10.27 rev5: Add Sentinel SuperPro v6.4.4 Add Sentinel SuperPro v6.4.3 2006.03.11 rev4: Add Sentinel SuperPro v6.4.2 Add Sentinel SuperPro v6.4.1 2005.05.07 rev3: Add Sentinel SuperPro v6.4 2004.12.31 rev2: Add Sentinel SuperPro v6.3.1.9 Add Sentinel SuperPro v6.3.1.8 Add Sentinel SuperPro v6.3.1.2 Add Sentinel SuperPro v6.3.1.1 2004.12.09 rev1: Add Sentinel SuperPro v6.3.1.10 Add Sentinel SuperPro v6.3.1.4 Add Sentinel SuperPro v6.3.1 Add Sentinel SuperPro v6.3 Add Sentinel SuperPro v6.2.1 Add Sentinel SuperPro v6.2 Add Sentinel SuperPro v6.1 Add Sentinel SuperPro v6.0 | |||
| Also listed in: | Dongle IDA Signatures, IDA Signatures, Sentinel Dongle Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | SentinelLM Dongle C/C++ library IDA Signatures |
| ||
|---|---|---|---|---|
| Author: | prt | |||
| Website: | N/A | |||
| Current version: | rev2 | |||
| Last updated: | June 14, 2007 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free | |||
| Description: | IDA Signature: SentinelLM C/C++ library version: rev2 2007.06.14 Add SentinelLM v8.0 Add SentinelLM v8.0.2 Fixed some obfuscated functions. 2004.12.30 rev1: inculde: SentinelLM v7.0 SentinelLM v7.0 SP2 SentinelLM v7.1 SentinelLM v7.1.1 SentinelLM v7.1.2 SentinelLM v7.2 SentinelLM v7.2.0.1 SentinelLM v7.2.0.3 SentinelLM v7.2.0.4 SentinelLM v7.2.0.5 SentinelLM v7.2.0.6 SentinelLM v7.2.0.8 SentinelLM v7.2.0.9 SentinelLM v7.2.0.12 SentinelLM v7.2.0.18 SentinelLM v7.3.0 | |||
| Also listed in: | Dongle IDA Signatures, IDA Signatures, Sentinel Dongle Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Strong Name Remove |
| ||
|---|---|---|---|---|
| Author: | Andrea Bertolotto | |||
| Website: | http://www.codeproject.com/KB/security/StrongNameRemove20.aspx | |||
| Current version: | 2.1.0.0 | |||
| Last updated: | July 19, 2007 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free / Open Source | |||
| Description: | Good application for removing strong name signatures in .NET executables. | |||
| Also listed in: | .NET Signature Removers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | swfdecrypt |
| ||
|---|---|---|---|---|
| Author: | arc_ | |||
| Website: | http://www.woodmann.com/forum/showthread.php?t=11720 | |||
| Current version: | 1.1 | |||
| Last updated: | September 28, 2008 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free / Open Source | |||
| Description: | Unpacker for the commercial SWF Encrypt 4.0 Flash protection program (http://www.amayeta.com/software/swfencrypt). | |||
| Also listed in: | Automated Unpackers, Flash Unpackers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | TypeLib Browser |
| ||
|---|---|---|---|---|
| Author: | José Roca | |||
| Website: | http://www.com.it-berater.org/typelib_browser.htm | |||
| Current version: | 2.05 | |||
| Last updated: | July 18, 2006 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free | |||
| Description: | The TypeLib Browser is a tool designed to let you to examine the contents of COM servers and ActiveX controls and to provide alternate ways to use them or to give workarounds to features still not available in the Power Basic compilers, such events sink. Besides letting you to inspect all the information available in the typelibs, it generates wrapper functions that use direct VTable calls. | |||
| Also listed in: | COM Debugging Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Universal HASP Dump to Reg converter |
| ||
|---|---|---|---|---|
| Author: | Sataron | |||
| Website: | http://www.woodmann.com/forum/showthread.php?t=9839 | |||
| Current version: | 1.1 b1 | |||
| Last updated: | February 27, 2007 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free | |||
| Description: | Support Dump size (in byte): 204, 220, 332, 693, 716, 719, 732. Support Dump from HaspHL keys: 719 ("hasp.dmp")+4048,+128,+112 ("hhl_mem.dmp"). Files "hasp.dmp" and "hhl_mem.dmp" should be in the same directory. Support change in the number of network users. Support for the user name (only for info in *.reg file). Support for the time and date. Support long EDS (for Glasha, HarmEr emulator). Support emulator: Chingachguk & Denger2k, Glasha or HarmEr(0.8b), HarmEr(0.9b)(test support), TORO Hasp4 (test support), Chingachguk based Hasp HL (table), SafeKey Hasp4 emulator (*.SYD). | |||
| Also listed in: | Dongle Dumper Tools, HASP Dongle Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Valgrind |
| ||
|---|---|---|---|---|
| Author: | ||||
| Website: | http://valgrind.org | |||
| Current version: | 3.2.3 | |||
| Last updated: | January 29, 2007 | |||
| Direct D/L link: | N/A | |||
| License type: | Free / Open Source | |||
| Description: | Valgrind is an award-winning suite of tools for debugging and profiling Linux programs. With the tools that come with Valgrind, you can automatically detect many memory management and threading bugs, avoiding hours of frustrating bug-hunting, making your programs more stable. You can also perform detailed profiling, to speed up and reduce memory use of your programs. The Valgrind distribution currently includes four tools: a memory error detector, a cache (time) profiler, a call-graph profiler, and a heap (space) profiler. It runs on the following platforms: X86/Linux, AMD64/Linux, PPC32/Linux, PPC64/Linux. | |||
| Also listed in: | Code Injection Tools, Linux Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | WinApiOverride |
| ||
|---|---|---|---|---|
| Author: | Jacquelin POTIER | |||
| Website: | http://jacquelin.potier.free.fr/winapioverride32/ | |||
| Current version: | 5.1.11 | |||
| Last updated: | July 18, 2009 | |||
| Direct D/L link: | http://jacquelin.potier.free.fr/exe/winapioverride32_bin.zip | |||
| License type: | Free / Open Source (GPL v2) | |||
| Description: | WinAPIOverride32 is an advanced api monitoring software. You can monitor and/or override any function of a process. This can be done for API functions or executable internal functions. It tries to fill the gap between classical API monitoring softwares and debuggers. It can break targeted application before or after a function call, allowing memory or registers changes; and it can directly call functions of the targeted application. Main differences between other API monitoring softwares : - You can define filters on parameters or function result - You can define filters on dll to discard calls from windows system dll - You can hook functions inside the target process not only API - You can hook asm functions with parameters passed through registers - Double and float results are logged - Preserve registers, floating stack and LastError - You can easily override any API or any process internal function - You can break process before or/and after function call to change memory or registers - You can call functions which are inside the remote processes - Can hook COM OLE and ActiveX interfaces - All is is done like modules : you can log or override independently for any function | |||
| Also listed in: | .NET Tracers, API Monitoring Tools, COM Monitoring Tools | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
| Tool name: | Wintruder |
| ||
|---|---|---|---|---|
| Author: | FutureVision | |||
| Website: | http://mitglied.lycos.de/wintruder/wintruder.zip | |||
| Current version: | 1.0.0.1 | |||
| Last updated: | October 17, 2008 | |||
| Direct D/L link: | Locally archived copy | |||
| License type: | Free | |||
| Description: | Wintruder is an extendable debugger for Windows 9x and Windows XP. By default, it includes debug interfaces for: - Win32 Debug API - Intel x86 - Microsoft VisualBasic p-code - Virtual Dos Machine (XP only) - Win32 Stealth (XP only) - Intel x86 - Microsoft VisualBasic p-code - Virtual Dos Machine - Microsoft .Net (.Net 1.0 and up) - .Net CIL You can use Wintruder for free. For more information read license.txt. If this file does not exist, type wintruder.exe -l This version of Wintruder is a development snapshot and far from being a final release. Most important limitations: - You may encounter several bugs and deficiencies. - The use of debug information is limited to bare function definitions. - The native .Net debugger is missing. - The script engine is not really working. - Much, much more… By the way: - The DiaDbg plug-in requires the Microsoft Debug Interface Access library. (msdia80.dll, msdia71.dll or msdia20.dll) - To be more precise: None of the libraries Wintruder is bound to is included in this distribution. | |||
| Also listed in: | .NET Debuggers, Ring 3 Debuggers, Visual Basic Debuggers | |||
| More details: | Click here for more details, screenshots, related URLs & comments for this tool! (or to update its entry) | |||
...
There were too many (recursive) child objects of this category to display them all, please use the sub categories below to increase the detail of your search criteria!
Feed containing all updates and additions for this category.
Feed containing all updates and additions for this category, including sub-categories.
Subcategories
There are 17 subcategories to this category.