Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learning Malware Analysis

You're reading from   Learning Malware Analysis Explore the concepts, tools, and techniques to analyze and investigate Windows malware

Arrow left icon
Product type Paperback
Published in Jun 2018
Publisher
ISBN-13 9781788392501
Length 510 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Monnappa K A Monnappa K A
Author Profile Icon Monnappa K A
Monnappa K A
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Introduction to Malware Analysis FREE CHAPTER 2. Static Analysis 3. Dynamic Analysis 4. Assembly Language and Disassembly Primer 5. Disassembly Using IDA 6. Debugging Malicious Binaries 7. Malware Functionalities and Persistence 8. Code Injection and Hooking 9. Malware Obfuscation Techniques 10. Hunting Malware Using Memory Forensics 11. Detecting Advanced Malware Using Memory Forensics 12. Other Books You May Enjoy

5. Listing Process Handles


During your investigation, once you pin down a malicious process, you may want to know which objects (such as processes, files, registry keys, and so on) the process is accessing. This will give you an idea of the components associated with the malware and an insight into their operation, for example, a keylogger may be accessing a log file to log captured keystrokes, or malware might have an open handle to the configuration file.

To access an object, a process needs to first open a handle to that object by calling an API such as CreateFile or CreateMutex. Once it opens a handle to an object, it uses that handle to perform subsequent operations such as writing to a file or reading from a file. A handle is an indirect reference to an object; think of a handle as something that represents an object (the handle is not the object itself). The objects reside in the kernel memory, whereas the process runs in the user space, because of which a process cannot access the...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image