Update README.md
Browse files
README.md
CHANGED
|
@@ -1,3 +1,48 @@
|
|
| 1 |
-
---
|
| 2 |
-
license: mit
|
| 3 |
-
---
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
---
|
| 2 |
+
license: mit
|
| 3 |
+
---
|
| 4 |
+
|
| 5 |
+
# Malware vs Benign PE Assembly Dataset (2020, Sliding Window)
|
| 6 |
+
|
| 7 |
+
This dataset consists of assembly code fragments extracted from malicious and benign Portable Executable (PE) files. It was created to support deep learning-based malware classification. Assembly code was segmented using a sliding window technique to preserve contextual information.
|
| 8 |
+
|
| 9 |
+
## Dataset Description
|
| 10 |
+
|
| 11 |
+
The dataset includes assembly code segments derived from two types of PE files:
|
| 12 |
+
|
| 13 |
+
- **Malware Samples**
|
| 14 |
+
Malicious PE files were downloaded from [MalwareBazaar](https://bazaar.abuse.ch/), specifically focusing on samples uploaded in **2020**. Each file was disassembled into assembly code using the `objdump` command on Ubuntu.
|
| 15 |
+
|
| 16 |
+
- **Benign Samples**
|
| 17 |
+
Benign PE files were collected from regular executable files stored on a PC using PowerShell. These files were also disassembled using `objdump` to extract assembly code in the same manner.
|
| 18 |
+
|
| 19 |
+
## Sliding Window Preprocessing
|
| 20 |
+
|
| 21 |
+
To prepare the data for machine learning:
|
| 22 |
+
|
| 23 |
+
- Assembly code was segmented using a sliding window approach:
|
| 24 |
+
- **Window Size:** 350 lines
|
| 25 |
+
- **Stride:** 175 lines (50% overlap)
|
| 26 |
+
- This setup ensures that the segments preserve contextual relationships between instructions.
|
| 27 |
+
- Importantly, **all segments generated from a single file are kept together** to maintain file-level grouping and avoid mixing across files.
|
| 28 |
+
- No tokenization was applied; the raw assembly code was used as-is during segmentation.
|
| 29 |
+
|
| 30 |
+
## Data Format
|
| 31 |
+
|
| 32 |
+
Each entry in the dataset includes:
|
| 33 |
+
|
| 34 |
+
- `assembly`: A segment of assembly code extracted via sliding window
|
| 35 |
+
- `label`: A binary classification label indicating `malware` or `benign`
|
| 36 |
+
|
| 37 |
+
## Intended Use
|
| 38 |
+
|
| 39 |
+
This dataset is suitable for the following tasks:
|
| 40 |
+
|
| 41 |
+
- Malware classification using NLP-based models (e.g., Transformer-based models)
|
| 42 |
+
- Research on malware detection using sliding window context segmentation
|
| 43 |
+
|
| 44 |
+
## Tools Used
|
| 45 |
+
|
| 46 |
+
- `objdump` (for extracting assembly code)
|
| 47 |
+
- PowerShell (for collecting benign files)
|
| 48 |
+
- Python scripts (for sliding window segmentation and maintaining per-file chunk structure)
|