Security alert: WFX Phantom probe indicates compromised GitHub credentials

Ouverte
#18,038 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
20/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
À l'abandon
Stack technique
github, github-actions, kotlin
Domaine
mobile, security

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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

Langage dominant
Kotlin
Étoiles
5.7k
Forks
2.1k
Merge moyen
1 j 22 h
PR mergées (30 j)
135

Préparer son environnement

Ouvrir dans Codespaces

Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de nextcloud/android

Toutes les issues de nextcloud/android

Issues similaires

Plus d'issues Kotlin

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.