{"id":17732,"date":"2026-04-20T08:42:43","date_gmt":"2026-04-20T06:42:43","guid":{"rendered":"https:\/\/www.uni.lu\/research-en\/?post_type=events&p=17732"},"modified":"2026-05-11T16:57:02","modified_gmt":"2026-05-11T14:57:02","slug":"doctoral-defence-marco-alecci","status":"publish","type":"events","link":"https:\/\/www.uni.lu\/research-en\/events\/doctoral-defence-marco-alecci\/","title":{"rendered":"Doctoral Defence: Marco ALECCI"},"content":{"rendered":"\n
<\/div>\n\n\n

The Doctoral School in Science and Engineering<\/a> is happy to invite you to Marco ALECCI\u2019s defence entitled<\/p>\n\n\n\n

\nContext Is Key: Combining Static Analysis and AI for Actionable Android App Analysis<\/h2>\n\n\n\n

Supervisor<\/strong>: Prof Jacques KLEIN<\/a><\/p>\n\n\n\n

Android apps are a central part of our lives; they support a wide range of activities such as communication, navigation, finance, health, and more. Apps handle sensitive data on a daily basis; therefore, ensuring their security and privacy is paramount. Today, app security heavily relies on automated analysis tools. Among these, static analyzers play a central role in identifying suspicious behaviors, potential vulnerabilities, and other security and privacy risks at scale.<\/p>\n\n\n\n

In practice, when static analysis tools are used, they often overwhelm practitioners with drastically large volumes of results. Inspecting all such outputs not only increases the cognitive burden on analysts but also reduces the practical utility of static analysis, making it difficult to extract actionable insights. Additionally, many of these results are false alarms or irrelevant to the specific analysis task, which limits their concrete actionability.<\/p>\n\n\n\n

One main reason for this limitation is that static analysis tools typically operate with limited awareness of the app\u2019s intended functionality and the analyst\u2019s objective. As an example, one may consider that some location data flowing out of a navigation app is part of its normal operation and expected behavior. At the same time, the same data flow in a calculator app may be highly suspicious and should be prioritized by an analyst. To make static analyzers practical and effective, such information must be taken into account. Hence, context is key.<\/p>\n\n\n\n

In this manuscript, we present contributions that address these challenges by improving the actionability and relevance of Android app static analysis. This work is organized into three parts.<\/p>\n\n\n\n

In Part I, we revisit Android app categorization, which directly affects an app\u2019s expected functionality. Existing categorizations, such as Google Play categories, are often too broad to capture meaningful behavioral differences between apps, limiting the effectiveness of context-aware analysis. To address this, we construct the first ground-truth dataset of fine-grained categorized apps and propose a new categorization approach, which better reflects the expected behavior of applications.<\/p>\n\n\n\n

In Part II, we introduce two analysis approaches leveraging multiple category-specific anomaly detection models to identify unusual behaviors: Difuzer++, which focuses on logic bombs, and DamFlow, which targets sensitive data leaks. By integrating contextual understanding of app behavior, these tools reduce the burden on the analyst and make the results more actionable.<\/p>\n\n\n\n

In Part III, we explore the analysis context itself. Specifically, we propose an LLM-based approach that allows practitioners aiming for data leak detection to focus on specific data flows (e.g., location data sent via SMS) rather than all possible flows. This approach allows prioritization of results based on the analysis objective while also reducing false negatives introduced by existing approaches. Altogether, this manuscript advances Android app analysis by combining app categorization, context-aware anomaly detection, and task-specific flow analysis. The contributions make static analysis outputs more relevant and actionable, empowering practitioners to efficiently identify security and privacy risks in real-world apps.<\/p>\n\n\n\n