/
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

Microsoft admits it signed a malicious driver called “Netfilter” targeting gaming environments; the rootkit malware was observed communicating with Chinese IPs

Microsoft has now confirmed signing a malicious driver being distributed within gaming environments. Source: Microsoft Security … .

BleepingComputer Ax Sharma

Context & Ripple Effects

Netfilter extends an earlier warning that flaws across dozens of third-party kernel drivers could yield elevated Windows privileges: a Microsoft signature made a malicious driver appear trusted rather than merely vulnerable. Later coverage shows the issue was not isolated, from driver-blocklist update failures to malware signed through Microsoft’s hardware program.

First-order effects

  • Gaming-environment users exposed to Netfilter faced a rootkit carrying a Microsoft signature and observed communications with Chinese IP addresses, undermining the trust signal Windows assigns to signed drivers.
  • Microsoft Security’s driver-signing process becomes the immediate control point under scrutiny because the signed artifact was malicious, not simply a compromised application.

Second-order effects

  • Windows defenses depend more heavily on timely blocklist distribution after a signed malicious driver is identified; the later failure to apply driver-blocklist updates shows how a certification error can persist at endpoints.
  • Hardware vendors and developers face greater pressure to secure driver-signing paths as attackers also used leaked NVIDIA code-signing certificates to sign Windows malware and tools.

Third-order effects

  • Windows kernel security is moving from a binary trust model based on signatures toward continuous revocation, blocklisting, and scrutiny of the software-delivery control plane.
  • If certification channels continue to be abused, platform operators will have to treat signed-driver ecosystems as shared security infrastructure rather than a one-time approval process.

The trend: Signed-driver trust is becoming a continuously managed Windows security boundary as attackers target both certification programs and the certificates behind them.

Discussion

  • @struppigel Karsten Hahn on x
    ☢️Network filter rootkit that connects to this IP in China: hxxp://110.42.4.180:2081/u It does not look like Moriya (signature will be corrected asap) File is signed by Microsoft. #rootkit #netfilter https://www.virustotal.com/...
  • @struppigel Karsten Hahn on x
    Update by Microsoft: https://msrc-blog.microsoft.com/ ... https://twitter.com/...