Avatar photo

CovertSwarm

About CovertSwarm

If you release code, hire people, open new premises or change your board more often than you attack yourself, you are not keeping pace with your own risk. CovertSwarm was founded in 2020 on that argument, frustrated that organizations relied on occasional penetration tests, thick reports and long gaps in between.

The Swarm runs realistic attacks across digital, physical, and social environments, then shows how weaknesses chain into paths an attacker could use against the business.

What we write about

  • Continuous offensive security testing: Why occasional testing can’t keep pace with how often your organization changes.
  • Emerging threats: New attack techniques and what they could let an attacker do to your organization.
  • Offensive AI and AI security: Prompt injection, multi-agent risk and how attackers can turn AI and agentic systems against the organizations running them.
  • Red teaming and adversary simulation: Chaining weaknesses into the attack paths a real adversary would follow.
  • Regulatory threat-led testing: CBEST, STAR-FS and threat-led testing, from a team with CREST accreditation for both.
  • Physical security and social engineering: Getting into buildings and past staff, and what that access exposes.
  • Vulnerability research: Flaws in software and systems, and what an attacker could do with each one.

Latest posts

Swarm Intelligence banner with redacted text

php2shell: moving beyond a lab proof of concept to code execution with ASLR enabled

The Swarm developed a working exploit for php2shell (CVE-2026-109618 and CVE-2026-109619). It achieved unauthenticated remote code execution with address space layout randomisation (ASLR) enabled and PHP error display disabled, in our tested AArch64 PHP 8.5.11 environment running Apache with mod_php.

Read the full postphp2shell: moving beyond a lab proof of concept to code execution with ASLR enabled
person under the spotlight

Swarm spotlight on the community: Thomas Cox on hacking, humanity, and the future of cybersecurity.

In this episode of Swarm Spotlight, Jayson E. Street sits down with national security and cybersecurity veteran Thomas Cox for a candid conversation on hacker culture, AI's impact on the industry, and why cyber education needs to start a lot earlier than it does today.

Read the full postSwarm spotlight on the community: Thomas Cox on hacking, humanity, and the future of cybersecurity.
Graham Haythornthwaite joins CovertSwarm as Technical Director

CovertSwarm appoints Graham Haythornthwaite to accelerate its challenge to the offensive security industry

CovertSwarm has appointed Graham Haythornthwaite as Technical Director, effective September 1, 2026. A former CovertSwarm client turned technical leader, Graham joins as the company defines Continuous Offensive Security Testing (COST), a model built to outpace real adversaries rather than test for them.

Read the full postCovertSwarm appoints Graham Haythornthwaite to accelerate its challenge to the offensive security industry
Gartner Hype Cycle XaaS Red teaming as a service

CovertSwarm named in two Gartner® Hype Cycle™ reports in the Red Teaming as a Service category  

CovertSwarm has been named a Sample Vendor for Red Teaming as a Service in the Gartner Hype Cycle for XaaS, 2026, published 7 July 2026. Five weeks earlier, the Gartner Hype Cycle for Security Operations, 2026 named CovertSwarm a Sample Vendor in the same category.

Read the full postCovertSwarm named in two Gartner® Hype Cycle™ reports in the Red Teaming as a Service category  
DORA compliance vs safety

DORA is not GDPR. Stop treating it like it is. 

Most firms are treating DORA like GDPR: get a consultant, document the framework, move on. That worked for data privacy. It won't work for a regulation built around one premise: that financial entities will be attacked, and regulators want proof the system won't collapse when they are. Here's what DORA actually requires, where enforcement stands in 2026, and why compliance and resilience are not the same thing.

Read the full postDORA is not GDPR. Stop treating it like it is.