Answers are grounded in this paper and cite their sources.
WebAssembly (Wasm) has emerged as a widely adopted binary instruction format that enables applications to run across diverse platforms with near-native performance. However, its compact and low-level structure makes it difficult to interpret. It is essential to identify the purpose of functions within WebAssembly binaries for both functionality understanding and security analysis. Developers often need to understand the functionality of obfuscated third-party WebAssembly modules, and attackers may employ obfuscation to conceal malicious applications. Identifying the intent of WebAssembly functions becomes more challenging when the binaries are obfuscated, as obfuscation techniques transform the code structure and logic. To address this challenge, we propose WASMOP, an obfuscation-resilient WebAssembly function classification framework, where functions are classified into semantic label categories serving as abstractions for function purpose. WASMOP utilizes Instruction Transition Matrices (ITMs) to extract features that are robust to obfuscation, which captures the contextual relationships between instructions. By analyzing WebAssembly files before and after obfuscation, it extract those semantic-related instruction transition patterns as features. We construct a dataset of 27,751 WebAssembly files sourced from real-world web deployments and open-source repositories, and apply multiple binary-level obfuscation techniques, categorizing the functions into 685 semantic labels. Our experiments show that WASMOP outperforms the state-of-the-art method by 15.4% on original binaries and by up to 29.8% under obfuscation, illustrating that our approach is effective at identifying function purposes in obfuscated WebAssembly binaries.
No takes yet. Share an insight, caveat, or question.
Zhang et al. (2026) studied this question.
Synapse has enriched 10 related papers. Consider them for comparative context: