It hides in plain sight, invisible to the human eye. A developer opens a file of code, scans it for problems, sees nothing unusual, and moves on. But embedded in the spaces between characters — in the encoding layer beneath what any editor or terminal will display — a malicious payload is already executing. Credentials are being harvested. Build systems are being compromised. And quietly, methodically, the infection is spreading. This is GlassWorm: a software supply chain attack that security researchers are calling one of the most sophisticated and consequential threats to emerge in the modern era of connected vehicle development. And it is not slowing down. For the automotive industry, which has spent the better part of a decade racing to transform cars into software-defined platforms — updatable over the air, packed with connected features, and increasingly dependent on the same open-source ecosystems that power the broader technology world — the campaign represents an unsettling new category of risk. The threat does not come through the vehicle itself. It comes through the pipelines used to build it. A Worm That Thinks Like a Developer GlassWorm was first identified by security researchers in the fall of 2025, when analysts at Koi Security observed a self-propagating malware campaign moving through developer environments at a scale that caught the industry off guard. The mechanism was deceptively simple and devastatingly effective: a developer downloads a compromised software component, the malware steals their publishing credentials, and those credentials are then used to push poisoned updates to legitimate packages — spreading the infection further with each iteration, silently and automatically. The campaign’s technical signature became its calling card. Rather than hiding malicious logic in code that a reviewer might catch, GlassWorm concealed its payloads using invisible Unicode characters — characters that render as nothing in