GitHub Dependabot Alerts or Security Updates Disabled
Description
Detects when Dependabot alerts or security updates are disabled at the repository, organization, or enterprise level in GitHub. Adversaries may turn off Dependabot to reduce the chance that a malicious or vulnerable dependency they introduced is flagged; disabling it for an organization or enterprise removes this coverage across many repositories at once.
Query · esql
from logs-github.audit-* metadata _id, _index, _version
| where
event.module == "github" and data_stream.dataset == "github.audit"
and event.action in (
"repository_vulnerability_alerts.disable",
"repository_security_updates.disable",
"dependabot_alerts.disable",
"dependabot_alerts_new_repos.disable",
"dependabot_security_updates.disable",
"dependabot_security_updates_new_repos.disable",
"business_dependabot_alerts.disable",
"business_dependabot_alerts_new_repos.disable"
)
| keep
_id,
_index,
_version,
@timestamp,
event.action,
user.name,
github.org,
github.repo,
github.actor_ip,
github.hashed_token,
github.programmatic_access_type,
github.user_agent
Investigation fields
Pivot points the source recommends for triage.
@timestampevent.actionuser.namegithub.orggithub.repogithub.actor_ipgithub.hashed_tokengithub.programmatic_access_typegithub.user_agent
Known false positives
- Repository admins disabling Dependabot on archival, template, or non-code repos. Confirm the change was intended and that production application repos remain covered.
Analyst notes
Investigating GitHub Dependabot Alerts or Security Updates Disabled
Disabling Dependabot removes automated visibility into vulnerable and malicious packages. This can precede a supply-chain commit or lockfile change. Repository-level actions affect a single repo, while dependabot_* (organization) and business_dependabot_* (enterprise) actions remove coverage across many repositories at once.
Possible investigation steps
- Identify
user.name,github.org,github.repo,event.action, andgithub.programmatic_access_type, and note whether the action is repository-, organization-, or enterprise-scoped. - Review commits and dependency manifest changes around the disable timestamp.
- Check whether Secret Scanning, code scanning, or the org security configuration were also changed.
- Re-enable Dependabot unless there is an approved exception.
False positive analysis
- Bulk disable on forks, mirrors, or documentation-only repositories.
- Org-policy automation that detaches a security configuration.
Response and remediation
- Re-enable Dependabot alerts (and security updates if required by policy).
- Audit recently added dependencies and workflow files.
- Rotate credentials if the actor is not a known admin.