Skip to content
[ SIGNAL VERIFIED ] INDEPENDENT CYBERCRIME JOURNALISMCLASSIFIED // THE UNDERGROUND HAS A NEWSROOM / RSS
.COM
Latest News
ALL NEWS
Threat Intelligence

WFX Phantom and the GitHub Actions Secret-Stealing Campaign

Researchers traced a fast-moving campaign in which compromised GitHub accounts were used to alter CI workflows and obtain secrets.

Threat Intelligence editorial artwork
PUBLISHED

Researchers traced a fast-moving campaign in which compromised GitHub accounts were used to alter CI workflows and obtain secrets.

How the activity unfolded

StepSecurity reported that attackers used stolen GitHub account access starting November 10, 2026, submitting apparently innocuous pull requests and, where permissions allowed, introducing code that ran in GitHub Actions. Researchers called the secret-stealing payload WFX Phantom.

The researcher described efforts to revert changes quickly and erase workflow traces, complicating the review of ordinary repository history. The publicly reported counts describe probes and suspected compromises; they should not all be treated as confirmed data theft.

Why build pipelines are valuable

Continuous-integration jobs often hold cloud tokens, package-publishing secrets and other automated identities. A compromised build workflow may open doors beyond the code repository itself.

What developers should review

Audit recent repository contributions and workflow modifications, review suspicious or missing action-run history, inspect third-party automation permissions and rotate credentials that could have been exposed. Check associated cloud logs for unexpected use even after changing a token.

Who is responsible?

This is a case of unauthorized use of compromised accounts. The presence of a malicious pull request does not imply that the named repository owner endorsed or knowingly deployed the code. Attribution should be handled carefully.

The lesson

Software-supply-chain defense requires review of machine identities and automation, not merely vulnerability scanning of application dependencies.

Sources and further reading

IPCRIME research and analysis based on the linked primary or attributed sources; no independent incident-response access is claimed.

Editorial note

IPCRIME distinguishes public records and documented findings from allegations, analysis and commentary. Report corrections through our contact page.