Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

In our recent analysis of AI browser exfiltration risks, we exposed how OpenAI's Atlas and Perplexity's Comet create permanent backdoors to sensitive data through persistent memory, autonomous agents, and cross-platform sync. The challenges with AI native browsers strongly resonated with CISO’s and security leaders we speak with on a daily basis. But the threat extends far beyond Atlas and Comet.

On December 3, 2025, immediately following the public disclosure of the critical, maximum-severity React2Shell vulnerability (CVE-2025-55182), the Cloudforce One Threat Intelligence team began monitoring for early signs of exploitation. Within hours, we observed scanning and active exploitation attempts, including traffic originating from infrastructure associated with Asian-nexus threat groups.

I first met Tines co-founders Eoin Hinchy and Thomas Kinsella more than a decade ago at eBay. Even then, we shared the same frustration: too much important work was slowed down by brittle processes, manual handoffs, and disconnected tools. We all believed technology should help people focus on meaningful work, not slow them down in muckwork. That idea has shaped my career ever since. I started out in security operations, using automation to make my own job easier.

Let’s be honest: if your SOC is drowning in noise, you’re not “doing security.” You’re babysitting tools that cry wolf. And the wolves? They’re doing just fine. Every vendor claims their AI magically cuts false positives. Most don’t. Why?

In November of last year, Aaron Bray made some supply chain security predictions for 2025. Now, as we approach the close of the year, we are going to look at how those predictions turned out. But first let’s start with the high-level statistics and review some of the campaigns we have been tracking and reporting on this year. As this year is not yet over, we have excluded data from December for both 2024 and 2025.

Why outsourcing auth doesn't mean outsourcing risk.

Privilege is no longer a static control. It shifts dynamically with every action taken by an increasingly dynamic set of users, workloads, and AI agents, making traditional reliance on static credentials outdated and unfit for modern, fast-paced hybrid environments. As a result, organizations now need to evolve to a more agile and adaptive approach to securing privilege, one that can effectively handle the sheer volume and complexity of identities operating across cloud, on-prem, and hybrid ecosystems.

Why we’re bringing Zero Standing Privileges to M365, and why it matters. In the past decade, we collectively agreed that standing access to infrastructure is a security failure. No credible security team allows permanent root access on production servers or standing SSH keys for cloud instances. We built vaults, we implemented session recording, and we moved to Just-in-Time (JIT) access for infrastructure.