<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Telecom-Breach on CuraSec</title><link>https://curasec.metacog.co.kr/tags/telecom-breach/</link><description>Recent content in Telecom-Breach 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/telecom-breach/index.xml" rel="self" type="application/rss+xml"/><item><title>3BB Breach: MeshCentral RMM Tool Abused as Backdoor for Root Access</title><link>https://curasec.metacog.co.kr/insights/2026-09-15-3bb-attacker-used-meshcentral-backdoor-for-root-access-targe/</link><pubDate>Tue, 15 Sep 2026 15:32:56 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-09-15-3bb-attacker-used-meshcentral-backdoor-for-root-access-targe/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Demonstrates how a legitimate open-source RMM platform (MeshCentral) can be weaponized for persistent root-level access — worth reviewing whether MeshCentral or similar tools are present in your environment and whether their exposure is authorized.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Plan:&lt;/strong> Living-off-the-land via legitimate RMM tooling is a growing evasion pattern; build or tune detections for unauthorized MeshCentral agent deployments and anomalous outbound connections to MeshCentral servers not in your approved asset inventory.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>