<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Automation on Qtnes</title><link>http://qtnes.com/tags/automation/</link><description>Recent content in Automation on Qtnes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 22 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://qtnes.com/tags/automation/index.xml" rel="self" type="application/rss+xml"/><item><title>BotConf 2026 Android Workshop: A Practical Android Malware Analysis Playbook</title><link>http://qtnes.com/posts/botconf-2026-android-workshop---a-practical-malware-analysis-playbook/</link><pubDate>Wed, 22 Apr 2026 00:00:00 +0000</pubDate><guid>http://qtnes.com/posts/botconf-2026-android-workshop---a-practical-malware-analysis-playbook/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;The BotConf 2026 Android workshop was not a bag of random “look how clever this sample is” tricks. It was a workflow: learn how the APK is put together, figure out where the malware is hiding, watch what it does at runtime, and then automate the boring rabbit chase once the pattern starts repeating.&lt;/p&gt;
&lt;p&gt;That progression matters. A lot of Android reversing goes sideways because the analyst dives straight into strings or decompilation and never gets the bigger picture. This workshop does the opposite and treats the whole stack as layered:&lt;/p&gt;</description></item></channel></rss>