Browse State-of-the-Art › Malware Detection
Malware Detection
108 papers with code · 2 benchmarks · 5 datasets archive 2025-07-28
Malware Detection is a significant part of endpoint security including workstations, servers, cloud instances, and mobile devices. Malware Detection is used to detect and identify malicious activities caused by malware. With the increase in the variety of malware activities on CMS based websites such as malicious malware redirects on WordPress site (Aka, WordPress Malware Redirect Hack) where the site redirects to spam, being the most widespread, the need for automatic detection and classifier amplifies as well. The signature-based Malware Detection system is commonly used for existing malware that has a signature but it is not suitable for unknown malware or zero-day malware
Source: The Threat of Adversarial Attacks on Machine Learning in Network Security - A Survey
Description from the archive archive 2025-07-28.
Benchmarks archive 2025-07-28
2 leaderboard tables shown for this task, 2 with rows (a “benchmark” on this site is a table with at least one row, as on /sota), ordered by row count. “Best model” is the first row in the archive's own order at snapshot; nothing is re-ranked here and metric direction is not recorded in the archive. PwC's Trend sparklines are not in the archive, so that column is omitted.
| Dataset | Best model (first row in archive order) | Paper | Code | Syntology | Compare |
|---|---|---|---|---|---|
| Android Malware Dataset (4 rows) | Graph2Vec | graph2vec: Learning Distributed Representations of Graphs | code | Syntology 2 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified | Compare |
| MalNet (3 rows) | SHERLOCK (family) | Self-Supervised Vision Transformers for Malware Detection | code | Syntology official (archive's flag): 8 ran · 8 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 2 honoured, 2 violated, 3 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified | Compare |
Syntology column: samples harvested from the paper's repositories and executed on synthesized fixtures; “ran” is not a correctness claim and does not order the table. Each line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the row's paper, the line starts with that repository's state (“official” is the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from. A dash means no Syntology record for that paper, not a recorded non-run. Each “ran” line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.
Libraries
Not in the archive: the export carries no per-task library table, so there is nothing to show at snapshot 2025-07-28.
Datasets archive 2025-07-28
5 datasets whose archive record lists this task, ordered by the archive's paper count.
Subtasks archive 2025-07-28
No subtask under this task in the archive's task tree.
Parent tasks archive 2025-07-28
Papers archive 2025-07-28
archive papers tagged: 431 · with a code link: 108 · where Syntology ran a sample: 11 (8 with a run with no instrument failure, 3 where every run was a failure of Syntology's instrument) Syntology
Show: all tagged papersonly where code ran (11 of 431 tagged: 8 with a run with no instrument failure, 3 where every run was a failure of Syntology's instrument)
Page 1 of 5: papers 1 to 100 of 431, in archive order: by repositories listed in the archive (most first), then newest first, not by stars (the archive holds no stars, so PwC's “Social” and “Latest” sorts cannot be reproduced). Papers that list no repository come after every paper that lists one.
Papers without a page here are shown as plain text. A Syntology line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the figure “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code); hover it for the repositories the samples that ran came from. The first sentence of the abstract is shown for the first 30 papers; every abstract is on its paper's page.
-
25 Oct 2017 7 repositories listed Syntology 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 3 unverified (of 7 harvested samples)In this work we introduce malware detection from raw byte sequences as a fruitful research area to the larger machine learning community.
-
13 Mar 2018 4 repositories listed Syntology 3 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 3 where Syntology's instrument failed) · 0 unverified (of 3 harvested samples)However, deep learning is often criticized for its lack of robustness in adversarial settings (e. g., vulnerability to adversarial inputs) and general inability to rationalize its predictions.
-
20 Feb 2017 4 repositories listedA generative network is trained to minimize the generated adversarial examples' malicious probabilities predicted by the substitute detector.
-
15 May 2019 3 repositories listedWith the rapid proliferation and increased sophistication of malicious software (malware), detection methods no longer rely only on manually generated signatures but have also incorporated more general approaches like…
-
18 May 2017 3 repositories listedFirst, we introduce neuron coverage for systematically measuring the parts of a DL system exercised by test inputs.
-
29 Jun 2016 3 repositories listedAlso, we show that the subgraph vectors could be used for building a deep learning variant of Weisfeiler-Lehman graph kernel.
-
5 Jun 2025 2 repositories listedA lack of accessible data has historically restricted malware analysis research, and practitioners have relied heavily on datasets provided by industry sources to advance.
-
8 Feb 2023 2 repositories listedWe propose a new hierarchical contrastive learning scheme, and a new sample selection technique to continuously train the Android malware classifier.
-
31 Jan 2023 2 repositories listed Syntology official (archive's flag): 7 ran · 11 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 3 honoured, 0 violated, 6 with no contract checked; 2 where Syntology's instrument failed) · 3 unverified (of 14 harvested samples)When applied to the popular MalConv malware detection model, our smoothing mechanism RS-Del achieves a certified accuracy of 91% at an edit distance radius of 128 bytes.
-
15 Jun 2021 2 repositories listedThe use of Machine Learning has become a significant part of malware detection efforts due to the influx of new malware, an ever changing threat landscape, and the ability of Machine Learning methods to discover…
-
17 Aug 2020 2 repositories listedRecent work has shown that adversarial Windows malware samples - referred to as adversarial EXEmples in this paper - can bypass machine learning-based detection relying on static code analysis by perturbing relatively…
-
12 Jul 2020 2 repositories listedNeural network classifiers (NNCs) are known to be vulnerable to malicious adversarial perturbations of inputs including those modifying a small fraction of the input features named sparse or L₀ attacks.
-
23 Jun 2020 2 repositories listedWe propose a versatile framework based on random search, Sparse-RS, for score-based sparse targeted and untargeted attacks in the black-box setting.
-
17 Jul 2019 2 repositories listedIn this paper, we propose a novel and low-cost feature extraction approach, and an effective deep neural network architecture for accurate and fast malware detection.
-
5 Jun 2019 2 repositories listedDeep learning is increasingly used as a building block of security systems.
-
19 Sep 2018 2 repositories listedOur approach can check different safety properties and find concrete counterexamples for networks that are 10× larger than the ones supported by existing analysis techniques.
-
21 Nov 2017 2 repositories listedWhile conventional signature and token based methods for malware detection do not detect a majority of new variants for existing malware, the results presented in this paper show that signatures generated by the DBN…
-
5 Sep 2017 2 repositories listedMany efforts have been made to use various forms of domain knowledge in malware detection.
-
31 Jan 2017 2 repositories listedIn the experiments conducted on the novel test data set the accuracy was observed as 89.
-
24 May 2025 1 repository listedIn practice, these distributions evolve due to frequent changes in the Android ecosystem, adversarial development of new malware families, and the continuous emergence of both benign and malicious applications.
-
14 May 2025 1 repository listedAdversarially trained defenses, including AT-rFGSM-k, AT-MaxMA, improves robustness under small budgets but remains vulnerable to unrestricted perturbations, with attack success rates of 99.
-
7 May 2025 1 repository listedTherefore, we recommend testing single classifiers and imbalance learning techniques for each new dataset and application involving imbalanced datasets as is the case in several cyber security applications.
-
30 Mar 2025 1 repository listedThis study addresses the often-overlooked issue of class imbalance in malware detection by evaluating various machine learning strategies for detecting malware in Android applications.
-
12 Mar 2025 1 repository listedIn our primary example, we rigorously assess the safety of fine-tuned models using the OWASP top 10 framework, finding that fine-tuning reduces safety resilience across all tested LLMs and every adversarial attack (e.…
-
18 Feb 2025 1 repository listedWe also empirically show that we only need a subset of the function call sequence, specifically calls to the ntdll. dll library, to identify malware.
-
24 Dec 2024 1 repository listedThis study presents a set of innovative problem-based evasion attacks against well-known Android malware detection systems, which decrease their detection rate by up to 97%.
-
29 Sep 2024 1 repository listedAmong the various tools employed in malware detection, graph representations (e. g., function call graphs) have played a pivotal role in characterizing the behaviors of Android apps.
-
28 Sep 2024 1 repository listed Syntology official: harvested, nothing ran · 0 ran · 1 unverified (of 1 harvested sample)The escalating frequency and scale of recent malware attacks underscore the urgent need for swift and precise malware classification in the ever-evolving cybersecurity landscape.
-
29 Aug 2024 1 repository listedRecent advancements in ML and DL have significantly improved Android malware detection, yet many methodologies still rely on basic static analysis, bytecode, or function call graphs that often fail to capture complex…
-
27 Aug 2024 1 repository listedIn particular, our defense can improve adversarial robustness by up to 55% against realistic evasion attacks compared to Sec-SVM.
-
4 Jun 2024 1 repository listed
-
29 Feb 2024 1 repository listed
-
13 Dec 2023 1 repository listed
-
11 Dec 2023 1 repository listed
-
19 Sep 2023 1 repository listed
-
18 Sep 2023 1 repository listed
-
7 Sep 2023 1 repository listed
-
Efficient Query-Based Attack against ML-Based Android Malware Detection under Zero Knowledge Setting5 Sep 2023 1 repository listed
-
31 Aug 2023 1 repository listed
-
27 Jul 2023 1 repository listed
-
23 Jun 2023 1 repository listed
-
31 May 2023 1 repository listed Syntology official (archive's flag): 4 ran · 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 7 unverified (of 11 harvested samples)
-
20 Mar 2023 1 repository listed
-
22 Feb 2023 1 repository listed
-
11 Feb 2023 1 repository listed
-
30 Jan 2023 1 repository listed
-
3 Nov 2022 1 repository listed
-
28 Oct 2022 1 repository listed Syntology official (archive's flag): 3 ran · 3 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 1 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified (of 3 harvested samples) · 3 pointer-only (licence)
-
6 Sep 2022 1 repository listed
-
15 Aug 2022 1 repository listed Syntology official (archive's flag): 8 ran · 8 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 2 honoured, 2 violated, 3 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified (of 8 harvested samples) · 4 pointer-only (licence)
-
16 Jun 2022 1 repository listed
-
30 May 2022 1 repository listed
-
26 May 2022 1 repository listed Syntology official (archive's flag): 5 ran · 5 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 3 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 3 unverified (of 8 harvested samples)
-
25 May 2022 1 repository listed
-
24 May 2022 1 repository listed
-
13 Apr 2022 1 repository listed
-
28 Feb 2022 1 repository listed
-
7 Feb 2022 1 repository listed
-
19 Jan 2022 1 repository listed
-
23 Dec 2021 1 repository listed
-
7 Oct 2021 1 repository listed
-
20 Sep 2021 1 repository listed
-
5 Sep 2021 1 repository listed
-
14 Aug 2021 1 repository listed
-
5 Jun 2021 1 repository listed
-
24 May 2021 1 repository listed Syntology official (archive's flag): 2 ran · 2 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 1 unverified (of 3 harvested samples) · 3 pointer-only (licence)
-
15 Apr 2021 1 repository listed
-
9 Mar 2021 1 repository listed
-
31 Jan 2021 1 repository listed
-
26 Jan 2021 1 repository listed
-
17 Dec 2020 1 repository listed
-
16 Dec 2020 1 repository listed
-
19 Oct 2020 1 repository listed
-
5 Oct 2020 1 repository listed
-
28 Sep 2020 1 repository listed
-
23 Sep 2020 1 repository listed
-
11 Sep 2020 1 repository listed
-
30 Jun 2020 1 repository listed
-
11 Jun 2020 1 repository listed
-
25 May 2020 1 repository listed
-
12 May 2020 1 repository listed
-
1 May 2020 1 repository listed
-
25 Apr 2020 1 repository listed
-
24 Apr 2020 1 repository listed
-
15 Apr 2020 1 repository listed
-
7 Apr 2020 1 repository listed
-
18 Feb 2020 1 repository listed
-
17 Feb 2020 1 repository listed Syntology official (archive's flag): 2 ran · 2 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified (of 2 harvested samples)
-
27 Jan 2020 1 repository listed
-
19 Dec 2019 1 repository listed Syntology official (archive's flag): 1 ran · 1 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified (of 1 harvested sample) · 1 pointer-only (licence)
-
20 Nov 2019 1 repository listed
-
24 Oct 2019 1 repository listed
-
12 Jun 2019 1 repository listed
-
16 May 2019 1 repository listed
-
13 Mar 2019 1 repository listed
-
21 Jan 2019 1 repository listed
-
18 Dec 2018 1 repository listed
-
4 Oct 2018 1 repository listed
-
24 Sep 2018 1 repository listed
-
22 Jul 2018 1 repository listed
Syntology lines on 11 of the papers shown; no Syntology record for the others (a paper without an arXiv id cannot be joined to the graph, and absence from the graph layer is not a recorded non-run). “Ran” means the sample executed on a synthesized fixture, not that the paper's result was reproduced; each line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections