How to detect/clean GlassWorm

-


What was GlassWorm?

GlassWorm is a sophisticated supply‑chain malware campaign that targeted software developers and the open‑source ecosystem. 

Key traits:

  • Spread via:
    • Malicious VS Code / OpenVSX extensions
    • Compromised npm and Python packages
    • Poisoned GitHub repositories 
  • Goal:
    • Steal credentials (GitHub, npm, cloud tokens)
    • Exfiltrate crypto wallets and secrets
    • Take over developer accounts and propagate further 
  • Big risk:
    • One compromised developer → downstream supply‑chain compromise impacting many organizations 

 Why it was so dangerous

GlassWorm was unusually hard to stop because of its resilient, multi-layered command-and-control (C2) design:

  • Solana blockchain → stored C2 addresses (immutable “dead drops”)
  • BitTorrent DHT → decentralized config distribution
  • Google Calendar → hidden encoded commands
  • Traditional servers → payload delivery 

👉 This meant:

Taking down one channel didn’t matter—the malware would just switch to another.

 What “disrupted” means

On May 26–27, 2026, a coordinated operation by:

  • CrowdStrike
  • Google
  • Shadowserver Foundation

simultaneously took down all four C2 channels. 

Result:

  • Attackers lost control of infected systems
  • Malware couldn’t receive new commands or payloads
  • Botnet effectively neutralized (disrupted) 

 Scope of the campaign

Before disruption:

  • Active since October 2025 
  • Hundreds of software artifacts and repos affected (300–400+) 
  • Tens of thousands of developers potentially exposed 

 Important: “Disrupted” ≠ “Gone”

Even though the infrastructure was taken down:

  • Infected machines may still exist
  • Stolen credentials can still be abused
  • Operators could rebuild infrastructure

Security researchers stress the threat actors are persistent and well-resourced 

 Bottom line

  • GlassWorm = advanced developer-targeting supply-chain malware
  • Disrupted = its control infrastructure was taken offline in a coordinated strike
  • Impact = major win for defenders, but not necessarily permanent

If you want, I can break down how to detect/clean GlassWorm in an enterprise environment or what indicators to look for—especially relevant given your sysadmin role

DETECTION — What to look for

GlassWorm hides in developer tooling and supply chains, so focus on dev endpoints and CI/CD systems first.

 Endpoint Indicators (dev machines)

Check for:

Suspicious developer artifacts

  • Unknown or recently installed:
    • VS Code / OpenVSX extensions
    • npm / pip packages
  • Especially anything installed outside approved repos or internal mirrors
<pre><code> // 
# Node
npm ls -g --depth=0

# Python
pip list

# VS Code extensions
code --list-extensions
 </code></pre>

Red flag: packages/extensions you didn’t explicitly approve.

🔐 Credential access activity

GlassWorm targets:

  • ~/.ssh
  • ~/.aws
  • ~/.config/gcloud
  • Git credential helpers

Check:

  • Unexpected file reads or exfil attempts
  • New/modified SSH keys
  • Recently accessed token files

🌐 Network anomalies

Look for these behaviors:

  • Connections to:
    • BitTorrent/DHT traffic (UDP-heavy, random peers)
    • Blockchain APIs (Solana RPC endpoints)
    • Google Calendar API from non-browser processes
  • Repeated DNS queries with encoded data patterns
# Example quick checks
netstat -ano
Get-NetTCPConnection # PowerShell

🧩 Code & Repo Indicators

Compromised repos/packages

  • Unexpected commits (especially:
    • obfuscated JS/py code
    • base64 blobs
    • eval(), exec())
  • Maintainer account changes
  • Release versions that:
    • differ from source
    • include injected scripts
grep -r "eval(" .
grep -r "base64_decode" .
``

⚙️ CI/CD Pipeline Indicators

  • New build steps added silently
  • Secrets accessed during builds unexpectedly
  • Builds reaching external endpoints (non-whitelisted)

 2. CONTAINMENT — Stop the spread fast

 Immediate actions (high priority)

1. Isolate infected systems

  • Remove from network (EDR quarantine or VLAN isolation)

2. Revoke ALL credentials from affected systems

  • GitHub / GitLab tokens
  • npm, PyPI tokens
  • AWS / Azure keys
  • SSH keys

👉 Assume token theft already happened

3. Block known abuse channels

At firewall / proxy level:

  • BitTorrent / DHT traffic
  • Solana RPC endpoints
  • Suspicious Google API patterns

4. Freeze affected repos

  • Lock pushes
  • Disable CI pipelines temporarily
  • Audit recent commits

 3. ERADICATION — Cleaning infected hosts

 Option A (recommended): Rebuild

GlassWorm is stealthy → safest path is:

✅ Wipe and reimage dev machines

Then:

  • Install only approved tooling
  • Enforce package allowlists

🛠️ Option B: Manual cleanup (if rebuild not possible)

Remove malicious artifacts

  • Uninstall unknown VS Code extensions
  • Remove suspicious npm/pip packages
npm uninstall -g <package>
pip uninstall <package>

Kill persistence mechanisms

Check:

  • Startup scripts:
    • ~/.bashrc, .zshrc
    • Windows Run keys
  • Scheduled tasks
  • Cron jobs
  • Verify system binaries
  • Run integrity checks (EDR or file hash baseline)
  • Look for replaced tooling (node, python wrappers)

 4. RECOVERY — Secure re-entry

 Credentials reset (critical)

  • Rotate:
    • API keys
    • SSH keys
    • OAuth tokens
  • Force developer password resets

Audit supply chain

  • Rebuild all artifacts from:
    • clean source
    • trusted dependencies
  • Re-publish known-good package versions

 Strengthen controls

✅ Implement:

  • Dependency allowlisting
  • Private package registries (Artifactory, Nexus)
  • Signed packages (Sigstore, etc.)

✅ Enforce:

  • MFA everywhere (GitHub, cloud)
  • Least privilege tokens

 5. PREVENTION — Future hardening

Developer environment controls

  • Block:
    • direct npm/pip installs from internet
  • Force:
    • internal mirrors only

Monitoring rules to add

SIEM / EDR detections:

  • Processes accessing:
    • SSH keys + network connections simultaneously
  • Non-browser apps hitting:
    • Google APIs
  • DHT / P2P traffic from dev machines

Git security

  • Signed commits required
  • Branch protections enforced
  • Alert on:
    • new maintainers
    • token usage from new locations

 Quick Triage Checklist

If you suspect GlassWorm:

  • Identify dev machines with new packages/extensions
  • Check for unusual outbound traffic (DHT/blockchain/API)
  • Revoke all credentials immediately
  • Freeze repos + audit commits
  • Rebuild affected machines
  • Rotate all secrets

 Reality Check

Glass Worm is dangerous because:

  • It moves through trust chains (developers → packages → orgs)
  • It steals credentials before you notice
  • It persists across multiple channels

👉 So assume:

If one dev box is hit → your supply chain may be impacted


Comments

Post a Comment

Popular posts from this blog

Entire List Leaked for Canvas Ransomware Attack

-
Image
  ( NOTE FROM REDDITOR: All attempts at requesting edit access will be denied. If something is needed, you may email me at: storeluxorsales@gmail.com ) I am not affiliated with this group in any way - so also, please do stop asking (looking at you random press sites). - If anyone wants to save this document, feel free to make a copy. I will be deleting this copy on 10/1/2026. File from link begins below this line. _____________________ This file has been downloaded from the ShinyHunters Data Leak Site (DLS). Our DLS is accessible at these locations:     - http://shnyhntww34phqoa6dcgnvps2yu7dlwzmy5lkvejwjdo6z7bmgshzayd.onion/     - http://shinypogk4jjniry5qi7247tznop6mxdrdte2k6pdu5cyo43vdzmrwid.onion/ > These files were leaked on the ShinyHunters DLS because the victim did not pay a ransom or cooperate and comply with the ShinyHunters group. src;refs;lnks; http://web.archive.org/web/20260322033123/https://shinyhunte.rs/ http://web.archive...
Read more

WSUS CVE-2025-59287 Mitigation

-
Image
CVE-2025-59287 is a critical Remote Code Execution (RCE) vulnerability affecting Windows Server Update Services (WSUS) . Here's a detailed breakdown of what it is, how it works, and what you should do about it: Overview Disclosed: October 2025 Patch Tuesday CVSS Score: 9.8 (Critical) Affected Systems: Windows Server 2012 through 2025 (including Server Core installations) Exploitability: Microsoft rates it as “Exploitation More Likely” Technical Details The vulnerability arises from unsafe deserialization of untrusted data in WSUS. Specifically, the GetCookie() endpoint in WSUS processes encrypted AuthorizationCookie objects without proper type validation. The deserialization occurs via .NET BinaryFormatter , which is known to be insecure when handling untrusted input. Attackers can send a crafted SOAP request to WSUS over port 8530 , containing a malicious AuthorizationCookie . The cookie is decrypted using a hardcoded AES key and then deserialized, allow...
Read more

Cloud Infrastructures are Having a Bad Week

-
Image
  Today’s disruptions across Microsoft Azure and Amazon Web Services (AWS) were significant, but they’re not signs of cloud computing’s demise. Instead, they underscore the risks of centralization and the importance of designing systems that can withstand provider-level failures. What happened today? • Microsoft Azure outage: Azure’s Front Door service suffered a major disruption due to a misconfiguration, impacting services like Outlook, Xbox, Microsoft 365, and even third-party platforms like Starbucks and Alaska Airlines. The Azure website states a little more than disruption. "Azure Front Door - Connectivity issues - Observing recovery Starting at approximately 16:00 UTC on 29 October 2025, customers and Microsoft services leveraging Azure Front Door (AFD) may have experienced latencies, timeouts, and errors. We have confirmed that an inadvertent configuration change was the trigger event for this issue. Affected Azure services may have included, but were not limited to: App S...
Read more

CVE-2025-58034 Fortinet Warnings and Mitigation

-
Image
Type: OS Command Injection vulnerability (CWE-78) Affected Product: Fortinet FortiWeb (Web Application Firewall) Affected Versions: 8.0.0 – 8.0.1 7.6.0 – 7.6.5 7.4.0 – 7.4.10 7.2.0 – 7.2.11 7.0.0 – 7.0.11 [nvd.nist.gov] , [cvedetails.com] Description The vulnerability is caused by improper neutralization of special elements used in OS commands . An authenticated attacker can exploit this flaw by sending crafted HTTP requests or CLI commands , allowing them to execute arbitrary code on the underlying system. This can compromise the integrity, confidentiality, and availability of the device. [nvd.nist.gov] , [cvedetails.com] Severity CVSS v3.1 Base Score: 7.2 (High) Vector: AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H Attack Vector: Network Attack Complexity: Low Privileges Required: High User Interaction: None Impact: High on Confidentiality, Integrity, and Availability [cvedetails.com] Exploitation Status Actively Exploited: Yes. Fortinet confirmed expl...
Read more

Broadcom is dismantling of VMware Cloud Service Providers (VCSPs)

-
Image
  What Broadcom Is Doing to the VCSP Program 1. Broadcom is shutting down the existing VCSP program Multiple sources confirm that Broadcom issued formal non‑renewal notices to many VMware Cloud Service Providers, ending contracts as of January 26, 2026 . Partners may finish existing commitments but cannot renew or create new long‑term contract commitments . 2. Moving to an invite‑only VCSP ecosystem Broadcom is replacing the open VCSP model with a highly selective, invite‑only program , keeping only a small fraction of providers . For example: • Only 19 providers in the U.S. were retained out of thousands. • Hundreds of European providers are being cut loose. 3. White Label program sunset (critical for smaller providers) The White Label model—previously the path for smaller CSPs—has been terminated (or will be phased out depending on region). This effectively eliminates market access for many small providers. 4. Providers that are cut must hand off customers Broadcom directs ...
Read more

FBI Seizes RAMP Cybercrime Forum

-
Image
The FBI has taken down RAMP (Russian Anonymous Marketplace) , one of the most active cybercrime forums used by ransomware gangs, initial access brokers, malware sellers, and extortion groups . The takedown affected both the clearnet and dark‑web (Tor) domains, which now display official FBI/DOJ seizure notices. Why RAMP Was Significant RAMP was: Known as “the only place ransomware allowed.” A major hub for groups including LockBit, ALPHV/BlackCat, Conti, DragonForce, Qilin, RansomHub , and more. A high‑trust marketplace offering malware, exploits, tutorials, and escrow services . Home to 14,000+ vetted users , some paying fees for anonymity. Impact of the Seizure 1. Major Disruption to Criminal Infrastructure The takedown is seen as a meaningful blow against ransomware‑as‑a‑service communities. 2. Forced Migration to Other Forums Criminal groups are already shifting activity to alternative platforms like Rehub . These migrations are chaotic and risky for criminals due to: Loss of rep...
Read more

Instagram Data Leak Update

-
Image
  Instagram Data Leak What Happened? Cybersecurity firm Malwarebytes discovered a dataset containing personal information from approximately 17.5 million Instagram accounts circulating on dark web forums. The leaked data reportedly includes: Usernames Email addresses Phone numbers Partial physical addresses In some cases, location details .  How Did It Occur? The data appears to have been scraped via Instagram’s API , likely exploiting weaknesses in rate-limiting or privacy safeguards. A threat actor using the alias “Solonik” posted the dataset on BreachForums, claiming it originated from a 2024 API leak . Meta (Instagram’s parent company) denies any breach of internal systems , stating that the surge in password reset emails was due to a bug that allowed external parties to trigger reset requests, not unauthorized access. Risks to Users Phishing & Social Engineering: Attackers can craft convincing messages using real account details. SIM-Swapping & Account Takeove...
Read more

CodeRED emergency alert system is currently down across many regions!

-
Image
  CodeRED emergency alert system is currently down across many regions in the U.S. following a ransomware attack on its vendor, Crisis24. The incident has disrupted critical emergency communications and exposed user data. What Happened Attack Type : Ransomware Threat Actor : INC ransomware group Target : OnSolve CodeRED platform (owned by Crisis24) Impact : Emergency alerts (weather, missing persons, terror threats) are unavailable in many municipalities. Personal data compromised : names, addresses, emails, phone numbers, and passwords used to create CodeRED accounts. Key Details Date of Outage : Began in early November 2025, publicly confirmed Nov 26 Scope : Hundreds of municipalities affected nationwide Response : Crisis24 is migrating customers to a new CodeRED platform hosted in a separate, hardened environment. Some cities (e.g., Douglas County, CO) have terminated their CodeRED contracts and are seeking replacements. Others are using social media, door-...
Read more

SitusAMC Breached!

-
Image
  What Happened? On November 12, 2025 , SitusAMC detected unauthorized access to its systems. Hackers exfiltrated sensitive corporate and client-related data. The attack did not involve ransomware or encrypting malware , suggesting the goal was data theft rather than disruption. [techcrunch.com] Data Impacted Corporate data : Accounting records, legal agreements, and internal contracts. Client-related data : Information tied to residential mortgage loans, which may include personally identifiable information (PII) such as Social Security numbers and financial details. The exact scope and number of affected individuals is still under investigation. [ibtimes.co.uk] Who Is Affected Major U.S. banks including JPMorgan Chase, Citigroup, and Morgan Stanley were notified that their data may have been exposed. SitusAMC works with hundreds of lenders, so the potential ripple effect across the financial sector is significant. [webpronews.com] SitusAMC has contained the breach,...
Read more

Notepad++ update service was compromised

-
Image
  Notepad++ update service was compromised Multiple independent security investigations confirm that Notepad++’s update infrastructure was hijacked between June and December 2025 . This was a supply-chain attack originating from a compromise at the hosting‑provider level , not from Notepad++’s code. What exactly was compromised? 1. Update traffic was intercepted and redirected Attackers manipulated the update endpoint ( getDownloadUrl.php ) so that some users requesting updates were silently redirected to malicious servers serving tampered executables . 2. It was targeted , not widespread All sources emphasize that only specific users were affected, likely in an espionage‑focused campaign , not a mass malware distribution effort. 3. Hosting provider compromise, not a Notepad++ bug The attackers gained access to the shared hosting environment , losing direct access in September 2025 but maintaining stolen internal service credentials through December 2, 2025. Attribution: Likely...
Read more