<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Malware-Analysis on Suspicious Bytes</title><link>https://suspiciousbytes.com/en/tags/malware-analysis/</link><description>Recent content in Malware-Analysis on Suspicious Bytes</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 13 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://suspiciousbytes.com/en/tags/malware-analysis/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Read JavaScript That Was Written Not to Be Read</title><link>https://suspiciousbytes.com/en/posts/javascript-deobfuscation-walkthrough/</link><pubDate>Fri, 13 Nov 2026 00:00:00 +0000</pubDate><guid>https://suspiciousbytes.com/en/posts/javascript-deobfuscation-walkthrough/</guid><description>&lt;p&gt;Open the source of a phishing page, a malicious ad or a skimmer, and you&amp;rsquo;ll often find a wall of JavaScript that looks like someone fell asleep on the keyboard. Variable names like &lt;code&gt;_0x3c1e&lt;/code&gt;. Strings that make no sense. One line that scrolls for a minute.&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s obfuscation. The author wants the code to run, but not to be read.&lt;/p&gt;
&lt;p&gt;You don&amp;rsquo;t need to understand every line. You need to answer two questions: what does this script do, and who does it talk to? Most obfuscation is a stack of simple tricks you can peel off one layer at a time.&lt;/p&gt;</description></item></channel></rss>