GTG-1002 shows how AI can scale intrusions fast. Here’s why static OAuth trust is risky for SaaS and how to verify apps and tokens nonstop.
Come along with me on a journey as we delve into the swirling, echoing madness of identity attacks. Today, I present a case study on how different implementations of OAuth 2.0, the core authentication ...
Token theft is a leading cause of SaaS breaches. Discover why OAuth and API tokens are often overlooked and how security teams can strengthen token hygiene to prevent attacks. Most companies in 2025 ...
Abstract: The OAuth 2.0 protocol is a widely adopted standard for online authorization. Given its widespread use, it has received substantial attention from the research community towards assessing ...
The August 2025 Salesloft Drift breach demonstrates a systemic security blind spot across all industries: third-party delegated access through OAuth integrations. Over 700 organizations — including ...
The New York Liberty’s bid to repeat as WNBA champions ended Friday night in a 79-73 loss to the Phoenix Mercury in Game 3 of their playoff series. It wasn’t for a lack of effort from Breanna Stewart, ...
An as-of-yet undiagnosed compromise of the Salesloft Drift AI-driven platform has led to a rash of stolen OAuth tokens, in turn creating downstream breaches at some of the biggest names in the ...
Google Threat Intelligence Group (GTIG) warns that attackers are stealing OAuth tokens via Salesloft Drift integrations in a massive Salesforce data theft. Alphabet’s GTIG and Mandiant attributed the ...
Hackers accessed customer contact information and case data from Salesforce instances at Cloudflare, Palo Alto Networks, and Zscaler. Cybersecurity firms Cloudflare, Palo Alto Networks, and Zscaler on ...
Google is advising users of the Salesloft Drift AI chat agent to consider all security tokens connected to the platform compromised following the discovery that unknown attackers used some of the ...
I have an open-id connect provider (id-austria) that replies to a token-request with an invalid token (only 2 parts, not 3). spring-security then tries to get the id-token from the user-info-uri. But ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results
Feedback