Uloženo v:
Podrobná bibliografie
Hlavní autor: Daniel Arp
Médium: Recurso digital
Jazyk:
Vydáno: Zenodo 2025
On-line přístup:https://doi.org/10.5281/zenodo.18782865
Tagy: Přidat tag
Žádné tagy, Buďte první, kdo vytvoří štítek k tomuto záznamu!
Obsah:
  • <p>The <strong>AndMal2025</strong> dataset provides a comprehensive behavioral representation of Android applications by integrating static code attributes and runtime execution indicators. Each record corresponds to a single APK instance, where the feature set captures permission usage, system interactions, service binding activities, resource consumption patterns, and network behavior. The dataset to support robust supervised learning for Android malware analysis, including both primary binary detection and auxiliary multi-label family characterization.</p> <p>The feature space is organized into six major groups to reflect different operational layers of Android applications.</p> <h3>1. Application Metadata Features</h3> <p>These attributes summarize high-level structural properties of the APK and provide contextual signals regarding application complexity.</p> <ul> <li> <p><strong>App_ID</strong> — Unique identifier assigned to each application instance.</p> </li> <li> <p><strong>APK_Size_KB</strong> — Size of the packaged APK file in kilobytes, reflecting application footprint.</p> </li> <li> <p><strong>Dex_Method_Count</strong> — Total number of methods extracted from the DEX bytecode, indicating codebase complexity.</p> </li> </ul> <p>These metadata features help distinguish lightweight benign utilities from feature-dense malicious packages.</p> <h3>2. Permission-Based Static Features</h3> <p>Permission indicators capture declared capabilities within the Android manifest and are widely recognized as strong malware predictors.</p> <ul> <li> <p><strong>perm_SEND_SMS</strong> — Indicates whether the application requests SMS transmission permission.</p> </li> <li> <p><strong>perm_ACCESS_NETWORK_STATE</strong> — Reflects access to network connectivity state information.</p> </li> <li> <p><strong>perm_WRITE_SETTINGS</strong> — Indicates permission to modify system settings.</p> </li> <li> <p><strong>perm_INTERNET</strong> — Specifies whether the application can access network resources.</p> </li> <li> <p><strong>perm_count_total</strong> — Total number of permissions requested by the application.</p> </li> <li> <p><strong>perm_count_dangerous</strong> — Number of high-risk permissions requested.</p> </li> <li> <p><strong>danger_perm_ratio</strong> — Ratio of dangerous permissions to total permissions.</p> </li> </ul> <p>These features characterize the privilege profile of each application and expose over-permission patterns commonly associated with malicious behavior.</p> <h3>3. Intent and Broadcast Action Features</h3> <p>Broadcast receivers and intent filters reveal persistence mechanisms and background execution strategies.</p> <ul> <li> <p><strong>intent_BOOT_COMPLETED</strong> — Indicates registration for device boot completion events.</p> </li> <li> <p><strong>intent_SCREEN_ON</strong> — Indicates monitoring of screen activation events.</p> </li> </ul> <p>Such signals are frequently linked to stealth persistence and opportunistic background activity.</p> <h3>4. Class and API Usage Indicators</h3> <p>These features capture the presence of sensitive framework classes that often appear in suspicious workflows.</p> <ul> <li> <p><strong>class_java_lang_Class</strong> — Reflects dynamic class loading or reflection usage.</p> </li> <li> <p><strong>class_android_telephony_SmsManager</strong> — Indicates access to SMS management APIs.</p> </li> </ul> <p>API-level evidence complements permission analysis by exposing how declared privileges are operationalized.</p> <h3>5. Runtime Event and Service Interaction Features</h3> <p>Dynamic execution monitoring provides insight into inter-process communication and service orchestration behaviors.</p> <ul> <li> <p><strong>evt_Transact</strong> — Count of Binder transaction events.</p> </li> <li> <p><strong>evt_onServiceConnected</strong> — Number of successful service connection callbacks.</p> </li> <li> <p><strong>evt_bindService</strong> — Frequency of service binding requests.</p> </li> <li> <p><strong>evt_attachInterface</strong> — Interface attachment operations observed at runtime.</p> </li> <li> <p><strong>evt_ClassLoader</strong> — Dynamic class loading events.</p> </li> <li> <p><strong>evt_total</strong> — Aggregate count of monitored runtime events.</p> </li> <li> <p><strong>evt_entropy</strong> — Distribution entropy of runtime event types.</p> </li> </ul> <p>These features expose behavioral patterns that may remain hidden in purely static inspection.</p> <h3>6. System Activity, Resource, and Network Features</h3> <p>This group captures operational footprints generated during application execution.</p> <p><strong>System and Resource Metrics</strong></p> <ul> <li> <p><strong>syscall_count_total</strong> — Total number of observed system calls.</p> </li> <li> <p><strong>cpu_mean</strong> — Mean CPU utilization during execution.</p> </li> <li> <p><strong>mem_mean_mb</strong> — Average memory consumption in megabytes.</p> </li> <li> <p><strong>file_write_count</strong> — Number of file write operations.</p> </li> <li> <p><strong>service_start_count</strong> — Count of service start invocations.</p> </li> </ul> <p><strong>Network Behavior Metrics</strong></p> <ul> <li> <p><strong>net_conn_count</strong> — Number of outbound network connections.</p> </li> <li> <p><strong>dns_query_count</strong> — DNS query frequency.</p> </li> <li> <p><strong>net_tx_kb</strong> — Volume of transmitted network data (KB).</p> </li> <li> <p><strong>net_rx_kb</strong> — Volume of received network data (KB).</p> </li> </ul> <p><strong>Code Structure Indicators</strong></p> <ul> <li> <p><strong>opcode_ngram_entropy</strong> — Entropy of opcode n-gram distribution.</p> </li> <li> <p><strong>dex_string_entropy</strong> — Entropy of embedded string constants.</p> </li> </ul> <p>These features jointly model communication intensity, resource usage patterns, and code-level irregularities associated with malicious workflows.</p> <h2>Target Labels</h2> <p>The dataset supports both primary detection and fine-grained family characterization.</p> <h3>Primary Prediction Label</h3> <ul> <li> <p><strong>Malware_Binary</strong> — Binary ground truth where</p> <ul> <li> <p><code>0</code> denotes benign applications</p> </li> <li> <p><code>1</code> denotes malicious applications</p> </li> </ul> </li> </ul> <p>This label is intended for the main supervised malware detection task.</p> <h3>Auxiliary Multi-Label Family Annotations</h3> <p>To enable detailed behavioral analysis, the dataset provides non-exclusive malware family indicators:</p> <ul> <li> <p><strong>y_scareware</strong> — Scareware activity indicator</p> </li> <li> <p><strong>y_ransomware</strong> — Ransomware activity indicator</p> </li> <li> <p><strong>y_adware</strong> — Adware activity indicator</p> </li> <li> <p><strong>y_sms_malware</strong> — SMS-based malicious activity indicator</p> </li> </ul> <p>Multiple family labels may be active simultaneously for a single application, enabling multi-label learning and cross-family behavioral studies.</p>