<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hardware-Backdoor on CuraSec</title><link>https://curasec.metacog.co.kr/tags/hardware-backdoor/</link><description>Recent content in Hardware-Backdoor on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 28 Aug 2026 21:21:40 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/hardware-backdoor/index.xml" rel="self" type="application/rss+xml"/><item><title>ZBT Routers Ship With Two Factory Implants Granting Unauthenticated Root</title><link>https://curasec.metacog.co.kr/insights/2026-08-28-china-made-zbt-routers-ship-with-two-implants-giving-unauthe/</link><pubDate>Fri, 28 Aug 2026 21:21:40 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-28-china-made-zbt-routers-ship-with-two-implants-giving-unauthe/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> ZBT is a niche brand unlikely in most enterprise estates, but the factory-implant nature and public PoCs on both CVEs elevate urgency if these devices are deployed; audit hardware inventory for any ZBT devices and replace or network-isolate them pending vendor response.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Plan:&lt;/strong> If ZBT routers appear anywhere in the estate, treat them as pre-compromised and hunt for anomalous outbound traffic or unexpected management-plane connections; also worth adding device-model detection logic for SPEAKINGSTONE/DARKLANTERN C2 patterns if VulnCheck publishes IOCs.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> A confirmed hardware supply-chain backdoor from a Chinese OEM reinforces the policy case for approved-hardware lists and firmware provenance requirements; useful context for board-level discussions on hardware procurement risk, though ZBT&amp;rsquo;s limited enterprise footprint makes immediate action unlikely for most organizations.&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> CVE-2026-74232 — CISA KEV: not listed, EPSS 0.00, public PoC on GitHub · CVE-2026-74233 — CISA KEV: not listed, EPSS 0.03, public PoC on GitHub&lt;/li>
&lt;/ul></description></item><item><title>Zbtlink Routers Ship With Factory Backdoor Enabling Unauthenticated Root Shells</title><link>https://curasec.metacog.co.kr/insights/2026-08-06-chinese-made-zbtlink-routers-ship-with-backdoor-that-opens-u/</link><pubDate>Thu, 06 Aug 2026 13:03:19 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-06-chinese-made-zbtlink-routers-ship-with-backdoor-that-opens-u/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> Zbtlink is a niche brand unlikely to appear in enterprise infrastructure, and no enrichment signals indicate active exploitation; however, the finding that backdoors persist across 2+ years of firmware images is a useful supply-chain sourcing reminder when evaluating network hardware vendors.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No IOCs or ATT&amp;amp;CK-mapped TTPs are available from the summary, and Zbtlink hardware is uncommon in enterprise estates, so there is no immediate hunt or detection to build; worth noting the beaconing behavior pattern if these devices ever appear in an asset inventory.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> This reinforces hardware supply-chain risk from certain manufacturers but is not a systemic enterprise event; useful context for a future board conversation on network equipment sourcing standards, but no same-week action is warranted.&lt;/li>
&lt;/ul></description></item></channel></rss>