2015 IEEE/ACM 1st International Workshop on Software Protection 2015
DOI: 10.1109/spro.2015.13
|View full text |Cite
|
Sign up to set email alerts
|

Obfuscating Windows DLLs

Abstract: Abstract-We present two techniques to obfuscate the interfaces between application binaries and Windows system DLLs (dynamic-link libraries). The first technique obfuscates the related symbol information in the binary to prevent static analyses from identifying the invoked library functions. The second technique combines static linking with code obfuscation to avoid the external interface altogether, thus preventing dynamic attacks as well. This is done while still maintaining compatibility with multiple Windo… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
6
0

Year Published

2017
2017
2020
2020

Publication Types

Select...
5
1

Relationship

0
6

Authors

Journals

citations
Cited by 6 publications
(6 citation statements)
references
References 8 publications
0
6
0
Order By: Relevance
“…The feature is available in some commercial obfuscation tools, such as DexProtector (2018). Abrath et al (2015) investigate the problem for Windows software, and they also propose to replace the original function calls via a binder. Bohannon and Holmes (2017) investigated a similar problem for Windows powershell scripts.…”
Section: Code Diversificationmentioning
confidence: 99%
“…The feature is available in some commercial obfuscation tools, such as DexProtector (2018). Abrath et al (2015) investigate the problem for Windows software, and they also propose to replace the original function calls via a binder. Bohannon and Holmes (2017) investigated a similar problem for Windows powershell scripts.…”
Section: Code Diversificationmentioning
confidence: 99%
“…DLL Static Linking When a system DLL is statically linked to a malware executable, we cannot identify the APIs exported from the DLL [1]. This is because the codes of the APIs exported from the DLL do not have any taint tags, even though we need taint tags to resolve the API names.…”
Section: Limitationmentioning
confidence: 99%
“…One closely related study is by Abrath et al [2]. They proposed a technique of linking Windows-system DLLs statically with an executable and deleting imported API information from it to prevent API calls from being monitored.…”
Section: Related Workmentioning
confidence: 99%
“…Stealth Loader evaded all the tools. IAT Obfuscation and API Redirection are techniques for API obfuscation while ldrmodules is a tool for extracting loaded DLLs 2. When we manually gave the correct original entry point of a protected executable to Scylla, it could identify imported APIs correctly.…”
mentioning
confidence: 99%