Explore >> Select a destination
|
You are here 
|
blog.haboob.sa | ||
| | | | |
x0rb3l.github.io
|
|
| | | | | OverviewIn Part II we concluded our static analysis by becoming familiar with IDA Pro and using it to confirm one of our previous findings and to examine obfuscated strings on the stack. In this article, we will be conducting code analysis. Code analysis involves examining the code that comprises the specimen, only this time in a dynamic fashion. We will be using x32dbg as our debugger. The goal of Part III is to demonstrate how we can step through the malware's instructions and allow it to automatically reveal information about itself that is otherwise "invisible" while not running.x32dbgx32dbg is the 32-bit debugger that is a part of the open-source x64dbg software package. It is probably my favorite user mode Windows debugger due to its ease of use and fr... | |
| | | | |
blog.redcrowlab.com
|
|
| | | | | Much of the time people engage in short term security testing such as penetration tests, vulnerability assessments, code reviews, etc. Often these are 1-2 weeks with some period for reporting. The approach to conducting these sorts of projects typically includes the following types of steps: * Heavy reliance on automated tools | |
| | | | |
usualsuspect.re
|
|
| | | | | ||
| | | | |
ivyfanchiang.ca
|
|
| | | Tearing apart Go malware sent to my honeypot and discovering Golang's interesting runtime quirks | ||
