Security

Salesforce OAuth Abuse: Microsoft Guidance on ShinyHunters

3 min read

Summary

Microsoft detailed how threat activity associated with ShinyHunters abused trusted OAuth relationships in Salesforce to gain persistent access, exfiltrate CRM data, and evade traditional sign-in detections. The company also announced improved Salesforce telemetry and near-real-time detection in Defender for Cloud Apps, giving security teams better visibility into connected apps, OAuth scopes, and suspicious SaaS activity.

Need help with Security?Talk to an Expert

Introduction

Microsoft has published new guidance on a growing SaaS threat pattern: attackers abusing trusted OAuth connections instead of stealing passwords or deploying malware. For organizations using Salesforce and other integrated SaaS platforms, this matters because malicious activity can look like normal application behavior and bypass traditional authentication alerts.

What Microsoft observed

Between mid-2025 and mid-2026, Microsoft tracked campaigns with tradecraft overlapping with ShinyHunters. The activity targeted Salesforce environments and relied on trusted access paths to query and exfiltrate data at scale.

The three main intrusion paths

  • Vishing-led OAuth consent abuse: Attackers impersonated IT support and convinced users to approve malicious connected apps, sometimes disguised as Salesforce Data Loader tools.
  • SaaS supply chain compromise: Threat actors abused trusted integrations and compromised vendor workflows involving tools such as Salesloft, Gainsight, and later credentials linked to the Klue incident.
  • Misconfigured guest access: Attackers used overly permissive guest-user access and Salesforce Aura/GraphQL requests to retrieve more data than intended.

What’s new from Microsoft

Microsoft said it worked with Salesforce to improve telemetry available through Microsoft Defender for Cloud Apps.

Key enhancements include:

  • Near-real-time visibility into Salesforce security and activity events
  • Connected application attribution to identify which OAuth app performed actions
  • Expanded OAuth permission and scope insights
  • Improved investigation context across identity, session, and API activity
  • Better correlation in Microsoft Defender across identities, apps, and SaaS environments

For customers using Salesforce Shield: Event Monitoring, the updated Salesforce connector now supports the Real-Time Event Monitoring (RTEM) framework to speed detection and investigation.

Impact on IT and security teams

This research reinforces that SaaS risk is no longer limited to user credentials. If an attacker gains access through a trusted OAuth app or a third-party integration, they may inherit legitimate permissions and operate quietly for long periods.

For administrators, the biggest challenge is visibility. Traditional sign-in anomaly detection may miss this type of attack because the access occurs through approved apps, valid tokens, or legitimate integrations.

Admins should review their SaaS governance and monitoring controls now:

  • Audit OAuth-connected applications and remove unused or high-risk apps
  • Validate third-party Salesforce integrations and stored connection secrets
  • Review guest-user permissions and public access configurations
  • Enable Salesforce Event Monitoring where available
  • Use Defender for Cloud Apps to investigate app activity, OAuth scopes, and suspicious API behavior
  • Train users to recognize vishing and fraudulent consent prompts

The key takeaway is clear: trusted SaaS relationships need the same scrutiny as user identities. Stronger OAuth governance and better telemetry are now essential parts of cloud security operations.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

SalesforceOAuthDefender for Cloud AppsSaaS securityShinyHunters

Related Posts

Security

Microsoft Sentinel Named a 2026 SIEM Leader

Microsoft has been named a Leader in the 2026 Gartner Magic Quadrant for SIEM, highlighting the continued momentum behind Microsoft Sentinel. The announcement also underscores Microsoft's push toward integrated, AI-powered security operations through deep Sentinel integration with the new Integrated Security Operations Center in Microsoft Defender.

Security

Microsoft Perception GA: Agentic Security at Ignite

Microsoft has made Microsoft Perception generally available, introducing an agentic security platform that coordinates red, blue, and green team agents through automated playbooks. Announced at Ignite 2026, the update also expands Defender and Sentinel capabilities to help security teams detect, investigate, and remediate AI-speed threats while keeping administrators in control.

Security

Device Code Phishing Risks for AI Coding Agents

Microsoft warns that device code phishing can be used against AI coding agents such as GitHub Copilot CLI, not just user mailboxes or cloud apps. In a controlled lab, a single approved device code sign-in could enable remote session steering, memory poisoning, synced session exposure, and private repository access depending on account permissions and enabled features.

Security

Microsoft 365 Outage Phishing Campaign Targets Users

Microsoft Threat Intelligence reported a high-volume phishing campaign that impersonates Microsoft 365 service-health notifications to trick users into clicking malicious links. The campaign matters because it uses outage-themed urgency and recipient-specific tracking to target multiple industries, increasing the risk of credential theft and follow-on account compromise.

Security

SCKit ScreenConnect Attack: MSPs Must Hunt Now

Microsoft Threat Intelligence confirmed a campaign abusing ConnectWise ScreenConnect to deploy unauthorized remote-access clients and the SCKit worm on MSP-managed endpoints. The activity can also target technician sessions, making this a high-priority incident for defenders because removing a rogue client alone does not eliminate persistence or invalidate exposed sessions.

Security

AI Agent Supply Chain Attacks Target Coding Tools

Microsoft Security researchers detailed two post-training supply chain attack paths that can backdoor coding and terminal agents: dataset poisoning and model poisoning. The findings matter because compromised agents can misuse tools, execute commands, and access sensitive environments even when prompts appear benign, reinforcing the need for stronger controls around training data, model provenance, and tool permissions.