< Back to situations

Monitor this situation.

[SITUATION] · [ACTIVE] · [TECHNOLOGY]

2 clusters · 3 sources · 17 days · First seen · Last updated

GitHub supply chain cyberattacks

Overview

Security researchers have identified large-scale cyberattacks targeting the GitHub developer platform through the manipulation of software repositories and automated workflows.

Initial reports from Socket indicated that since October 7, 2026, over 500 compromised accounts were used to inject malicious code into tens of thousands of repositories via manipulated GitHub Actions workflows. The primary objective of these attacks was to steal sensitive credentials, such as cloud infrastructure access keys and AI service keys, by transmitting data to a hardcoded IP address.

Subsequent findings by Wiz Research identified a specific campaign named ‘Gheist’ that had been active since September 15, 2026. This campaign utilized stolen tokens to commit a ‘sync-check’ workflow to accessible repositories. This workflow was designed to print repository secrets into workflow logs, which attackers then downloaded via the GitHub API before deleting the runs to evade detection. While GitHub implemented controls for public repositories, the campaign successfully targeted private and enterprise environments by using GitHub’s own API for exfiltration, bypassing traditional security measures that look for external outbound connections.

Entities

GitHub · Microsoft Security FORGE Lab · Socket · Microsoft · Wiz Research

Timeline

  1. [TECHNOLOGY] 3 sources
    Wiz Research identifies Gheist GitHub token abuse campaign

    The Gheist campaign uses compromised GitHub tokens to print repository secrets into workflow logs and exfiltrate them via the GitHub API, affecting over 850 accounts.

  2. [TECHNOLOGY] 3 sources
    GitHub accounts compromised in large-scale malicious code injection

    Over 500 compromised GitHub accounts have been used to inject malicious workflows into tens of thousands of repositories to steal cloud and AI credentials.

Sources

cybernoz.com · thehackernews.com · wiz.io