Security researchers say hijacked developer accounts were used to probe tens of thousands of repositories and inject secret-stealing workflow changes.
What was observed
StepSecurity and other researchers reported a campaign starting November 10, 2026, involving compromised GitHub accounts, routine-looking pull requests and, in some cases, changes designed to collect CI/CD secrets. The campaign has been described as WFX Phantom or wfx-loot.
Public research identified probes against tens of thousands of repositories. A probe is not necessarily a completed compromise; evidence of code execution and credential exposure requires separate assessment.
Why pipeline access is a valuable prize
Build environments may hold deployment keys, tokens for package registries and cloud account credentials. An attacker who reaches the automation layer may be able to extend an intrusion well beyond one source-code repository.
What maintainers should review
Examine unexpected workflow edits and automation changes since November 10, recent token activity and missing or deleted job runs. Revoke credentials that were plausibly exposed and look for corresponding access in cloud account logs.
The human element
Developers trust colleagues and established repository workflows. When an account itself has been stolen, ordinary trust signals become less reliable. Strong account authentication and tightly scoped tokens help reduce the damage.
Further IPCRIME analysis
Our Threat Intelligence section includes a separate explanation of the reported attack chain and its defensive implications.
Sources
IPCRIME news report prepared November 14, 2026. Facts are attributed to the named companies, public records and published reporting. Corrections can be submitted through our contact page.