EMBER Feature Extraction
This repository allows the user to easily create a dataset using EMBERv3 features, starting from a collection of PE files.
If you want to work with EMBER2017 dataset (containing features from 1.1 million PE files scanned in or before 2017) or the EMBER2018 dataset (containing features from 1 million PE files scanned in or before 2018), or EMBER2024 please refer to the official repository.
Details of the selected features is available here: https://arxiv.org/pdf/2506.05074
Prerequisites
- Make sure you have a running and active version of Docker.
Usage:
-
Clone the repository and change directory:
git clone git@github.com:w-disaster/ember.git && cd ember
-
Setup the directory containing PE files. The directory should have the following structure:
<YOUR_PE_MALWARE_DIR>/ ├── <FAMILY_0>/ │ ├── SHA_0_0 │ ├── SHA_0_1 │ ├── ... │ └── ├── <FAMILY_1>/ │ ├── SHA_1_0 │ ├── ... │ └── ├── ... └──
where
FAMILY_0, FAMILY_1, ...are the directories named with the malware family andSHA_0_0, SHA_0_1, ...are the PE files named with their SHA256.The directory structure doesn't change if you want to do malware detection: simply create two directories
benignandmaliciousas the malware families. -
Configure the env variables and Run the static features extraction:
MALWARE_DIR_PATH=<YOUR_MALWARE_DIR> PE_DATASET_NAME=<YOUR_PE_DATASET_NAME> EMBER_DATA_DIR=<YOUR_EMBER_OUTPUT_DIR> docker run \ --name ember-feature-extraction \ -e MALWARE_DIR_PATH=/usr/input_data/malware/ \ -e FINAL_DATASET_FILENAME=/usr/app/dataset/$PE_DATASET_NAME.pkl \ -e N_PROCESSES=64 \ -v $MALWARE_DIR_PATH:/usr/input_data/malware/ \ -v $EMBER_DATA_DIR:/usr/app/dataset/ \ ghcr.io/malware-concept-drift-detection/ember-features-extraction:master
Metadata
Release files for EMBER_CDD__Wdis 1.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ember_cdd_wdis-1.2.1.tar.gz | 17.4 kB | Without provenance | Details for ember_cdd_wdis-1.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ember_cdd_wdis-1.2.1-py3-none-any.whl | Python 3 | none | any | Details for ember_cdd_wdis-1.2.1-py3-none-any.whl |
Total release size: 35.1 kB
Release files / ember_cdd_wdis-1.2.1.tar.gz
| Download URL | ember_cdd_wdis-1.2.1.tar.gz |
|---|---|
| Size | 17.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
37f4d54513c358e9509e0961e25cd91aeeaaea1429170ee26f05159a18231198
|
|
BLAKE2b-256 checksum How to use checksums |
c5d78998c37d3d7eefa143bf94040cbce9abe7be7b039e5b8a66812319b7aa47
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.3 CPython/3.12.3 Linux/6.11.0-1018-azure
|
Release files / ember_cdd_wdis-1.2.1-py3-none-any.whl
| Download URL | ember_cdd_wdis-1.2.1-py3-none-any.whl |
|---|---|
| Size | 17.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
156c23b0eabdefee9eecd4ede75c0fc3e25d192777af823c0ef2a8ccab58d158
|
|
BLAKE2b-256 checksum How to use checksums |
a19a692826f36145e93bd28c367526e7ca44f34e371a406ed133a5b8ca0e3eb7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.3 CPython/3.12.3 Linux/6.11.0-1018-azure
|
Security for EMBER_CDD__Wdis 1.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.