Have you noticed how cheap attacking an Android app has become? Not just "free tools" cheap, but "AI writes an exploit while you make coffee and still have time to confidently hallucinate" cheap. And the people who were already organized and funded noticed that too. Today's most successful crews use AI the same way your team does, writing code, planning operations, iterating at speed. In the last few months alone, one crew walked away with billions (with a 'B') from a single attack; more bypass research was published openly; and new CVEs were found in the libraries, SDKs and kernel layers your app depends on. Hooking scripts may have once been a rite of passage, and the obfuscated `isSecure()` never was strong security. Now it's just decoration. Let's explore one app built in three different ways: one with the everyday obfuscation, another with a homemade vibe-coded RASP, and the last one with Licel's DexProtector. We'll run all three and evaluate what the logcat actually reveals: - Build a security lab: root an emulator, install Magisk, Xposed and Frida - See the insides of an app: disassemble and deobfuscate it - Reverse engineer a native SDK (NDK/JNI) - Mod an app: read, edit and repackage the APK - Inject arbitrary code with Frida and Xposed - Learn about other everyday security surfaces So you can leave this workshop with the ability to answer: "Does the security in my app hold up?"

These days, all we talk about is AI. But can it actually build an Android runtime protection that stands up to a highly-caffeinated reverse engineer vibe-hacking at 3 AM? In this session we'll explore what a RASP needs to survive in the wild, from dodging clever bypasses to surviving false positives. We're going to build a specially crafted Android RASP with the finest vibe to see if the output tokens are just hallucination lies, or if they are secure enough to actually earn the Production Ready™️ stamp. Agenda: •⁠ ⁠Create a foundational knowledge layer from open source projects, articles and book references - ⁠List what features a RASP need - Validate architectural ideas - Do the threat model of RASP structures •⁠ ⁠LLM project structure •⁠ ⁠Implement static analysis protection •⁠ ⁠Implement runtime analysis protection •⁠ ⁠Test the solution against most common attack vectors and false positives •⁠ ⁠Wrap up