<?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>Wt.exe on Journal of Connar</title><link>https://connar.github.io/tags/wt.exe/</link><description>Recent content in Wt.exe on Journal of Connar</description><generator>Hugo -- 0.147.3</generator><language>en-us</language><atom:link href="https://connar.github.io/tags/wt.exe/index.xml" rel="self" type="application/rss+xml"/><item><title>Weaponizing the windows terminal app</title><link>https://connar.github.io/posts/weaponizing-windows-terminal-app/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://connar.github.io/posts/weaponizing-windows-terminal-app/</guid><description>&lt;h2 id="execution-and-persistence-via-the-windows-terminal-app">Execution and persistence via the windows terminal app&lt;/h2>
&lt;h3 id="intro">Intro&lt;/h3>
&lt;p>We have seen cases in the past where threat actors target dev environments and config files to achieve stealthy execution and persistence. Because these files are trusted by the host applications and often ignored by traditional antivirus, they offer a good place to hide malicious actions.&lt;/p>
&lt;p>An example of this is the weaponization of project files, such as &lt;code>.csproj&lt;/code> files in &lt;a href="https://www.outflank.nl/blog/2023/03/28/attacking-visual-studio-for-initial-access/">visual studio projects&lt;/a>. In the past, visual studio code was used for initial access, where attackers embedded malicious MSBuild targets inside &lt;code>.csproj&lt;/code> files. When a developer opens or builds the project, visual studio automatically parsed these configurations and executed the hidden commands. The developer believes they are compiling code, but in reality the project file itself is acting as a dropper.&lt;/p></description></item></channel></rss>