/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Researcher details a backdoor in Huawei-owned HiSilicon chips used in millions of smart devices, including security cameras, that has been active since 2013

Researcher said he did not notify HiSilicon due to a lack of trust in the hardware vendor to adequately fix the issue.

ZDNet Catalin Cimpanu

Context & Ripple Effects

This lands on top of a years-long stack of Huawei security findings: Vodafone's earlier Telnet backdoor findings from 2011–2012, the Microsoft-discovered PCManager bug that behaved like NSA-style malware on MateBooks, and firmware testing that found vulnerabilities in 55% of sampled Huawei telecom device images. What is new here is the layer — not network gear or laptop software, but the HiSilicon system-on-chip itself, sitting inside millions of third-party security cameras and smart devices and reportedly active since 2013.

The disclosure path matters as much as the bug: the researcher says he skipped notifying HiSilicon entirely because he did not trust the vendor to fix it properly. That breaks the coordinated-disclosure model the industry runs on, and it set up Huawei's blanket denial two days later that it does not include backdoors in any product, HiSilicon included.

First-order effects

  • Millions of already-deployed cameras and smart devices built on HiSilicon silicon carry a vulnerability their owners cannot patch at the chip level, leaving integrators and end users exposed with no vendor advisory to work from.

Second-order effects

  • Device manufacturers that built product lines on HiSilicon chips inherit the reputational damage and face buyer pressure to prove their supply chain, while rival chip vendors gain a sales argument against Chinese silicon — a playbook the later undocumented ESP32 'backdoor' finding shows repeating across the category.

Third-order effects

  • When researchers conclude vendors will not fix disclosed flaws, private reporting collapses and findings surface unpatched in public — pushing procurement toward audited silicon provenance and making chip-level security review a structural requirement for any volume IoT supplier, regardless of country.

The trend: Security scrutiny of mass-deployed chips is moving trust debates upstream from patchable software to silicon provenance, where neither vendors nor disclosure norms currently offer a reliable fix path.

Discussion

  • @axcheron Alexandre Cheron on x
    0day vulnerability (backdoor) in firmware for HiSilicon-based DVRs, NVRs and IP cameras https://habr.com/...
  • @cybergibbons @cybergibbons on x
    Important to note this is not a hardware backdoor. You can use a HiSilicon chip and not use this software. Axis and Hikvision are not vulnerable AFAIK. https://twitter.com/...
  • @counternotions Kontra on x
    CCP in ur chipz. https://twitter.com/...
  • @phhaith1 Phaith on x
    HiSilicon SoC chips are backdoored with hardcoded knock sequence and hardcoded admin credentials. And HiSilicon is Huawei. Huawei backdoors their firmware QEDLMBO. https://www.zdnet.com/...
  • @taosecurity Richard Bejtlich on x
    I think @corelight_inc powered by real @Zeekurity is ready to detect these sorts of shenanigans, as the Telnet parser does not care about ports due to Dynamic Protocol Detection (DPD). If you're doing your #networksecuritymonitoring correctly you already know if you're affected. …
  • @iheartmalware Ronnie ‘BEC’ Tokazowski on x
    “...did not report the issue to HiSilicon citing a lack of trust in the vendor to properly fix the issue” After seeing IoT vendor responses post-Mirai, I don't blame the researcher one bit. https://www.zdnet.com/...
  • @campuscodi Catalin Cimpanu on x
    Backdoor mechanism discovered (again) in HiSilicon chips —Researcher did not notify HiSilicon due to a lack of trust in the vendor to patch the issue —Backdoor was first reported in 2013, and again in 2017, but inadequately patched all this time https://www.zdnet.com/... https://…