<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Jscript on Matt Swann — Detection Engineering &amp; Threat Intel</title><link>http://mattswann.dev/tags/jscript/</link><description>Recent content in Jscript on Matt Swann — Detection Engineering &amp; Threat Intel</description><image><title>Matt Swann — Detection Engineering &amp; Threat Intel</title><url>http://mattswann.dev/og-image.png</url><link>http://mattswann.dev/og-image.png</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 12 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://mattswann.dev/tags/jscript/index.xml" rel="self" type="application/rss+xml"/><item><title>When Comments Aren't Comments: Decoding An Obfuscated JavaScript Sample</title><link>http://mattswann.dev/posts/when-comments-arent-comments-obfuscated-javascript/</link><pubDate>Sun, 12 Jul 2026 00:00:00 +0000</pubDate><guid>http://mattswann.dev/posts/when-comments-arent-comments-obfuscated-javascript/</guid><description>An obfuscated JavaScript sample was observed on a device with an oddly large comment block at the top of the code. Students of programming are often taught that comments are not part of code itself and serve no other purpose other than to provide explanations for code blocks. In this article, we explore why that isn&amp;rsquo;t always true.</description></item></channel></rss>