Find notable cyber news and cases, enriched with sources, timelines, and signals.

GlassWorm open-source supply-chain campaign targeting developers

Campaign
First reported
Last updated
Happening score
H score 48
2 unique sources, 4 articles

Summary

Hide ▲

The GlassWorm campaign has added a new Open VSX wave of 73 cloned VS Code extensions that impersonate legitimate packages to build trust before delivering malware. Six extensions were confirmed malicious, while the rest acted as sleeper packages that later updated into a hidden delivery path using a Zig dropper and a VSIX payload from GitHub. The payload is installed into multiple IDEs, including VS Code, Cursor, Windsurf, and VSCodium, to steal credentials, bookmarks, and other sensitive data while avoiding Russian systems.

Related Happenings

Deadcode09284814 malicious npm packages delivering Phantom Bot and infostealers

Malware Activity
First: 18.05.2026 11:57 Last: 18.05.2026 11:57 Sources 1

About this happening: Four **npm** packages published by **deadcode09284814** were found delivering **information-stealing malware** and **Phantom Bot** DDoS capability, putting installers at risk of *...

Mini Shai-Hulud supply-chain campaign targeting npm and PyPI

Campaign
First: 12.05.2026 17:45 Last: 12.05.2026 17:45 Sources 1

About this happening: The **Mini Shai-Hulud** **supply-chain campaign** linked to **TeamPCP** expanded into downstream victim reporting, including **Grafana Labs**. Grafana said its **GitHub environmen...

Latest development: 21.05.2026 11:00

Grafana Labs said its GitHub environment was accessed and its codebase downloaded, with additional internal operational information taken from GitHub repositories, after compromise linked to the Mini Shai-Hulud campaign and TanStack npm packages. Grafana said it first spotted malicious activity on May 11, discovered the unauthorized download on May 17, and after contact from the ransom gang rotated automation tokens, enabled enhanced monitoring, audited commits since the May 11 incident, and hardened its GitHub security posture, while saying there is no indication customer production systems or operations were compromised.

Shai-Hulud supply-chain campaign spreading via stolen CI/CD credentials

Campaign
First: 12.05.2026 14:29 Last: 12.05.2026 14:29 Sources 1

About this happening: The **Shai-Hulud** **supply-chain campaign** remains active across **npm**, **PyPI**, and **Composer**, with the latest reporting tying **TeamPCP** to both a claimed **GitHub inte...

Mini Shai-Hulud npm supply-chain malware wave

Malware Activity
First: 12.05.2026 14:07 Last: 12.05.2026 14:07 Sources 1

About this happening: The **Sha1-Hulud** npm supply-chain campaign is a fresh **second wave** of **Shai-Hulud**-style activity that has compromised **hundreds of npm packages**. The malware runs during...

TeamPCP Mini Shai-Hulud npm supply-chain campaign

Campaign
First: 12.05.2026 14:07 Last: 12.05.2026 14:07 Sources 1

About this happening: The **TeamPCP**-linked **Mini Shai-Hulud** campaign is a **malicious npm supply-chain operation** that steals developer credentials and abuses trusted publishing paths to spread t...

Timeline

  1. 17.03.2026 23:42 3 articles · 2mo ago

    GlassWorm renews multi-platform campaign across GitHub, npm, and VSCode/OpenVSX

    Campaign Scope Update

    GlassWorm renewed its supply-chain campaign against GitHub, npm, and VSCode/OpenVSX, with researchers identifying 433 compromised components this month across 200 GitHub Python repositories, 151 GitHub JS/TS repositories, 72 VSCode/OpenVSX extensions, and 10 npm packages. The operators compromised GitHub accounts to force-push malicious commits, published obfuscated code using invisible Unicode characters, and used Solana blockchain transactions as C2 to deliver a Node.js runtime and a JavaScript-based information stealer that targets cryptocurrency wallet data, credentials, access tokens, SSH keys, and developer environment data.

    Show sources
  2. 14.03.2026 14:55 1 articles · 2mo ago

    GlassWorm open-source supply-chain campaign targeting developers

    Initial Disclosure

    The earliest visible phase relied on seemingly standalone Open VSX extensions that later updated to pull in a **GlassWorm-linked** dependency. That transitive change created a hidden delivery path before the malicious payload became apparent.

    Show sources