Security alert: WFX Phantom probe indicates compromised GitHub credentials

Aperta
#18,038 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
20/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
github, github-actions, kotlin
Ambito
mobile, security

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
Kotlin
Stelle
5.7k
Fork
2.1k
Merge medio
1g 22h
PR unite (30g)
135

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nextcloud/android

Tutte le issue di nextcloud/android

Issue simili

Altre issue su Kotlin

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.