<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mqtt on CuraSec</title><link>https://curasec.metacog.co.kr/tags/mqtt/</link><description>Recent content in Mqtt on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 15 Sep 2026 15:32:56 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/mqtt/index.xml" rel="self" type="application/rss+xml"/><item><title>BambooToken malware uses MQTT protocol for Windows/Linux C2</title><link>https://curasec.metacog.co.kr/insights/2026-09-15-bambootoken-malware-controls-windows-and-linux-systems-via-m/</link><pubDate>Tue, 15 Sep 2026 15:32:56 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-15-bambootoken-malware-controls-windows-and-linux-systems-via-m/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> MQTT as a C2 channel is an emerging evasion technique worth noting for threat modeling — if you run MQTT brokers or IoT infrastructure, review whether outbound MQTT to external brokers is permitted and consider blocking or monitoring it.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Plan:&lt;/strong> Build or tune detections for MQTT (port 1883/8883) traffic from endpoints to external brokers as a C2 indicator; the summary lacks published IOCs, but MQTT is not typically monitored in most SIEM/EDR rulesets and this framework&amp;rsquo;s activity dates to 2023.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>