http://www.woodmann.com/collaborative/tools/index.php/Special:FeedListing/Code_Ripping_Tools/feed?recursive=1&feed_type=atom 2010-09-03T10:26:28Z Update Notification Feed for Category: Code Ripping Tools (and its sub-categories) MediaWiki 1.11.2 via dELTA feed generator http://www.woodmann.com/collaborative/tools/index.php/OfficeMalScanner 2010-06-17T09:51:08Z

<P><B>Listed in categories:</B>&nbsp;<I><a href="http://www.woodmann.com/collaborative/tools/index.php/Category:Code_Ripping_Tools">Code Ripping Tools</a>, <a href="http://www.woodmann.com/collaborative/tools/index.php/Category:Data_Search_and_Extraction_Tools">Data Search and Extraction Tools</a></I></P><p><b>Most recent version:</b><br /> <i>v0.51</i> </p><p><b>Most recent release date:</b><br /> <i>February 5, 2010</i> </p><p><b>Description:</b><br /> <i>OfficeMalScanner v0.51 is a Ms Office forensic tool to scan for malicious traces, like shellcode heuristics, PE-files or embedded OLE streams. Found files are being extracted to disk. It supports disassembly and hexview as well as an easy brute force mode to detect encrypted files. Next to this, an office file is being scanned for VB-macro code and if found, it will be extracted for further analysis. The &quot;inflate&quot; feature extracts Ms Office 2007 documents into a directory and marks potentially malicious files. Also included in this package is a tool called MalHost-Setup, some kind of MS Office runtime emulation environment to debug shellcode in malicious documents in realtime.</i> </p>

http://www.woodmann.com/collaborative/tools/index.php/TMG_Ripper_Studio 2008-01-10T21:16:26Z

<P><B>Listed in categories:</B>&nbsp;<I><a href="http://www.woodmann.com/collaborative/tools/index.php/Category:Code_Ripping_Tools">Code Ripping Tools</a></I></P><p><b>Most recent version:</b><br /> <i>0.03</i> </p><p><b>Most recent release date:</b><br /> <i>2005</i> </p><p><b>Description:</b><br /> <i>This is a tool for converting a small part of a program into assemblycode that you could paste into your own sources. The program takes either a fileoffset or a virtual address as input and starts to disassemble from that point. When a conditional jump is reached, it branches and follow both directions. It also follows unconditional jumps and traces calls.</i> </p>