Nice Little Satellite You Got Here. Shame If Anything Were to Happen to It

Yesterday’s post presented the evidence for and the implications of Elon Musk’s throttling of Ukraine’s Starlink/Starshield access. Since then, additional evidence makes this an established fact. Most notably, reporting in the WSJ that Trump (on bended knee?) asked Musk to release his grip (and WSJ reporting today that uneven Starshield restrictions are still persisting even after Trump’s call). When asked about it, the normally no-filter Trump declined to answer. Mark that down as confirmation.

But it gets better! Today’s brief, co-authored with @LibertyLynx (who originated, architected, and built the entire SGP4 orbital, FCC regulatory, and corporate forensic investigation from the ground up), demonstrates the near certainty that in addition to undermining Ukraine’s defensive capabilities (where the 130 to 160 km/h speed cap cut Ukrainian Unmanned Systems Forces validated target output by 23.0%), Musk/SpaceX compromised, or at least threatened to compromise, Ukraine’s offensive capability. Specifically, its capability to attack refineries and other targets within Russia.

The brief is extremely detailed and extensive, so here’s the TLDR version (though I do encourage reading it). Ukraine relies on Starlink/Starshield to control drones for operations at the front (and the logistical zone) and counter Russian aerial attacks. It does not use Starlink for reconnaissance and targeting of strikes deep inside Russia. For that it relies on Synthetic Aperture Radar (SAR) imagery from the ICEYE-X36 (NORAD 59103) satellite, operated by ICEYE US (the U.S. subsidiary of a Finnish company, operating under FCC license S3165).

Beginning on 15 October, within 48 hours of the Starshield throttle, a Russian inspector satellite, COSMOS 2612 (NORAD 68762), maneuvered to within less than a kilometer of X36 (closing to 0.76 km in the public catalog, and within a few hundred meters per optical trackers). And here’s the thing. Russia relies on ground-based radars that can only observe an orbiting satellite like X36 for narrow time windows (leaving 6 to 11 hour tracking gaps), and which do not allow it to track X36 continuously and with sufficient precision to arrange an intercept in which COSMOS 2612 compressed 364.3 hours of natural orbital drift into a 25.5-hour sprint (a 14.29x closure compression from 425 km away, cutting separation by 382.7 km relative to its pre-sprint orbit), braked, and then remained within a kilometer for more than 12 hours before moving away. (And across every Russian maneuver transition, the public Space-Track catalog lagged behind by 19.4 to 22.7 hours.)

Who can provide that real-time information? SpaceX. At the exact time COSMOS 2612 began its sprint (15 October at 04:15 UTC), X36 sat inside a 401-meter public collision alert with SpaceX’s STARLINK-35856 (NORAD 67013, where SpaceX’s private operator ephemeris diverged from public data by 15.37 to 30.13 km while carrying a 2.862 km 3D position uncertainty). Because X36 only has one trajectory, this overlapping Starlink alert pinned X36 in place—preventing it from executing a 0.5 km evasive altitude drop as it had in June (which generates 71 km/day of drift and exits a 3 km Russian braking box in 61 minutes), while requiring X36 under FCC Condition 16 to coordinate its trajectory with SpaceX. Under SpaceX’s Space Safety Terms of Service (Appendix A and Section 4(b)), committed maneuver trajectories uploaded to SpaceX are exposed to third-party sharing with a $500 liability cap (Section 10). Moreover, SpaceX tracks the 540 to 550 km orbital shell at 10 to 15 minute intervals using its 31,000 Stargaze cameras—and conveniently onboarded Chinese operators to its Space Safety platform on 6 and 16 October. Again, with its ground resources alone, Russia would have been flying COSMOS 2612 blind.

No other entity has all five of these capabilities. The intercept would not have been possible without these capabilities.

Nice little satellite you got here. A shame if anything happened to it. A threat that could only have been delivered with the help of SpaceX/Starlink/Musk. I further note that Russia has not delivered a similar threat to any Starlink asset while Tesla’s Q3 10-Q (filed 30 September) discloses $5.966 billion in rolling Chinese working-capital debt maturing between October 2026 and September 2027 and explicitly admits “presumed significant influence” over SpaceX through their shared CEO.

Goldfinger famously said: “Once is happenstance. Twice is coincidence. Three times is enemy action.” The simultaneous throttling of Ukraine’s defensive capability and compromising/threatening of its offensive capability, the first definitively attributed to SpaceX and the second solely within SpaceX’s capability, makes plain that Musk has acted against Ukraine and for Russia. Enemy action, indeed.

SpaceX’s culpability here is indisputable. The only open question is whether Musk acted on his own, or in connivance with the administration/Pentagon. And just as was the case with yesterday’s post, both alternatives are disturbing in their own way.

Trump’s, Rubio’s, and Hegseth’s claims that the administration had nothing to do with throttling Starlink may or may not be true. Trump’s asking Musk pretty please to turn it back on could be genuine, or it could be Kabuki. Again, neither alternative is good. If the President of the United States is reduced to a supplicant, and Musk has the unilateral authority (shielded by commercial Terms of Service) to make decisions with such vital national security implications, and perhaps to do so in cooperation with American enemies, we are in a very bad place. Especially given how embedded SpaceX currently is within the Pentagon as we head toward Round Two with Iran.