GitHub Private Repository Turned Public

Last updated a month ago on 2025-12-16

Created 2 years ago on 2023-12-16

About

Detects when a private GitHub repository is changed to public visibility. Adversaries may change repository visibility to public in order to exfiltrate sensitive code or data, potentially indicating a compromise or unauthorized access.

Tags

Domain: CloudUse Case: Threat DetectionTactic: ExfiltrationTactic: ImpactData Source: GithubLanguage: eql

Severity

low

Risk Score

MITRE ATT&CK™

Exfiltration (TA0010)(external, opens in a new tab or window)

↳ Automated Exfiltration (T1020)(external, opens in a new tab or window)

↳ Exfiltration Over Web Service (T1567)(external, opens in a new tab or window)

Impact (TA0040)(external, opens in a new tab or window)

License

Elastic License v2(external, opens in a new tab or window)

Definition

Rule Type: Event Correlation Rule
Integration Pack: Prebuilt Security Detection Rules
Index Patterns: logs-github.audit-*
Related Integrations: github(external, opens in a new tab or window)
Query

✄𐘗text code block:
✄𐘗configuration where event.dataset == "github.audit" and github.operation_type == "modify" and github.category == "repo" and
event.action == "repo.access" and github.previous_visibility == "private" and github.visibility == "public"

Install detection rules in Elastic Security

Detect GitHub Private Repository Turned Public in the Elastic Security detection engine by installing this rule into your Elastic Stack.

To setup this rule, check out the installation guide for Prebuilt Security Detection Rules(external, opens in a new tab or window).