<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Malware | ConsulThink</title>
	<atom:link href="https://www.consulthink.it/tag/malware/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.consulthink.it</link>
	<description>IT consulting</description>
	<lastBuildDate>Fri, 09 Feb 2024 13:35:35 +0000</lastBuildDate>
	<language>it-IT</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://www.consulthink.it/wp-content/uploads/2020/02/logo-icon-87x87.ico</url>
	<title>Malware | ConsulThink</title>
	<link>https://www.consulthink.it</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Rustware Part 3: Dynamic API resolution</title>
		<link>https://www.consulthink.it/rustware-part-3-dynamic-api-resolution/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=rustware-part-3-dynamic-api-resolution</link>
		
		<dc:creator><![CDATA[Consulthink]]></dc:creator>
		<pubDate>Fri, 09 Feb 2024 10:55:00 +0000</pubDate>
				<category><![CDATA[ExperThinkers]]></category>
		<category><![CDATA[Offensive]]></category>
		<category><![CDATA[Offensive Security]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[Malware]]></category>
		<category><![CDATA[Rustware]]></category>
		<guid isPermaLink="false">https://www.consulthink.it/?p=10372</guid>

					<description><![CDATA[<p>In the previous blog post we have seen how to perform a shellcode process injection by finding a target process PID using several WinAPIs, in that case all the WinAPIs were called directly. Usually malwares resolve the WinAPI address at runtime in order to hide malicious behaviours during static analysis. In this blog post we ...</p>
<p>The post <a href="https://www.consulthink.it/rustware-part-3-dynamic-api-resolution/">Rustware Part 3: Dynamic API resolution</a> first appeared on <a href="https://www.consulthink.it">ConsulThink</a>.</p>]]></description>
		
		
		
			</item>
		<item>
		<title>Rustware Part 2: Process Enumeration Development</title>
		<link>https://www.consulthink.it/rustware-part-2-process-enumeration-development/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=rustware-part-2-process-enumeration-development</link>
		
		<dc:creator><![CDATA[Consulthink]]></dc:creator>
		<pubDate>Mon, 06 Nov 2023 12:18:11 +0000</pubDate>
				<category><![CDATA[Cyberattack]]></category>
		<category><![CDATA[CyberSecurity]]></category>
		<category><![CDATA[ExperThinkers]]></category>
		<category><![CDATA[Offensive Security]]></category>
		<category><![CDATA[Red Team]]></category>
		<category><![CDATA[Malware]]></category>
		<guid isPermaLink="false">https://www.consulthink.it/?p=10303</guid>

					<description><![CDATA[<p>In the previous blog post we have seen how to develop a Shellcode Process Injection in Rust; the described Process Injection flow relies on several WinAPIs: OpenProcess used to open a handle to the target process, then the VirtualAllocEx was used to allocate a new readable and writable region of memory into the target process, ...</p>
<p>The post <a href="https://www.consulthink.it/rustware-part-2-process-enumeration-development/">Rustware Part 2: Process Enumeration Development</a> first appeared on <a href="https://www.consulthink.it">ConsulThink</a>.</p>]]></description>
		
		
		
			</item>
	</channel>
</rss>
