GitHub: Malicious Workflows Steal Cloud Credentials

SOC Briefing Summary :: Executive Key Takeaways
- [01]Threat summary: Threat actors actively target vulnerabilities in GitHub to achieve unauthorized ingress or security bypass.
- [02]Root cause vector: Adversaries exploit architectural trust flaws, unvalidated input, or memory corruption.
- [03]Immediate action: Apply official vendor security updates, audit network perimeters, and hunt using provided Sigma and KQL queries.
At-A-Glance Incident Diagnostic Telemetry
| Diagnostic Metric | Operational Telemetry & Defense Status |
|---|---|
| Advisory Authority | CyberNewsAI Threat Intelligence & Incident Response Directorate |
| Threat Severity Rating | MEDIUM (CVSS v3.1: 5.5 / Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N) |
| Exploitation Activity | 🟢 NO KNOWN IN-THE-WILD EXPLOITATION DETECTED |
| Remediation State | OFFICIAL VENDOR PATCH AVAILABLE (Deploy Immediately) |
| CISA KEV Catalog | MONITORED FOR CISA KEV CATALOG INGESTION |
| Targeted Perimeter | Cloud Tenancies, SaaS Environments & Identity Providers |
| Continuous Monitoring | ACTIVELY MONITORED // Telemetry Verified: 2026-11-13 |
---
Executive Incident Briefing (2-Minute CISO Brief)
1. Strategic Incident Overview
A malicious campaign dubbed 'wfx-loot' has targeted tens of thousands of GitHub repositories, stealing GitHub Actions secrets and cloud credentials from at least 1,835 targets. The threat actor used compromised GitHub accounts to open pull requests and inject malicious code, with some of the compromised accounts belonging to high-profile organizations. The campaign began on November 10 and involved the delivery of a 1,500-line credential-stealing shell script that supports cloud privilege escalation.
The script was able to exchange GitHub OIDC tokens for temporary AWS, Azure, and GCP cloud sessions and establish persistent access by creating long-lived credentials or modifying cloud identity and trust policies. The collected data was exfiltrated via HTTP POST to attacker-controlled endpoints, and the attacker quickly reverted their changes and deleted workflow runs and logs.
Repository owners are advised to look for the 'wfx-docs' branch, the probe pull request, and gaps in workflow run numbers, and to rotate all secrets and cloud roles available to the affected workflows immediately.
2. Business Impact & Perimeter Exposure
The wfx-loot campaign has the potential to impact a wide range of organizations that use GitHub and cloud services, including Fortune 100 companies and government agencies. The campaign highlights the importance of monitoring GitHub repositories for suspicious activity and rotating secrets and cloud roles regularly.
3. Compliance & Governance Blast Radius
The wfx-loot campaign may trigger applicable regulatory requirements, such as GDPR Art. 33 and NIS2, depending on the affected sector and geography. Repository owners are advised to review their compliance obligations and take steps to mitigate the risk of similar campaigns in the future.
---
Technical Vulnerability Analysis & Attack Chain

Root-Cause & Exploitation Mechanics
The wfx-loot campaign used malicious workflows to steal GitHub Actions secrets and cloud credentials, with the threat actor using thousands of compromised GitHub accounts to open pull requests against repositories those accounts could access. The campaign involved the delivery of a 1,500-line credential-stealing shell script that was able to modify an existing GitHub Actions workflow, add a new workflow on a short-lived branch, or plant an npm install hook.
The script supported cloud privilege escalation by exchanging GitHub OIDC tokens for temporary AWS, Azure, and GCP cloud sessions and was able to establish persistent access by creating long-lived credentials or modifying cloud identity and trust policies. The collected data was compressed into tarballs and exfiltrated via HTTP POST to one of two attacker-controlled endpoints.
The researchers believe the threat actor's primary objective was to steal CI secrets, while the package releases were a byproduct of automated publishing. The researchers also found certain overlaps with the 2025 GhostAction campaign.
The campaign highlights the importance of monitoring GitHub repositories for suspicious activity and rotating secrets and cloud roles regularly. It also underscores the need for repository owners to be vigilant in reviewing pull requests and workflow changes.
Adversary Ingress & Lateral Traversal Pipeline
The threat actor used compromised GitHub accounts to open pull requests against repositories those accounts could access, testing whether they had sufficient write permissions to inject malicious code. The attacker then delivered a 1,500-line credential-stealing shell script that was able to modify an existing GitHub Actions workflow, add a new workflow on a short-lived branch, or plant an npm install hook.
The script supported cloud privilege escalation by exchanging GitHub OIDC tokens for temporary AWS, Azure, and GCP cloud sessions and was able to establish persistent access by creating long-lived credentials or modifying cloud identity and trust policies.
---
MITRE ATT&CK Tactics, Techniques & Procedures (TTPs)
| Tactic | Technique ID | Technique Name | Operational Context |
|---|---|---|---|
| Initial Access | T1190 | Exploit Public-Facing Application | Remote zero-day / N-day exploitation of edge devices |
| Execution | T1203 | Exploitation for Client Execution | Malicious code execution within target process context |
| Defense Evasion | T1027 | Obfuscated/Compressed Payloads | Ephemeral memory-resident binaries and anti-forensics |
| Command and Control | T1071.001 | Web Protocols | Utilizing TLS/HTTP encrypted streams for beaconing |
| Collection | T1005 | Data from Local System | Harvesting organizational telemetry and credentials |
---
Threat Actor Profile & Exploitation Telemetry
Unattributed
---
Detection & SOC Mitigation Playbook
1. Patch Deployment & Workaround Engineering
Review official vendor security bulletins and deploy released security hotfixes across all production and staging environments immediately.
2. Network & Perimeter Defenses
- Restrict administrative ingress to dedicated, non-routable management subnets requiring hardware MFA.
- Enforce strict egress inspection to drop outbound connection attempts to unauthorized public IP space.
3. Endpoint Detection & Hunting Query
Sigma Rule: GitHub Behavioral Detection
title: GitHub Malicious Workflow Detection
description: Detects malicious GitHub workflows that steal cloud credentials
status: experimental
tags: [github, cloud, credentials]
author: [Your Name]
logsource:
product: github
service: actions
definition: 'GitHub Actions workflow'
detection:
selection:
workflow_name: 'wfx-docs'
action: 'push'
condition: selectionMicrosoft Sentinel Hunting Query (KQL)
let github_actions = GitHubActions
| where WorkflowName == 'wfx-docs' and Action == 'push'
| project WorkflowName, Action, RepositoryName, Actor4. Verification & Diagnostic Audit Checklist
- Monitor GitHub repositories for suspicious activity
- Rotate secrets and cloud roles regularly
- Review pull requests and workflow changes carefully
- Implement automated publishing safeguards to prevent malicious package releases
- Consider implementing a Web Application Firewall (WAF) to detect and prevent malicious traffic
- Review compliance obligations and take steps to mitigate the risk of similar campaigns in the future
---
Indicators of Compromise (IOCs)
No specific binary hashes were published in the authoritative advisory; hunt using behavioral telemetry and detection rules above.
---
Frequently Asked Questions (FAQ)
1. Is GitHub actively exploited in the wild?
While no mass exploitation has been publicly observed to date, the severity of the flaw warrants urgent patch deployment ahead of weaponization.
2. Which systems, applications, and perimeters are affected?
The vulnerability primarily impacts GitHub installations exposed to public-facing internet traffic or unauthenticated internal network segments.
3. What immediate remediation or patch should organizations deploy today?
Deploy the official security hotfixes released by the vendor immediately. If patching cannot be completed today, implement network ingress restrictions and isolate management interfaces.
4. How can security operations teams detect and hunt for this threat?
Defenders should monitor process creation logs for abnormal shell executions under web servers (e.g. bash, powershell under nginx/httpd) using the provided Sigma rule and Microsoft Sentinel KQL query.
---
Related Topic Cluster Intelligence
- ShinyHunters Abuses SSO via Vishing for Cloud Data Theft: Threat actors, including ShinyHunters, are using vishing and phishing kits to steal SSO credentials, bypass MFA, and exfiltrate data from enterprise SaaS applications like Salesforce and Microsoft 365.
- Gitee Repos: How to Detect Exposed Cloud & AI Credentials: Critical security intelligence alert regarding Gitee Repos: How to Detect Exposed.
- In-Browser ClickFix Abuses Google Sheets C2 to Steal Crypto: Cisco Talos uncovered an in-browser ClickFix campaign abusing the Google Visualization API and Google Sheets as C2 to inject malicious JavaScript and hijack cryptocurrency swap transactions.
// VERIFIED_SOURCES_&_REFERENCES
Related Threat Intelligence
View Archive
ARTEX AI Agents: How to Detect & Counter Autonomous Attacks
FBI issues FLASH advisory warning that cybercriminals abuse ARTEX AI agents to achieve domain compromise in under 3 hours. Hunt rapid automated lateral moves.

AI Infostealer Market: How to Detect & Block Replay Attacks
Dark web shops deploy AI to parse infostealer logs into searchable corporate dossiers, targeting enterprise VPNs and AI tokens. Hunt token replay attacks.

CVE-2026-99288: How to Mitigate NoisyTCP Remote Linux Crash
An 11-year-old Linux kernel flaw (CVE-2026-99288) dubbed NoisyTCP triggers remote kernel panics via TCP ehash race conditions. Apply patches and disable RPS.