Shuohan Wu
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Research Subjects
Research Interests
Shuohan Wu has a total of 17 co-authors. Here are the top co-authors by number of shared publications:
- Xiapu Luo
The Hong Kong Polytechnic University, Hong Kong, China
5 shared publications - Hao Zhou
The Hong Kong Polytechnic University, Hong Kong, Hong Kong
4 shared publications - Zihao Li
The Hong Kong Polytechnic University, Hong Kong, Hong Kong
3 shared publications - Le Yu
School of Computer Science, Nanjing University of Posts and Telecommunications, Nanjing, China
2 shared publications - Shudi Bao
Ningbo Key Laboratory of Spatial Intelligence and Digital Derivative, Ningbo Institute of Digital Twin, Eastern Institute of Technology, Ningbo, China
2 shared publications - Chao Zhang
Tsinghua University, Beijing, China and Zhongguancun Laboratory, Beijing, China
1 shared publication
Latest Publications
- 21 January 2026
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Services Computing
- Vol. 19 (2) , 1406-1421
Mind the Service: What Crypto Wallets Aren’t Telling You
Web3 introduces a new paradigm of decentralized services, where users interact with distributed applications and digital assets without centralized intermediaries. Non-custodial wallets, as faithful practitioners of this philosophy, also serve as critical service interfaces, enabling users to store and transact digital assets independently without reliance on third parties. Although prior studies have examined non-custodial wallet design, most focus on generic app issues rather than the service-oriented software challenges unique to wallets, particularly overlooking their core feature-transaction. Since all user actions in the crypto world depend on transactions, the design and implementation of transaction features are critical to wallet usability and trustworthiness, yet remain largely underexplored. To bridge the gap, this paper proposes a five-phase, semi-automated approach that leverages dynamic analysis to thoroughly evaluate the design of transaction features from multiple perspectives. Our study of 77 popular wallets shows that the design of transaction features is often unsatisfactory, potentially undermining the quality and reliability of wallet services and, in some cases, leading to direct financial losses. We identify numerous common design flaws across these wallets and provide targeted recommendations for wallet developers to improve the quality of wallet. This work sheds light on a critical dimension of Web3 services.
- 21 January 2026
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Services Computing
- Vol. 19 (2) , 1406-1421
Mind the Service: What Crypto Wallets Aren’t Telling You
Web3 introduces a new paradigm of decentralized services, where users interact with distributed applications and digital assets without centralized intermediaries. Non-custodial wallets, as faithful practitioners of this philosophy, also serve as critical service interfaces, enabling users to store and transact digital assets independently without reliance on third parties. Although prior studies have examined non-custodial wallet design, most focus on generic app issues rather than the service-oriented software challenges unique to wallets, particularly overlooking their core feature-transaction. Since all user actions in the crypto world depend on transactions, the design and implementation of transaction features are critical to wallet usability and trustworthiness, yet remain largely underexplored. To bridge the gap, this paper proposes a five-phase, semi-automated approach that leverages dynamic analysis to thoroughly evaluate the design of transaction features from multiple perspectives. Our study of 77 popular wallets shows that the design of transaction features is often unsatisfactory, potentially undermining the quality and reliability of wallet services and, in some cases, leading to direct financial losses. We identify numerous common design flaws across these wallets and provide targeted recommendations for wallet developers to improve the quality of wallet. This work sheds light on a critical dimension of Web3 services.
- 1 January 2026
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Software Engineering
- Vol. 52 (9) , 1-17
SmarTracker: Leveraging LLMs to Automate User Behavior Tracking in Mobile Apps
- 1 January 2026
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Transactions on Software Engineering
- Vol. 52 (9) , 1-17
SmarTracker: Leveraging LLMs to Automate User Behavior Tracking in Mobile Apps
- Open Access
- 11 September 2024
- Published by Association for Computing Machinery (ACM)
- p. 1440-1452
Following the “Thread”: Toward Finding Manipulatable Bottlenecks in Blockchain Clients
Blockchain clients are the fundamental element of the blockchain network, each keeping a copy of the blockchain’s ledger. They play a crucial role in ensuring the network’s decentralization, integrity, and stability. As complex software systems, blockchain clients are not exempt from bottlenecks. Some bottlenecks create new attack surfaces, where attackers deliberately overload these weak points to congest client’s execution, thereby causing denial of service (DoS). We call them manipulatable bottlenecks. Existing research primarily focuses on a few such bottlenecks, and heavily relies on manual analysis. To the best of our knowledge, there has not been any study proposing a systematic approach to identify manipulatable bottlenecks in blockchain clients. To bridge the gap, this paper delves into the primary causes of bottlenecks in software, and develops a novel tool named ThreadNeck to monitor the symptoms that signal these issues during client runtime. ThreadNeck models the clients as a number of threads, delineating their inter-relationship to accurately characterize the client’s behavior. Building on this, we can identify the suspicious bottlenecks and determine if they could be exploited by external attackers. After applying ThreadNeck to four mainstream clients developed in different programming languages, we totally discover 13 manipulatable bottlenecks, six of which are previously unknown.
- 11 September 2024
- Published by Association for Computing Machinery (ACM)
- p. 1440-1452
Open AccessFollowing the “Thread”: Toward Finding Manipulatable Bottlenecks in Blockchain Clients
Blockchain clients are the fundamental element of the blockchain network, each keeping a copy of the blockchain’s ledger. They play a crucial role in ensuring the network’s decentralization, integrity, and stability. As complex software systems, blockchain clients are not exempt from bottlenecks. Some bottlenecks create new attack surfaces, where attackers deliberately overload these weak points to congest client’s execution, thereby causing denial of service (DoS). We call them manipulatable bottlenecks. Existing research primarily focuses on a few such bottlenecks, and heavily relies on manual analysis. To the best of our knowledge, there has not been any study proposing a systematic approach to identify manipulatable bottlenecks in blockchain clients. To bridge the gap, this paper delves into the primary causes of bottlenecks in software, and develops a novel tool named ThreadNeck to monitor the symptoms that signal these issues during client runtime. ThreadNeck models the clients as a number of threads, delineating their inter-relationship to accurately characterize the client’s behavior. Building on this, we can identify the suspicious bottlenecks and determine if they could be exploited by external attackers. After applying ThreadNeck to four mainstream clients developed in different programming languages, we totally discover 13 manipulatable bottlenecks, six of which are previously unknown.
- Open Access
- 12 April 2024
- Published by Association for Computing Machinery (ACM)
- p. 1-13
Are We There Yet? Unraveling the State-of-the-Art Smart Contract Fuzzers
- 12 April 2024
- Published by Association for Computing Machinery (ACM)
- p. 1-13
Open AccessAre We There Yet? Unraveling the State-of-the-Art Smart Contract Fuzzers
- Open Access
- 18 July 2022
- Published by Association for Computing Machinery (ACM)
- p. 629-641
NCScope: hardware-assisted analyzer for native code in Android apps
More and more Android apps implement their functionalities in native code, so does malware. Although various approaches have been designed to analyze the native code used by apps, they usually generate incomplete and biased results due to their limitations in obtaining and analyzing high-fidelity execution traces and memory data with low overheads. To fill the gap, in this paper, we propose and develop a novel hardware-assisted analyzer for native code in apps. We leverage ETM, a hardware feature of ARM platform, and eBPF, a kernel component of Android system, to collect real execution traces and relevant memory data of target apps, and design new methods to scrutinize native code according to the collected data. To show the unique capability of NCScope, we apply it to four applications that cannot be accomplished by existing tools, including systematic studies on self-protection and anti-analysis mechanisms implemented in native code of apps, analysis of memory corruption in native code, and identification of performance differences between functions in native code. The results uncover that only 26.8% of the analyzed financial apps implement self-protection methods in native code, implying that the security of financial apps is far from expected. Meanwhile, 78.3% of the malicious apps under analysis have anti-analysis behaviors, suggesting that NCScope is very useful to malware analysis. Moreover, NCScope can effectively detect bugs in native code and identify performance differences.
- 18 July 2022
- Published by Association for Computing Machinery (ACM)
- p. 629-641
Open AccessNCScope: hardware-assisted analyzer for native code in Android apps
More and more Android apps implement their functionalities in native code, so does malware. Although various approaches have been designed to analyze the native code used by apps, they usually generate incomplete and biased results due to their limitations in obtaining and analyzing high-fidelity execution traces and memory data with low overheads. To fill the gap, in this paper, we propose and develop a novel hardware-assisted analyzer for native code in apps. We leverage ETM, a hardware feature of ARM platform, and eBPF, a kernel component of Android system, to collect real execution traces and relevant memory data of target apps, and design new methods to scrutinize native code according to the collected data. To show the unique capability of NCScope, we apply it to four applications that cannot be accomplished by existing tools, including systematic studies on self-protection and anti-analysis mechanisms implemented in native code of apps, analysis of memory corruption in native code, and identification of performance differences between functions in native code. The results uncover that only 26.8% of the analyzed financial apps implement self-protection methods in native code, implying that the security of financial apps is far from expected. Meanwhile, 78.3% of the malicious apps under analysis have anti-analysis behaviors, suggesting that NCScope is very useful to malware analysis. Moreover, NCScope can effectively detect bugs in native code and identify performance differences.