Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Security
Malware Analysis
Opinion about behavioral analysis
Message
<blockquote data-quote="Deleted member 65228" data-source="post: 666969"><p>This is why I said by changing the value within EAX to 0 it will be bypassed (or RAX for 64-bit). But cool!</p><p></p><p>That ASM method you will only work for a 32-bit process, on a 64-bit process you'll be using the RAX register as well (64-bit version of EAX - AX -> EAX -> RAX). RAX returns the result on a 64-bit process.</p><p></p><p>- You can use the __readfsdword() (32-bit) and __readgsqword() (64-bit) to get the Thread Environment Block.</p><p>- Retrieve the PEB address from the TEB.</p><p></p><p>There's a function called NtCurrentTeb which will return the Thread Environment Block of the thread you executed the call from, also. Then you can ->ProcessEnvironmentBlock with the returned PTEB type variable.</p></blockquote><p></p>
[QUOTE="Deleted member 65228, post: 666969"] This is why I said by changing the value within EAX to 0 it will be bypassed (or RAX for 64-bit). But cool! That ASM method you will only work for a 32-bit process, on a 64-bit process you'll be using the RAX register as well (64-bit version of EAX - AX -> EAX -> RAX). RAX returns the result on a 64-bit process. - You can use the __readfsdword() (32-bit) and __readgsqword() (64-bit) to get the Thread Environment Block. - Retrieve the PEB address from the TEB. There's a function called NtCurrentTeb which will return the Thread Environment Block of the thread you executed the call from, also. Then you can ->ProcessEnvironmentBlock with the returned PTEB type variable. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
