June 24, 2022 12:15 AM (GMT+2) - Filipi Pires

Demonstrate different kind of structures in the binaries as a PE (header and your sessions) , ELF (header and your sessions), PDF(header/ body/cross-reference table/trailer), explaining how each session works within a binary, what are the techniques used such as packers, obfuscation with JavaScript (PDF) and more, explaining too about some anti-disassembly techniques, demonstrating as a is the action of these malware’s and where it would be possible to “include” a malicious code. By the end of this “talk” it will be clear to everyone, differences in binaries structures, how can the researcher should conduct each of these kinds of analyzes, besides of course, it should seek more basic knowledge, with file structures, software architecture, and programming language.

🇬🇧 Dissecting and Comparing different Binaries to Malware Analysis Filipi Pires

Blog post reference

PDF Malware Analysis

Introduction

Static analysis describes the process of analyzing a program’s code or structure to determine its function. The program itself doesn’t run at this time (depending on the program), this makes the parsing process more “safe”, because we aren’t actually executing it.

Dynamic analysis is based solely on behavior, ie the interaction that malware has when it is executed or a maldoc is used, also known as “runtime” analysis. It can be easily automated, there are sites today that already perform analysis of malicious artefacts, using the concept called “sandbox”

Magic number

File identification using magic number

Untitled

PDF File

Structure

Untitled

Header identification using PDFiD

Untitled

/JS and /JavaScript indicate that the PDF document contains JavaScript. Almost all malicious PDF documents that I’ve found in the wild contain JavaScript (to exploit a JavaScript vulnerability and/or to execute a heap spray). Of course, you can also find JavaScript in PDF documents without malicious intent.

/AA and /OpenAction indicate an automatic action to be performed when the page/document is viewed. All malicious PDF documents with JavaScript I’ve seen in the wild had an automatic action to launch the JavaScript without user interaction.

Analysis with 🔗 pdf-parser