Explore >> Select a destination
|
You are here 
|
blog.haboob.sa | ||
| | | | |
www.malwaretech.com
|
|
| | | | | One of the most common questions I'm asked is "what programming language(s) should I learn to get into malware analysis/reverse engineering", to answer this question I'm going to write about the top 3 languages which I've personally found most useful. I'll focus on native malware (malware which does not require a framework such as Java, Python, or .NET to run), as this is the most common type and understanding it it will provide you the skills required to pivot into other kinds. In this article I won't b... | |
| | | | |
gpfault.net
|
|
| | | | | [AI summary] The provided text is a detailed explanation of how to write a simple 64-bit Windows application in assembly language that calls the ExitProcess function from the KERNEL32.DLL library. It covers the following key topics: 1. **Memory and Register Basics**: Explains how memory and registers work in 64-bit Windows, including the use of the stack pointer (RSP), registers like RCX, RDX, R8, and R9 for passing arguments, and the importance of stack alignment for performance. 2. **Calling Conventions**: Details the 64-bit Windows calling convention, including how the first four integer or pointer arguments are passed in registers (RCX, RDX, R8, R9), how additional arguments are passed on the stack, and the requirement for the stack to be aligned to ... | |
| | | | |
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 | |
| | | | |
brunty.me
|
|
| | | Developer and problem solver | ||
