How China and Russia's Starlink countermeasure plans work, and where they don't

In November 2023, researchers from China's main space contractor laid out a coordinated counter-Starlink architecture in a closed forum: joint frequency and orbital filings with Russia, a geographically selective electromagnetic-jamming plan built on common technical standards, and a separate menu of cyber and destructive options. A joint investigation by The Insider, Der Spiegel, and Le Monde obtained four of those forum presentations and a June 2023 working protocol, putting the specifics on the public record for the first time.

The countermeasure presentation is attributed to CASC researchers Huang Hui and Ren Jie, according to The Insider's reporting. The slides describe pressure at three levels: diplomatic and regulatory action, electromagnetic jamming, and cyber or destructive operations. The first level includes proposed coordination with Russia on spectrum and orbital filings at the International Telecommunication Union. The second proposes a jamming architecture that can be aimed selectively at geographic regions, anchored to shared technical standards so Chinese and Russian systems can interoperate. The third sketches cyber and kinetic options without specifying the conditions for use.

ChinaTalk's analysis treats the regulatory and jamming tracks as distinct and reads the investigation with one key caveat: there is no public evidence of a joint ITU filing. The forum slides describe what cooperation could look like, not a record of it being executed. That gap, between a paper architecture and a working capability, is where the story actually sits.

The absence of a joint filing matters because the regulatory lever is the most concrete mechanism on the table. Spectrum coordination at the ITU is how satellite operators secure interference protection for their downlink frequencies. A coordinated Chinese-Russian filing push could, in principle, complicate Starlink's access to specific bands or orbital slots in regions where the two countries have regulatory standing. Proposed filings are not the same as guaranteed exclusion, and the investigation does not claim they are. It is a pressure tool, not a switch.

The jamming track is more technically specified and less constrained by international process. The slides reportedly call for systems that can target Starlink service in chosen regions while sharing standards across operators. That design is consistent with the problem jamming solves: a wide-band uplink signal, applied locally, can deny service to a constellation's user terminals inside a defined area without affecting satellites outside it. The proposal language describes a system, not a deployed capability. The investigation does not establish that the architecture is operational or that any single jamming test has been run against Starlink traffic.

Cyber and destructive options appear in the slides as a separate, vaguer category. The investigation describes them as proposals; the reporting does not name targets, timelines, or operational status. Treating that menu as anything more than a list of theoretical responses would overreach the source record.

The 2023 timing is also part of the story. The forum meetings predated SpaceX's current Starlink scale: Starlink accounts for the majority of satellites in low Earth orbit, per industry tracking cited in the original reporting. The countermeasures were sketched when the constellation was smaller and when the regulatory environment for low Earth orbit spectrum was less settled. ChinaTalk notes that booster-recovery tests by Chinese launchers are a separate track from the counter-Starlink architecture; reusing first stages is the lever on launch cost and cadence, and the 2023 slides do not depend on a reusable-launcher program to be implementable.

What the investigation supports, in plain terms, is a documented Chinese-Russian discussion of coordinated regulatory, electromagnetic, and cyber options to constrain Starlink. What it does not support is a claim that any of these options is in place. The architecture is on paper; the deployment record is not.