Security alert: WFX Phantom probe indicates compromised GitHub credentials

Aberta
#18,038 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
20/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Estagnada
Stack de tecnologia
github, github-actions, kotlin
Domínio
mobile, security

Direção de pesquisa

Start by reviewing the linked pull request #18015 and the account activity described in this alert. Check for unauthorized commits, workflow changes, and deleted runs across repositories accessible to the account, then follow the linked StepSecurity guidance to assess any credential exposure. Done means the account and any affected credentials have been secured and the investigation's findings are documented.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

I'm Venkat from StepSecurity. We're reaching out about a security concern requiring your attention: the following PR matches the account-access probe used in the WFX Phantom credential-theft campaign.

The PR's documentation change is harmless, but the account activity is the warning sign. In this campaign, attackers use already-compromised GitHub credentials to create these PRs and test their access before attempting to inject credential-stealing code.

If you did not authorize this PR, treat the credentials associated with the account as compromised—even if no malicious follow-up commit is visible. Closing the PR does not revoke the attacker's access, and the absence of malicious code in the current branch does not rule out earlier activity that was reverted.

The probe PR is already closed. We have not verified the current credential-remediation status.

This notice concerns repository/account access; the probe alone does not establish that published releases or CI secrets were compromised.

Please prioritize:

  1. Securing the affected account: review and revoke compromised personal access tokens or OAuth app authorizations, and review active sessions.
  2. Checking other repositories accessible to that account: look for unauthorized commits, workflow changes, and deleted runs. Do not limit the investigation to this PR.
  3. Following the remediation guidance below: if credential-stealing code ran, rotate the credentials it could access and check for persistence.

Our investigation explains the probe, follow-on attacks, indicators, and recovery steps:

StepSecurity: WFX Phantom — The GitHub Actions Secret Stealer That Deletes Its Tracks

Thanks,
Venkat — StepSecurity

Linguagem predominante
Kotlin
Estrelas
5.7k
Forks
2.1k
Merge médio
1d 22h
PRs com merge (30d)
135

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de nextcloud/android

Todas as issues de nextcloud/android

Issues semelhantes

Mais issues de Kotlin

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.