1. Resources
  2. Detection rules
  3. Enterprise Owner or Billing Manager Invited in GitHub

Enterprise Owner or Billing Manager Invited in GitHub detection rules

An attacker who controls an enterprise owner invites an outside account to become enterprise owner or billing manager, a pending way back in that turns into control of the whole enterprise once the invitation is accepted.

Platform
GitHub
Severity
High
Log source
GitHub audit log
Last updated
Rule formats
Sigmaand queries for: SplunkMicrosoft SentinelIBM QRadar
What an attacker needs
Control of an enterprise owner account in an enterprise with personal accounts, where owners invite the other administrators.
Impact
Complete control of the enterprise and, by joining any organization, of the code and secrets held there, once the invitation is accepted.
Response
Cancel the pending invitation or remove the account from the enterprise, and secure the owner account that sent the invitation.
Mitigation
Keep enterprise owners few and on phishing-resistant two-factor authentication, and review pending administrator invitations regularly.
Audit actions
business.invite_billing_managerbusiness.add_billing_managerbusiness.invite_admin

How the attack works

A GitHub enterprise account has its own administrators. Enterprise owners have complete control over the enterprise: they manage the administrators, add and remove organizations, enforce policies across every organization and manage security and billing settings. They have no access to an organization's settings or content by default, but they can gain it by joining any organization. Billing managers reach only the billing settings. In an enterprise with personal accounts, an owner invites a new administrator by username, full name or email address and chooses the role. The invited person has to accept the emailed invitation, and a pending invitation expires after 7 days.

After taking over an enterprise owner, an attacker invites an account they control. The invited account does not have to belong to the company, and nothing happens in any organization until the invitation is accepted, which makes the invitation easy to miss. GitHub records it at once, as business.invite_admin for an owner and business.invite_billing_manager for a billing manager. Acceptance appears later as business.add_admin, which the page on organization and enterprise owners being added covers, or as business.add_billing_manager.

What an attacker needs

  • Control of an enterprise owner account. GitHub gives the right to invite enterprise administrators to enterprise owners.
  • An enterprise with personal accounts. With Enterprise Managed Users, owners and billing managers can be added only through the identity provider.

Impact

As enterprise owner, complete control of the enterprise: its administrators, its policies for every organization, its security settings and, by joining any organization, the code and secrets held there. A billing manager is limited to billing settings, but is still an outside account with a standing role in the enterprise. The invited account survives the recovery of the owner account that sent the invitation.

Detection rules

GitHub Enterprise Billing Manager Invited or Added

Detects an invitation for someone to become a billing manager of a GitHub enterprise account, and a billing manager being added. Billing managers reach only the billing settings of the enterprise, so this is a low-level signal. It is kept because the role can be given to an account from outside the company, which then has a standing role in the enterprise.

LevelLowStatusExperimentalLog sourceGitHub audit log
title: GitHub Enterprise Billing Manager Invited or Added
id: aeb17013-98df-4e69-b906-5d040e0707e5
status: experimental
description: >-
  Detects an invitation for someone to become a billing manager of a GitHub
  enterprise account, and a billing manager being added. Billing managers
  reach only the billing settings of the enterprise, so this is a low-level
  signal. It is kept because the role can be given to an account from outside
  the company, which then has a standing role in the enterprise.
references:
  - https://docs.github.com/en/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise
  - https://docs.github.com/en/enterprise-cloud@latest/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise
  - https://docs.github.com/en/enterprise-cloud@latest/admin/managing-accounts-and-repositories/managing-roles-in-your-enterprise/abilities-of-roles
  - https://attack.mitre.org/techniques/T1098/003/
author: Forestall
date: 2026-11-16
tags:
  - attack.persistence
  - attack.privilege-escalation
  - attack.t1098.003
logsource:
  product: github
  service: audit
detection:
  selection:
    action:
      - business.invite_billing_manager
      - business.add_billing_manager
  condition: selection
falsepositives:
  - Finance or procurement staff who are given the billing manager role as part of their work. Confirm that the account belongs to the person it is meant for.
level: low

False positives

  • Finance or procurement staff who are given the billing manager role as part of their work. Confirm that the account belongs to the person it is meant for.

GitHub Enterprise Owner Invited

Detects an invitation for someone to become an owner of a GitHub enterprise account. An enterprise owner controls the administrators, policies and security settings of the enterprise and can join any of its organizations. The invitation is pending until the invited person accepts it and expires after 7 days, so an invitation nobody can explain can still be cancelled. The accepted invitation is a different event (business.add_admin).

LevelMediumStatusExperimentalLog sourceGitHub audit log
title: GitHub Enterprise Owner Invited
id: b02e3154-0148-4ad2-b0c5-dd7336fae1fc
status: experimental
description: >-
  Detects an invitation for someone to become an owner of a GitHub enterprise
  account. An enterprise owner controls the administrators, policies and
  security settings of the enterprise and can join any of its organizations.
  The invitation is pending until the invited person accepts it and expires
  after 7 days, so an invitation nobody can explain can still be cancelled.
  The accepted invitation is a different event (business.add_admin).
references:
  - https://docs.github.com/en/enterprise-cloud@latest/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise
  - https://docs.github.com/en/enterprise-cloud@latest/admin/managing-accounts-and-repositories/managing-users-in-your-enterprise/inviting-people-to-manage-your-enterprise
  - https://docs.github.com/en/enterprise-cloud@latest/admin/managing-accounts-and-repositories/managing-roles-in-your-enterprise/abilities-of-roles
  - https://attack.mitre.org/techniques/T1098/003/
author: Forestall
date: 2026-11-16
tags:
  - attack.persistence
  - attack.privilege-escalation
  - attack.t1098.003
logsource:
  product: github
  service: audit
detection:
  selection:
    action: business.invite_admin
  condition: selection
falsepositives:
  - Planned changes to the enterprise's administrators. Enterprise owner invitations are rare, so confirm each one with the enterprise's security contact and check who was invited.
level: medium

False positives

  • Planned changes to the enterprise's administrators. Enterprise owner invitations are rare, so confirm each one with the enterprise's security contact and check who was invited.

Triage

  • Identify the owner who sent the invitation (actor) and the enterprise, and confirm it with the owner through a separate channel.
  • Find out who was invited. The documented fields of the event include the invitation ID and an email address, and the enterprise's People settings list every pending administrator invitation.
  • Check the invited account. A new account, an account outside the company's organizations or a personal email address needs an explanation.
  • Review what else the inviting owner did around that time, such as changes to single sign-on, policies, audit log streaming or other administrators.
  • If the invitation is not explained, cancel it before it is accepted.

Response

Once the attack is confirmed:

  1. Cancel the pending invitation. If it was already accepted, remove the account from the enterprise, which removes the administrative role and all its organization memberships.
  2. Secure the owner account that sent the invitation. Reset its password and second factor, end its sessions and revoke its personal access tokens and SSH keys.
  3. Compare the full list of enterprise owners and billing managers, and the pending invitations, with the list you expect. An attacker who sent one invitation may have sent several.
  4. If the invited account acted as an owner, review and reverse what it did, such as organizations it joined, policies it changed, single sign-on and audit log streaming settings and administrators it added or removed.
  5. Rotate the Actions secrets of the organizations the account joined, and the cloud credentials they unlock, because organization owners manage those secrets.

Mitigation

  • Keep the number of enterprise owners small and require phishing-resistant two-factor authentication for them.
  • Use Enterprise Managed Users where possible, so that enterprise administrators can be added only through the identity provider.
  • Review the administrators and the pending administrator invitations of the enterprise regularly.
  • Stream the enterprise audit log to your SIEM and alert on every enterprise owner invitation.

Frequently asked questions

Why alert on the invitation and not on the new owner?

Because the invitation is the earliest point at which the attack can be stopped. The invited person has to accept the emailed invitation before they can access the enterprise account, and a pending invitation can be cancelled. Until then nothing has changed in any organization. The accepted invitation is a separate event, `business.add_admin`, which the page on owners being added covers.

Do these rules cover an owner being invited to an organization?

No. GitHub's event reference lists no role or permission field for `org.invite_member`, so an invited organization owner cannot be told from an invited member at that point. The role becomes visible when the invitation is accepted, as `org.add_member` with the permission `admin`. The enterprise events are different, because the action name itself states the role.

Why is the billing manager rule only at level low?

Billing managers have access only to the enterprise's billing settings, and GitHub states that they do not have access to organization settings or content by default. It is a role for people who handle licences and invoices. The rule exists because a billing manager is still an outside account with a standing role, so each one should be known.

Can this happen in an enterprise with managed users?

Not through an invitation. With Enterprise Managed Users, enterprise owners and billing managers can be added or removed only through the identity provider. The equivalent attack there is a change in the identity provider that puts an account into the group or role mapped to enterprise owners, and it has to be watched in the identity provider's own logs.

References

We respect your privacy

We use cookies to keep this site secure and working properly. With your permission, we also use optional cookies to understand usage and improve the experience. Cookie Policy

You can change your choice at any time.