Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

bREACHYing the Perimeter: How One HTTP Request can Hijack your AI Robot

Software supply chain attacks are on the rise, and naturally taking the headlines. But with the rise of localized models and common software embedded into smart “things”, risks may even be hidden in plain sight – or, in some cases, quite literally watching you. Vulnerabilities and malicious packages may extend risks to the unlikeliest of places, demanding change and accountability in even some well-intended innovations.

17 Endpoints, Zero Logins Required: Broken Access Control in AI-Built Apps

We handed four vibe-coding tools (Emergent, Replit, Lovable, Base44) the same prompt for a FastAPI user-management microservice. The spec was explicit: JWT auth, parameterized queries, rate limiting, four-tier role model with per-endpoint scope. Each tool shipped a build, and our flagship autonomous pentest surfaced 137 confirmed vulnerabilities across all four.

Vibe Coding Security Checklist: Stress-Test Your AI-Built App in 10 Minutes

You shipped an app in a weekend. The AI wrote the login, the dashboard, and the database layer, and everything works, but it’s far from safe. With 0 logins, an attacker can forge admin invitations, alter audit logs, and change other users’ passwords. The guy is just swimming freestyle through your entire app stack. This is just one of the 137 vulnerabilities we found in vibe-coding across the top 4 platforms.

Warning: Phishing Operations Are Impersonating Prediction Markets

Fraudsters are exploiting the increased public interest in prediction markets such as PolyMarket and Kalshi, according to researchers at Recorded Future. Criminal groups known as “traffers” are providing fellow crooks with “websites, administrative panels, cryptocurrency payment infrastructure, victim-management capabilities, technical support, and promotional guidance” to target users of prediction markets.

CrowdStrike Secures AI Agents Inside Claude Cowork

When Claude Cowork executes code locally, it runs inside an isolated virtual machine on the user's computer. On the host, that VM runs as a single opaque process: The agent's activity inside the VM, including the processes it spawns, the packages it installs, and the network connections it makes, is not visible to the host's endpoint security sensor. Because host folders can be mounted into the VM, sensitive data can sit within the agent's reach.

Introducing AI Kill Switch: Taking Control When AI Agents Go Rogue

As organizations deploy increasingly autonomous and interconnected agents, the potential agentic blast radius grows. A single compromised or misaligned agent can trigger a chain of actions spanning credentials, applications, files, and enterprise systems that create consequences extending far beyond its original task. Traditional security approaches weren't designed to understand these behaviors, much less intervene at the speed agents operate. Security teams need more than alerts and investigations.

Security Integrations Break in Boring Ways: A Practical Look at Connector Development

Almost any enterprise SOC looks the same from the inside. Cloud platform. EDR. Identity provider. A couple of firewalls. A vulnerability scanner nobody fully trusts. And a SIEM that's supposed to hold it all together. Every tool works fine on its own. They just don't talk to each other. So the analyst becomes the glue. Terrible job for a person. Burns them out fast.