Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

When a new vulnerability is announced, the race begins. Security teams jump into action, checking exposure, triaging events, identifying affected systems, and figuring out how quickly they can patch. The clock is ticking and they know it. At the same moment, threat actors are doing their own version of that work. They’re reading the same advisories, watching the same feeds, and asking a much simpler question: Who is still vulnerable?

No man is an island, entire of itself; Every man is a piece of the continent, a part of the main.– John Donne Let’s face it, we have a gap in our cyber posture. Thirty percent of breaches originate from third parties, yet as organizations become increasingly exposed to supply chain attacks, they often lack the visibility, context, and workflows to detect and respond to them. Why?

Something fundamentally shifted in cybersecurity. Claude Mythos, Anthropic’s frontier AI model, signaled the arrival of what the Cloud Security Alliance called an “AI vulnerability storm,” a world where vulnerabilities are discovered and exploited at machine speed. This is a compression event, collapsing timelines, expanding attack surfaces, and forcing a rewrite of how organizations think about security operations, software development, risk, and ultimately, business survival.

Residential proxy services, also called RESIP, present a persistent operational hurdle for tracking and attributing malicious network activity, as they allow threat actors to mask their true origins behind seemingly benign, geographically diverse IP addresses. While often marketed for legitimate use cases, these networks are aggressively leveraged for fraud, credential abuse, and perimeter evasion.

I’ve spent a lot of time recently thinking about what "innovation" actually means in an industry that moves as fast as cybersecurity. It’s a term that gets thrown around a lot, but as a product leader at Bitsight, I see it as something much deeper than just shipping new features. It's about a fundamental shift in how we help organizations stay resilient.

A recent open letter from the UK government on AI-driven cyber threats highlights a clear shift in the threat landscape. Cyberattacks are no longer constrained in the same way by human expertise, as advanced AI models can now help identify vulnerabilities, generate exploit code, and increase the speed and scale of attacks.

A critical vulnerability CVE-2026-41940 has been identified in cPanel, WHM, and WP Squared, affecting cPanel & WHM versions after 11.40, as well as WP Squared. These web hosting control panels are commonly used to manage websites, email, databases, and server configurations, making unauthorized access a serious security concern.

Picture the first meeting after a serious security event. The Security Operations team is talking about alerts, detections, and lateral movement. Threat Intelligence is talking about adversary tradecraft and known campaigns. Governance and Risk is talking about control gaps, exposure, and business risk. And leadership? They only care about how bad this event is, and what the team is doing about it. Security teams often agree on the mission: deter and stop threat actors at all costs.

The rise of AI-driven vulnerability discovery using Anthropic's Claude Mythos, as well as similar tools from Google and OpenAI, is completely changing the calculus of cyber risk. The number of vulnerabilities is exploding. The time it takes for exploits to appear is shrinking. The patching cadences and scan intervals, assessments and risk registers that many organizations still rely on are rapidly becoming ineffective.

A few weeks ago we published the first part of this series where we described the infrastructure used by the RondoDox threat actors to scan and exploit vulnerable systems. In this second post we’ll take a deep dive into the malware that is deployed into vulnerable systems. Specifically, we’ll look at the initial implant used to fetch the RondoDox binary and the binary itself, detailing its behaviour, how it communicates with the Command and Control (C2), and its malicious capabilities.