Rethinking Smart Contract Fuzzing: Fuzzing With Invocation Ordering and Important Branch Revisiting
Not on the map. Why?
Abstract (arXiv)
Blockchain smart contracts have given rise to a variety of interesting and compelling applications and emerged as a revolutionary force for the Internet. Quite a few practitioners have devoted themselves to developing tools for detecting bugs in smart contracts. One line of efforts revolve around static analysis techniques, which heavily suffer from high false-positive rates. Another line of works concentrate on fuzzing techniques. Unfortunately, current fuzzing approaches for smart contracts tend to conduct fuzzing starting from the initial state of the contract, which expends too much energy revolving around the initial state and thus is usually unable to unearth bugs triggered by other states. Moreover, most existing methods treat each branch equally, failing to take care of the branches that are rare or more likely to possess bugs. This might lead to resources wasted on normal branches. In this paper, we try to tackle these challenges from three aspects: (1) In generating function invocation sequences, we explicitly consider data dependencies between functions to facilitate exploring richer states. We further prolong a function invocation sequence S1 by appending a new sequence S2, so that S2 can start fuzzing from states that are different from the initial state. (2) We incorporate a branch distance-based measure to evolve test cases iteratively towards a target branch. (3) We engage a branch search algorithm to discover rare and vulnerable branches, and design an energy allocation mechanism to take care of exercising these crucial branches. We implement IR-Fuzz and extensively evaluate it over 12K real-world contracts. Empirical results show that: (i) IR-Fuzz achieves 28% higher branch coverage than state-of-the-art fuzzing approaches, and (ii) IR-Fuzz detects more vulnerabilities and increases the average accuracy of vulnerability detection by 7% over current methods.
Key facts. Cited by 9 papers in the map (data through 13 Oct 2026). First posted on arXiv 10 Jan 2023.
Builds on
No reference list yet.
Built on by
Citing papers per year: 2024: 3; 2025: 6.
9 papers.
- 2024Exposing the Deception: Uncovering More Forgery Clues for Deepfake Detectioncited by 47
- 2025LLMs in Software Security: A Survey of Vulnerability Detection Techniques and Insightscited by 44
- 2024Smart-LLaMA: Two-Stage Post-Training of Large Language Models for Smart Contract Vulnerability Detection and Explanationcited by 8
- 2025Smart-LLaMA-DPO: Reinforced Large Language Model for Explainable Smart Contract Vulnerability Detectioncited by 7
- 2025Logic Meets Magic: LLMs Cracking Smart Contract Vulnerabilitiescited by 5
- 2025SoK: Security and Privacy of AI Agents for Blockchaincited by 4
- 2025SAEL: Leveraging Large Language Models with Adaptive Mixture-of-Experts for Smart Contract Vulnerability Detectioncited by 2
- 2025UEChecker: Detecting Unchecked External Call Vulnerabilities in DApps via Graph Analysiscited by 1
- 2024ETGuard: Malicious Encrypted Traffic Detection in Blockchain-based Power Grid Systemscited by 0
- 2025SoK: Security and Privacy of AI Agents for Blockchain8 Sep 2025
- 2025UEChecker: Detecting Unchecked External Call Vulnerabilities in DApps via Graph Analysis2 Aug 2025
- 2025SAEL: Leveraging Large Language Models with Adaptive Mixture-of-Experts for Smart Contract Vulnerability Detection30 Jul 2025
- 2025Smart-LLaMA-DPO: Reinforced Large Language Model for Explainable Smart Contract Vulnerability Detection23 Jun 2025
- 2025LLMs in Software Security: A Survey of Vulnerability Detection Techniques and Insights10 Feb 2025
- 2025Logic Meets Magic: LLMs Cracking Smart Contract Vulnerabilities13 Jan 2025
- 2024Smart-LLaMA: Two-Stage Post-Training of Large Language Models for Smart Contract Vulnerability Detection and Explanation9 Nov 2024
- 2024ETGuard: Malicious Encrypted Traffic Detection in Blockchain-based Power Grid Systems20 Aug 2024
- 2024Exposing the Deception: Uncovering More Forgery Clues for Deepfake Detection4 Mar 2024