2009 16th Working Conference on Reverse Engineering 2009
DOI: 10.1109/wcre.2009.24
|View full text |Cite
|
Sign up to set email alerts
|

Automatic Static Unpacking of Malware Binaries

Abstract: Abstract-Current malware is often transmitted in packed or encrypted form to prevent examination by anti-virus software. To analyze new malware, researchers typically resort to dynamic code analysis techniques to unpack the code for examination. Unfortunately, these dynamic techniques are susceptible to a variety of anti-monitoring defenses, as well as "time bombs" or "logic bombs," and can be slow and tedious to identify and disable. This paper discusses an alternative approach that relies on static analysis … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
29
0

Year Published

2010
2010
2022
2022

Publication Types

Select...
5
3
2

Relationship

2
8

Authors

Journals

citations
Cited by 54 publications
(29 citation statements)
references
References 10 publications
0
29
0
Order By: Relevance
“…Coogan et al [3] proposed an automatic static unpacking mechanism. It uses static analysis techniques to identify the unpacking code that comes with a given malware binary, then uses this code to construct a customized unpacker for that binary.…”
Section: Related Workmentioning
confidence: 99%
“…Coogan et al [3] proposed an automatic static unpacking mechanism. It uses static analysis techniques to identify the unpacking code that comes with a given malware binary, then uses this code to construct a customized unpacker for that binary.…”
Section: Related Workmentioning
confidence: 99%
“…There is a rich body of literature dealing with dynamically generated ("unpacked") code in the context of conventional native-code malware executables [14,19,4,10]. Much of this work focuses on detecting the fact of unpacking and identifying the unpacked code; because of the nature of the code involved, the techniques used are necessarily low-level, typically relying on detecting the execution of a previously-modified memory locations (or pages).…”
Section: Related Workmentioning
confidence: 99%
“…Therefore, the first step of the reverse translation is a code unpacking phase. As this topic is well documented in the literature (see [38,39]), we will not deal with it in our paper. After that, it is necessary to convert the platform-specific file format into a unified form of representation.…”
Section: Front-endmentioning
confidence: 99%