Detecting GitHub Action Compromises and CI Runner Threats
Score: 8/10

Detecting GitHub Action Compromises and CI Runner Threats

TeamPCP and related campaigns are targeting GitHub Actions CI runners using malware like Megalodon and Miasma to harvest credentials and persist within development pipelines.

Executive Summary

In late 2025 and early 2026, threat actors such as TeamPCP ramped up supply chain attacks targeting CI/CD pipelines, specifically exploiting GitHub Actions through compromised components like 'trivy-action'. These campaigns—including Megalodon, Shai-Hulud, and Miasma—focus on the CI runner, which serves as the execution environment where secrets are decrypted and held in memory.

The technical tradecraft involves injecting malicious scripts into GitHub Action entry points to harvest credentials from the Runner.Worker process memory or persistent filesystems on self-hosted runners. These stolen secrets are then exfiltrated via HTTP or secondary GitHub repositories, feeding a 'Developer Credential Economy' that facilitates lateral movement into cloud infrastructure and production environments. Defenders must pivot toward runtime monitoring of ephemeral and self-hosted runners to close the visibility gap in the software supply chain.

Key Details

Threat Name

Trivy Action Compromise

Affects

—

Adversary

TeamPCP

Malware/Tools

Megalodon, Mini Shai-Hulud, Miasma

Report Score

8out of 10
Quality Score
Good
IOC Quality3
TTP Details9
Detection Guidance9
Enterprise Relevance10
Clarity & Structure9
Technical Depth8

Sources