Security alert: WFX Phantom probe indicates compromised GitHub credentials

オープン
#18,038 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
20/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
停滞
技術スタック
github, github-actions, kotlin
領域
mobile, security

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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

主要言語
Kotlin
スター
5.7k
フォーク
2.1k
平均マージ
1日 22時間
マージ済み PR(30日)
135

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

nextcloud/android のほかの issue

nextcloud/android の issue をすべて見る

似ている issue

Kotlin の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。