Malicious GitHub Repository Creation With s1ngularity Exfiltration Name

PremiumReviewedSigma · High · v1
Product
github
Service
audit
Author
HuntRule
Published
2026-07-18
Updated
2026-08-28

ATT&CK techniques

Exfiltration
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Impact

What it detects

This rule detects a GitHub audit repo create event where the repository name contains s1ngularity, the naming convention of the exfiltration repositories used to publish stolen secrets. It matters because these attacker created repositories are the exfiltration destination in the nx supply chain attack.

Related detections9 linkedT1567 — drag to rearrange
Suspicious Credential Exfiltration to webhook.site (via dns_query)
Suspicious HTTP POST to Local AI Malware Exfil Endpoint (via proxy)
Malicious Mini Shai-Hulud TanStack C2 git-tanstack and getsession (via dns_query)
Suspicious Data Exfiltration to Webhook.site via Command Line (via process_creation)
Suspicious SNS Email Subscription for Data Exfiltration
Suspicious Azure OpenAI Training File Upload via Files Import Operation (via azure)
Malicious TeamPCP LiteLLM Credential Exfiltration C2 Lookup (via dns_query)
Malicious Shai-Hulud Data Exfiltration Script Execution via Process Creation
Malicious TeamPCP Trivy C2 Beacon to ICP Canister and Cloudflare Tunnel (via dns_query)
Malicious GitHub Repository Creation With s1ngularity Exfiltration Name
Pivot detection · T1567 · 9 related

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