Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

The pitch is familiar enough that most security leaders tune it out. It sounds like marketing language, just an updated way of saying “a better scanner.” This post is here to bust the myth behind that framing. Both scanners and autonomous pentesting agents look the same from the outside. Both crawl your application, both send payloads, and both produce findings. But they operate on completely different assumptions of what constitutes a vulnerability.

Every year, the Verizon Data Breach Investigations Report (DBIR) gives the security industry a chance to step back from the noise and look at what happened. Not what vendors predicted. Not what attackers threatened. Not what defenders feared. What happened. This year’s report makes one point hard to ignore: vulnerability exploitation became attackers’ initial leading access vector.

Under pressure, organizations often prioritize speed over process, unintentionally making the situation worse.

In our previous post, Token Bingo: Don’t Let Your Code Be the Winner, we documented Kali365, a phishing-as-a-service (PhaaS) kit abusing Microsoft’s OAuth 2.0 device authorization flow to steal Entra ID tokens. In this follow-up report, we track the same operator into new territory as they expand their operation and infrastructure.

AI adoption in business has moved at a staggering pace. According to a major survey from The Conversation, 58% of global employees are intentionally using AI at work. That same study revealed an alarming trend: 66% of global employees have used unapproved AI tools, while only 34% say their company has put in place rules to govern AI usage. This use — and potential misuse — of AI systems is the latest and most complex threat facing businesses today.

The terminal output was still scrolling when Jer Crane, the founder of PocketOS, realized what had happened. Nine seconds. That is how long it took a coding AI agent to delete his production database, his backups, and three months of operational records. PocketOS was using Cursor for what should have been a routine task in a test environment.