This is your Red Alert: China's Daily Cyber Moves podcast. I’m Ting, your friendly neighborhood China-and-cyber nerd, and today’s episode of “please patch before breakfast” starts with Microsoft’s own house catching fire. Over the past forty-eight hours, the big story has been the Miasma worm ripping through 73 Microsoft GitHub repositories, including Azure and Microsoft Docs repos, in what security analysts are calling a classic software supply chain compromise. According to a recent cyber stand‑up briefing, Miasma spreads laterally between repos by abusing developer credentials and GitHub Actions automation, quietly injecting malicious code into libraries that American developers blindly trust. The timeline there: initial anomalous commits spotted earlier this week, emergency access restrictions by GitHub on Friday, and nonstop incident response all weekend as US companies scramble to verify every dependency baked into their CI/CD pipelines. Now, why do I, Ting, think this smells like Beijing’s playbook? Because it perfectly matches long‑running Chinese espionage patterns like Volt Typhoon and Salt Typhoon, which Cyber Security News notes were designed to burrow into US critical infrastructure and telecoms for the long game, not a quick ransomware payday. You don’t hijack Microsoft supply chain components unless you want durable, deniable access deep inside US government contractors, defense suppliers, and cloud providers. Layer two of today’s headache: Cisco’s SD‑WAN Manager zero‑day, CVE‑2026‑20245. Cisco has already warned that it’s being actively exploited with no patch available yet, and this platform controls routing for a huge chunk of US enterprise and government networks. An attacker who owns SD‑WAN Manager can reroute traffic, sniff sensitive data, or quietly create backdoors into every branch office on the map. Tie that to the Volt Typhoon reporting, and you get a very plausible escalation scenario: in a Taiwan or South China Sea crisis, those footholds become instant disruption tools against US logistics, ports, and power. Meanwhile, a Chinese state‑sponsored group tracked as UNC5221 is rolling out new persistence malware in Microsoft 365: a backdoor called Brickstorm plus Plunet and Agent PSD, designed to survive password resets and incident response. Think malicious OAuth apps, stealthy mail‑forwarding rules on executive inboxes, and PowerShell backdoors lurking in Azure. That’s classic pre‑positioning for political, military, and election‑related intelligence inside the United States. So what do you, my security‑savvy listeners, need to do right now? First, lock down your code: audit all GitHub and GitLab repos, enforce hardware‑key MFA for developers, and verify checksums and signatures for any Microsoft‑linked packages before you deploy. Second, cage the Cisco beast: move SD‑WAN Manager onto a hardened management network, restrict access by IP, slap firewalls around it, and crank up log monitoring for weird admin sessions and config changes. Third, hunt in Microsoft 365: review OAuth app registrations, service principal permissions, and mail rules on high‑value accounts; investigate logins from unusual geographies, especially tied to admin roles. Finally, prepare for escalation: run tabletop exercises where Chinese‑linked actors flip those access points during a geopolitical crisis; practice rapid network segmentation, failover, and manual operations for critical services. Thanks for tuning in, listeners, and don’t forget to subscribe for more China‑meets‑cyber deep dives. This has been a quiet please production, for more check out quiet please dot ai. For more http://www.quietplease.ai Get the best deals https://amzn.to/3ODvOta