Suspicious Salesforce OAuth Refresh Token Use by Klue Battlecards App

PremiumReviewedSigma · Medium · v1
Product
salesforce
Author
HuntRule
Published
2026-09-15
Updated
2026-09-15

ATT&CK techniques

Initial Access → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Execution

  4. Defense Evasion

  5. Cred Access

  6. Discovery

  7. Lateral Movement

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule detects Salesforce API activity authenticated through an OAuth refresh token attributed to the Klue Battlecards connected application, the abused integration in this supply chain attack. The compromised app reused refresh tokens to authenticate as an external application and pull data without interactive login. Refresh token driven access from this connected app should be scrutinized for unauthorized data access.

Related detections9 linkedT1078 — drag to rearrange
Suspicious SonicWall NetExtender VPN Command-Line Authentication with Always-Trust (via process_creation)
Suspicious Self-Hosted GitHub Actions Runner Started As Root via Shell (via process_creation)
Malicious Shai-Hulud Self-Hosted GitHub Runner Registration via Process Creation
Suspicious Login Shell Assigned to Service Account games on Linux
Suspicious SSH Daemon Configuration Change Enabling Root Login
Suspicious Google Workspace OAuth Authorization for Chrome Web Store Scope via Token Audit
Suspicious NTLM Network Logon From Attacker Controlled Workstation Names (via security)
Suspicious dMSA Object Access with Migration AccessMask
Malicious Shai-Hulud npm Worm Marker via SHA1HULUD Process Name (via process_creation)
Suspicious Salesforce OAuth Refresh Token Use by Klue Battlecards App
Pivot detection · T1078 · 9 related

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