Security

Fox Tempest Malware Signing Service Disrupted

3 min read

Summary

Microsoft has disrupted Fox Tempest, a malware-signing-as-a-service operation that helped cybercriminals make ransomware and other malware appear legitimately signed. The takedown matters because the group abused Microsoft Artifact Signing, created more than 1,000 fraudulent certificates, and enabled attacks that could bypass security controls more easily.

Need help with Security?Talk to an Expert

Introduction

Microsoft has detailed the disruption of Fox Tempest, a financially motivated threat actor that operated a malware-signing-as-a-service (MSaaS) platform for other cybercriminals. This is significant for security teams because signed malware is more likely to evade defenses, appear trustworthy to users, and succeed in ransomware delivery.

What’s new

Microsoft disrupts Fox Tempest infrastructure

  • In May 2026, Microsoft’s Digital Crimes Unit (DCU), with industry partners, disrupted Fox Tempest’s service and supporting infrastructure.
  • Microsoft also revoked more than 1,000 code-signing certificates linked to the operation.

Abuse of Microsoft Artifact Signing

  • Fox Tempest abused Microsoft Artifact Signing (formerly Azure Trusted Signing) to obtain short-lived certificates valid for 72 hours.
  • These certificates made malware look legitimately signed, helping threat actors bypass some security controls.

Broad cybercrime enablement

  • Microsoft says Fox Tempest enabled the delivery of Rhysida ransomware and malware families including Oyster, Lumma Stealer, and Vidar.
  • The actor has been linked to ransomware activity involving groups such as Vanilla Tempest, Storm-0501, Storm-2561, and Storm-0249.

Evolving delivery model

  • The service initially operated through signspace[.]cloud, where customers uploaded files for signing.
  • In early 2026, Fox Tempest shifted to pre-configured VMs hosted through Cloudzy, streamlining signed malware delivery for customers.

Why it matters for defenders

Fox Tempest did not directly attack victims. Instead, it provided a critical supporting service to ransomware affiliates and malware operators. That makes this case especially important for IT and security administrators: disrupting access to trusted code-signing can reduce the effectiveness of downstream attacks across multiple threat groups.

Organizations in healthcare, education, government, and financial services were among those affected globally. Because signed binaries can appear legitimate, defenders should not treat digital signatures alone as proof that software is safe.

  • Review Microsoft Defender detections and indicators of compromise published with the report.
  • Hunt for suspicious signed binaries, especially those masquerading as common tools such as AnyDesk, Teams, PuTTY, or Webex.
  • Investigate recent malware activity tied to malvertising, SEO poisoning, and fake software downloads.
  • Tighten controls around application execution, including allowlisting and reputation-based protection.
  • Monitor for unusual Azure-related artifacts, suspicious certificate usage, and short-lived signing activity.
  • Educate users to verify software sources and avoid sponsored or poisoned search results.

Bottom line

The Fox Tempest disruption highlights how trusted-signing abuse has become a force multiplier for ransomware operators. Security teams should use Microsoft’s published detections and IOCs to validate exposure, strengthen defenses, and reduce the risk from signed malware.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

Fox Tempestmalware signingransomwareMicrosoft Defenderthreat intelligence

Related Posts

Security

Microsoft Sentinel Named a 2026 SIEM Leader

Microsoft has been named a Leader in the 2026 Gartner Magic Quadrant for SIEM, highlighting the continued momentum behind Microsoft Sentinel. The announcement also underscores Microsoft's push toward integrated, AI-powered security operations through deep Sentinel integration with the new Integrated Security Operations Center in Microsoft Defender.

Security

Microsoft Perception GA: Agentic Security at Ignite

Microsoft has made Microsoft Perception generally available, introducing an agentic security platform that coordinates red, blue, and green team agents through automated playbooks. Announced at Ignite 2026, the update also expands Defender and Sentinel capabilities to help security teams detect, investigate, and remediate AI-speed threats while keeping administrators in control.

Security

Device Code Phishing Risks for AI Coding Agents

Microsoft warns that device code phishing can be used against AI coding agents such as GitHub Copilot CLI, not just user mailboxes or cloud apps. In a controlled lab, a single approved device code sign-in could enable remote session steering, memory poisoning, synced session exposure, and private repository access depending on account permissions and enabled features.

Security

Microsoft 365 Outage Phishing Campaign Targets Users

Microsoft Threat Intelligence reported a high-volume phishing campaign that impersonates Microsoft 365 service-health notifications to trick users into clicking malicious links. The campaign matters because it uses outage-themed urgency and recipient-specific tracking to target multiple industries, increasing the risk of credential theft and follow-on account compromise.

Security

SCKit ScreenConnect Attack: MSPs Must Hunt Now

Microsoft Threat Intelligence confirmed a campaign abusing ConnectWise ScreenConnect to deploy unauthorized remote-access clients and the SCKit worm on MSP-managed endpoints. The activity can also target technician sessions, making this a high-priority incident for defenders because removing a rogue client alone does not eliminate persistence or invalidate exposed sessions.

Security

AI Agent Supply Chain Attacks Target Coding Tools

Microsoft Security researchers detailed two post-training supply chain attack paths that can backdoor coding and terminal agents: dataset poisoning and model poisoning. The findings matter because compromised agents can misuse tools, execute commands, and access sensitive environments even when prompts appear benign, reinforcing the need for stronger controls around training data, model provenance, and tool permissions.