GlassWorm Malware Returns – This Time Hijacking the Visual Studio Marketplace & OpenVSX

Malicious extensions were uploaded by attackers to the Microsoft Visual Studio Marketplace and the OpenVSX registry, frequently imitating the names, icons, and descriptions of real developer tools to deceive users into installing them. The installed extensions subsequently carried out malware attacks in a stealthy manner.

When the GlassWorm is installed, it is capable of stealing the credentials for NPM, GitHub, and OpenVSX, gaining access to crypto wallet information, and dropping backdoors through SOCKS proxies and invisible remote access tools, and it can also use the pilfered credentials to spread further.

Invisible Unicode characters are not visible in code editors, diffs, or even in many review tools, which makes it possible for the attackers to implant executable malicious logic that appears empty to people. This is often underestimated during normal code reviews and hence the virus manages to bypass the ordinary checks.

GlassWorm, unlike many other threats to supply chains that are dependent on single points of compromise, actually takes advantage of the theft of developer credentials plus the use of automated update processes for the purpose of infecting other packages. This is what makes the malware spread in a manner akin to a traditional worm in the environments of developers.

The campaign has resurged multiple times after initial removals. New waves of infected extensions have been found on both marketplaces after supposed containment, showing the threat is persistent until stronger vetting and controls are in place.

Look closely at publisher names (misspellings or variations from the official vendor), extension reviews and history, and be cautious with auto-updates. Use security tools that scan extensions for known IoCs and block invisible or obfuscated code patterns.

Treat the environment as fully compromised: isolate and rebuild systems where possible, rotate all developer credentials and tokens (npm, GitHub, VSX), audit code repos for unauthorized changes, and review other connected systems for lateral spread.

OpenVSX is a mix that is regulated cooperatively and openly and does not have security which gives it up to a certain extent. That doesn’t mean that OpenVSX is inherently unsafe, but it does highlight that there should be better scanning and filtering.

GlassWorm stands as a demonstration for enhancing the supply chain attacks-an attack in this version can hide code from human review, utilize a decentralized infrastructure like Blockchain for resilience, or weaponize the tools themselves. Vetting must be tightened, and malicious code must be trained for automated detection; in the end, the developer toolchain must be declared a critical threat surface.