AI Sec Watch: A Security Intelligence Platform for AI Systems

Luu, T.J.

GitHub already has an EDR. You just have to listen to it

infonews

securityresearch

Source: CSO OnlineAugust 11, 2026

Summary

Researchers at Black Hat USA 2026 presented findings showing that many supply-chain attacks (attacks targeting software dependencies used by many projects) could have been detected earlier using GitHub's built-in event data rather than waiting for external security tools. They identified recurring attack patterns like forged commit identities (fake author information in code changes), poisoned tags (malicious release versions), and workflow abuse, then created an open-source tool called GitHub Threat Detector with 22 production detection rules to catch these suspicious behaviors by correlating GitHub webhooks (notifications of repository events), API data, and Git repository inspection.

Solution / Mitigation

The source explicitly presents GitHub Threat Detector as the mitigation tool. According to the researchers' approach: (1) Track mismatches between commit author and authenticated pusher in Git metadata; (2) Search GitHub for reused forged identities across repositories; (3) Monitor tag history through the GitHub API and compare old and new commit references to detect mass tag poisoning (moving release tags to malicious commits); (4) Watch for new or modified workflows that enable OIDC (OpenID Connect, a system for generating short-lived identity credentials) token issuance. The tool collects GitHub webhooks, API events, commits, tags, and Actions activity, enriches this data with Git inspection context, and uses a PostgreSQL database to correlate events over time to convert weak individual signals into high-confidence alerts.