Security

StealC and Amadey Threats: Microsoft Disrupts C2

3 min read

Summary

Microsoft detailed how the StealC infostealer and Amadey malware loader fuel credential theft, account takeover, and downstream ransomware attacks. The company also announced a coordinated disruption with Europol and partners to take down more than 200 related command-and-control domains and IPs, giving defenders new insight into how these threats operate and how to respond.

Need help with Security?Talk to an Expert

Introduction

Microsoft has published new research on StealC and Amadey, two malware services that play a major role in today’s infostealer economy. This matters to security teams because these threats often begin on unmanaged or personal devices, then lead to enterprise compromise through stolen credentials, session cookies, and tokens.

What’s new

Microsoft breaks down the StealC and Amadey ecosystem

  • StealC is an infostealer sold as a malware-as-a-service offering.
  • It targets browser credentials, cookies, session tokens, crypto wallets, messaging apps, and email clients.
  • Amadey acts as a malware loader that delivers StealC and other payloads on demand.
  • Microsoft warns that this modular, pay-as-you-go model helps attackers move quickly from initial infection to broader compromise.

Coordinated disruption of attacker infrastructure

On June 24, 2026, Microsoft’s Digital Crimes Unit, working with Europol and industry partners, announced disruption activity against the infrastructure behind StealC and Amadey.

Key results include:

  • Identification of more than 200 malicious domains and IPs
  • Takedowns, suspensions, and blocking of command-and-control servers
  • Use of court orders, domain seizures, registrations, and provider notifications

Microsoft also said it used Copilot-assisted analysis to speed malware investigation, including string decryption, config extraction, and C2 identification.

Why this matters for defenders

Infostealers are especially dangerous because they can turn a consumer-device infection into an enterprise incident. Attackers may steal:

  • VPN credentials
  • SSO tokens
  • Session cookies
  • Cloud and email account access

That can allow threat actors to authenticate with what appears to be valid user activity, sometimes even bypassing MFA through stolen session data. Microsoft notes that organizations often detect the breach only after ransomware deployment, fraud, or large-scale data exfiltration begins.

Common delivery methods to watch

Microsoft highlighted several common delivery paths:

  • SEO poisoning and malvertising for fake software downloads
  • ClickFix social engineering that tricks users into running commands themselves
  • Phishing emails
  • Other malware loaders, including Amadey

Security teams should review protections around identity and unmanaged-device risk:

  • Strengthen credential hygiene and monitor for token theft
  • Enforce conditional access and sign-in risk policies where possible
  • Investigate suspicious use of valid credentials from unusual devices or locations
  • Educate users about fake software downloads, ClickFix lures, and phishing
  • Review Microsoft Defender detections and indicators of compromise from the source guidance

The key takeaway is clear: infostealers are no longer just an endpoint problem. They are an identity and enterprise access problem that requires fast detection and layered defenses.

Need help with Security?

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

Talk to an Expert

Stay updated on Microsoft technologies

StealCAmadeyinfostealerMicrosoft 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.