<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Frida on Blaž Škufca</title><link>https://blazskufca.com/tags/frida/</link><description>Recent content in Frida on Blaž Škufca</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 01 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blazskufca.com/tags/frida/index.xml" rel="self" type="application/rss+xml"/><item><title>Dynamic Analysis with Frida</title><link>https://blazskufca.com/projects/dynamic-analysis-with-frida/</link><pubDate>Sun, 01 Mar 2026 00:00:00 +0000</pubDate><guid>https://blazskufca.com/projects/dynamic-analysis-with-frida/</guid><description>&lt;style&gt;
 .post { max-width: min(800px, 100vw); overflow-x: hidden; }
 .post-content pre { max-width: 100%; overflow-x: auto; }
 .post-content table { display: block; max-width: 100%; overflow-x: auto; }
&lt;/style&gt;
&lt;h2 id="the-limits-of-static-analysis"&gt;The Limits of Static Analysis&lt;/h2&gt;
&lt;p&gt;In a &lt;a href="https://blazskufca.com/projects/bypassing-jni-security-on-android/"&gt;previous post&lt;/a&gt;, we explored how to defeat native anti-tamper checks by statically analyzing a library in &lt;a href="https://github.com/NationalSecurityAgency/ghidra"&gt;Ghidra&lt;/a&gt; and then patching the binary.&lt;/p&gt;
&lt;p&gt;Static analysis is a powerful first step, but it has one fundamental weakness: &lt;em&gt;&lt;strong&gt;you are reasoning about what the code does, not what it actually does at runtime.&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;</description></item></channel></rss>