GitHub Audit: Secret Scanning Push Protection Bypass Event Detected

Triggers on GitHub audit events indicating a secret scanning push protection bypass attempt.

FreeReviewedSigma · Low · v5

Product: github
Service: audit
Author: Muhammad Faisal (@faisalusuf) (SigmaHQ), DRL 1.1
Published: 2024-03-07
Updated: 2026-07-31

ATT&CK techniques

Recon
Resource Dev
Initial Access
Execution
Persistence
Priv Esc
Defense Evasion
Cred Access
Discovery
Lateral Movement
Collection
C2
Exfiltration
Impact

What it detects

This rule flags GitHub audit events where the action indicates a secret scanning push protection bypass. Attackers could use this to circumvent repository protections for secrets, potentially enabling sensitive data exposure. It relies on GitHub audit log telemetry containing the specific action string for the bypass.

Reporting behind it

Related detections9 linkedT1685 — drag to rearrange

Suspicious Vulnerable Intel Ethernet Driver Load for BYOVD via SCATTERED SPIDER (via driver_load)

Malicious Defender Disable And Executable Exclusion Via Registry

Malicious UAC Disable via EnableLUA Registry Modification (via registry_set)

Malicious AMSI and ETW Patching via PowerShell Script

Malicious PowMix AMSI Bypass via amsiInitFailed

Suspicious ThrottleStop Driver Abuse for Defense Evasion in Ransomware Attacks

Malicious Disabling of Microsoft Defender Real-Time Protection via SystemSettingsAdminFlows by DeadLock Ransomware

Suspicious Security Software Uninstallation via WMIC Product Call Uninstall (Chaos Ransomware)

Suspicious Security Product Uninstall via wmic product call uninstall

GitHub Audit: Secret Scanning Push Protection Bypass Event Detected

Pivot detection · T1685 · 9 related

Changelog

v5
Candidate ingested via manual entry.2026-07-31
v4
Candidate ingested via manual entry.2026-07-31
v3
Candidate ingested via manual entry.2026-07-31
v2
Candidate ingested via manual entry.2026-07-31
v1
No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.

github-audit-secret-scanning-push-protection-bypass-activity-detected-02cf536a

title: "GitHub Audit: Secret Scanning Push Protection Bypass Event Detected"
id: 8bea27c9-56b2-45a3-9b07-900db8a627cb
status: test
description: This rule flags GitHub audit events where the action indicates a secret scanning push protection bypass. Attackers could use this to circumvent repository protections for secrets, potentially enabling sensitive data exposure. It relies on GitHub audit log telemetry containing the specific action string for the bypass.
references:
  - https://docs.github.com/en/enterprise-cloud@latest/code-security/secret-scanning/push-protection-for-repositories-and-organizations
  - https://thehackernews.com/2024/03/github-rolls-out-default-secret.html
  - https://github.com/SigmaHQ/sigma/blob/master/rules/application/github/audit/github_push_protection_bypass_detected.yml
author: Muhammad Faisal (@faisalusuf), Huntrule Team
date: 2024-03-07
tags:
  - attack.defense-impairment
  - attack.t1685
logsource:
  product: github
  service: audit
  definition: "Requirements: The audit log streaming feature must be enabled to be able to receive such logs. You can enable following the documentation here: https://docs.github.com/en/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise#setting-up-audit-log-streaming"
detection:
  selection:
    action|contains: secret_scanning_push_protection.bypass
  condition: selection
falsepositives:
  - Allowed administrative activities.
level: low
license: DRL-1.1
related:
  - id: 02cf536a-cf21-4876-8842-4159c8aee3cc
    type: derived

Convert

This rule as a query you can run. Uses no unlock credit.

SplunkSPL