<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Detection Engineering on Matt Suiche</title><link>https://www.msuiche.com/categories/detection-engineering/</link><description>Recent content in Detection Engineering on Matt Suiche</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 24 Aug 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://www.msuiche.com/categories/detection-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>ELEGANTBOUNCER: When You Can't Get the Samples but Still Need to Catch the Threat</title><link>https://www.msuiche.com/posts/elegantbouncer-when-you-cant-get-the-samples-but-still-need-to-catch-the-threat/</link><pubDate>Sun, 24 Aug 2025 00:00:00 +0000</pubDate><guid>https://www.msuiche.com/posts/elegantbouncer-when-you-cant-get-the-samples-but-still-need-to-catch-the-threat/</guid><description>&lt;h2 id="the-genesis-when-signatures-arent-enough"&gt;The Genesis: When Signatures Aren&amp;rsquo;t Enough &lt;a href="#the-genesis-when-signatures-arent-enough" class="anchor"&gt;🔗&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;In the world of mobile security research, there&amp;rsquo;s a recurring frustration that keeps many of us up at night: the most sophisticated exploits - the ones that really matter - are rarely shared. When &lt;a href="https://citizenlab.ca" target="_blank" rel="noopener"&gt;Citizen Lab&lt;/a&gt; and &lt;a href="https://blog.google/threat-analysis-group/" target="_blank" rel="noopener"&gt;Google TAG&lt;/a&gt; discover NSO Group&amp;rsquo;s latest 0-click exploits targeting journalists and activists, we get brilliant technical writeups, CVE numbers, and patches. What we don&amp;rsquo;t get? The actual samples.&lt;/p&gt;
&lt;p&gt;This isn&amp;rsquo;t a criticism - there are excellent reasons for limiting access to weaponized exploits. But it creates a fundamental problem: &lt;strong&gt;How do you protect against threats you&amp;rsquo;ve never seen?&lt;/strong&gt;&lt;/p&gt;</description></item><item><title>Researching BLASTPASS: Detecting the exploit inside a WebP file - Part 1</title><link>https://www.msuiche.com/posts/researching-blastpass-detecting-the-exploit-inside-a-webp-file-part-1/</link><pubDate>Wed, 27 Sep 2023 12:00:00 +0200</pubDate><guid>https://www.msuiche.com/posts/researching-blastpass-detecting-the-exploit-inside-a-webp-file-part-1/</guid><description>&lt;p&gt;&lt;p class="markdown-image"&gt;
 &lt;img src="./images/riff-webp-vp8l-whitebg.png" alt="Anatomy of a WebP file" /&gt;
&lt;/p&gt;&lt;/p&gt;
&lt;h2 id="introduction"&gt;Introduction &lt;a href="#introduction" class="anchor"&gt;🔗&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;Once again compression algorithms are showing us that they are ruling the internet. My initial encounter with compression algorithms was in the year 2007, while reversing the Windows hibernation file to reimplement the now well-known &lt;a href="https://github.com/MagnetForensics/rust-lzxpress" target="_blank" rel="noopener"&gt;Microsoft LZXpress&lt;/a&gt; which I discovered later was used in most Microsoft products until today. This journey continues today, with the scrutiny of the vulnerability CVE-2023-4863 located within the open-source &lt;a href="https://developers.google.com/speed/webp" target="_blank" rel="noopener"&gt;Libwebp&lt;/a&gt; library, affecting Chromium-based browsers such as such Mozilla, Chrome, and Edge but also messaging applications such as iMessage.&lt;/p&gt;</description></item><item><title>Researching FORCEDENTRY: Detecting the Exploit With No Samples</title><link>https://www.msuiche.com/posts/researching-forcedentry-detecting-the-exploit-with-no-samples/</link><pubDate>Mon, 19 Dec 2022 12:00:00 +0200</pubDate><guid>https://www.msuiche.com/posts/researching-forcedentry-detecting-the-exploit-with-no-samples/</guid><description>&lt;p&gt;Earlier this month, I reached out to my friend &lt;a href="https://twitter.com/chompie1337" target="_blank" rel="noopener"&gt;Valentina&lt;/a&gt; and told her I wanted to learn about macOS/iOS exploitation, so she recommended taking a look at the CVE-2021-30860 vulnerability, also known as FORCEDENTRY, and the prior work &lt;a href="https://github.com/jeffssh/exploits/tree/main/CVE-2021-30860" target="_blank" rel="noopener"&gt;her friend Jeffrey Hofmann posted on Twitter&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;One year ago, &lt;a href="https://googleprojectzero.blogspot.com/2021/12/a-deep-dive-into-nso-zero-click.html" target="_blank" rel="noopener"&gt;Google Project Zero published an analysis&lt;/a&gt; of the NSO iMessage-based zero-click exploit &lt;a href="https://citizenlab.ca/2021/09/forcedentry-nso-group-imessage-zero-click-exploit-captured-in-the-wild/" target="_blank" rel="noopener"&gt;caught in-the-wild by Citizen Lab&lt;/a&gt; and was dubbed as “one of the most technically sophisticated exploits we’ve ever seen” by the Google Project Zero team.&lt;/p&gt;</description></item></channel></rss>