ReleaseLock learn

Do secrets leak into GitHub Actions logs? What the new workflow-log secret scanning catches, what it misses, and why wfx-loot deletes logs

By Cassie Crossley · Published November 16, 2026 · Sources checked November 16, 2026 (PT)

Yes, secrets can end up in Actions logs. On November 9, 2026, GitHub put secret scanning for workflow logs into public preview. It scans completed runs for known provider patterns and keeps an alert even after the log is deleted. It also has hard limits: only some enterprises can use it, it is off by default, it does not look at old logs, and it sends no notifications. The wfx-loot campaign deleted runs and logs after its payload ran, so a gap in run numbers is often the trace that remains.

What the November 9 preview does

According to GitHub's changelog, secret scanning now detects secrets in GitHub Actions workflow logs, in addition to issues, wikis, discussions and pull requests. The feature is in public preview.

The changelog does not say how soon after a run completes the scan happens, so this page does not claim that a run deleted within a minute would be scanned first.

What it misses

These are the limits GitHub lists for the preview. Treat them as a checklist of cases it will not cover:

So an alert can survive a deleted log only if the feature was already on, the run finished after that, and the leaked value matched a supported provider pattern.

Why wfx-loot deletes logs, and what still remains

Researchers describe the same cleanup in the wfx-loot campaign, which they date from about November 10, 2026. This page covers only the log side. For how to spot the campaign and rotate tokens, see our wfx-loot guide.

Aikido and GitGuardian also say the stealer was set up to send data by HTTP and, later, Telegram, with the options that write data into the run log turned off. Scanning logs would therefore not be where the stolen secrets show up. The logs matter here as a record of what ran.

Log deletion still helps an attacker against teams whose only record is the Actions tab, or who rely on notifications. It also helps against organizations that are not eligible for the preview or have not enabled it. The preview and the campaign arrived in the same week. This page does not claim GitHub built the feature because of wfx-loot.

A short checklist for maintainers

Where release integrity fits

Log scanning looks for leaked secrets. It does not tell you whether a published release was changed. Stolen publishing tokens remain a risk to releases. The wfx-loot guide states that none of the researchers it cites reports a confirmed GitHub release-asset swap, and nothing on this page changes that. Locking Actions shows which code ran, not what it printed, as explained in the workflow lockfiles guide. To see whether the tools you install have locked releases, search the ReleaseLock directory, and read Can this GitHub release be swapped? for what each lock level means.

Quick answers

Does GitHub secret scanning for workflow logs scan my old logs?

No. GitHub says only workflow runs that complete after you enable the feature are scanned, and existing logs are not backfilled.

Will I get an email when it finds a secret in a log?

No. GitHub says alerts from Actions workflow logs do not generate notifications during the preview, so check the repository's secret scanning alert list directly.

Who can use workflow log secret scanning?

The public preview is available to enterprises on GitHub Enterprise Cloud with GitHub Secret Protection or GitHub Advanced Security, including data residency on GHE.com. It is disabled by default, and an enterprise owner enables it in the enterprise Advanced Security policy.

What does it not detect?

GitHub says generic patterns, custom patterns, AI-detected secrets, and secrets already masked by Actions are not detected in this preview.

If a log is missing, does that mean nothing leaked?

No. In the wfx-loot campaign researchers say the actor deleted workflow runs and logs after the payload ran, and a missing run number is often the remaining trace. GitGuardian notes that a gap proves a run was created but not that it executed, so treat a gap as a reason to investigate.

Sources