ThreatBeaconXSubscribe
HighThreat Intelligence · 18 min read

Australia Disrupts Amadey Malware Controller as Operation Endgame Targets Amadey and StealC

Australia's signals-intelligence and cybersecurity agency, the Australian Signals Directorate (ASD), has reportedly gained access to an Amadey malware operator's backend infrastructure and disconnected the controller from approximately 180,000 infected computers worldwide, including computers in Australia. The action, reported by The Hacker News on October 27, 2026, disrupted the operator's ability to communicate with those infected systems through the affected controller. The Australian action follows the international Operation Endgame disruption effort conducted from June 15 to June 19, 2026. That operation targeted infrastructure associated with Amadey, StealC, and SocGholish. ESET Research supported the effort by supplying technical malware analysis, command-and-control (C2) server information, encryption keys, campaign and build identifiers, and statistical intelligence collected through long-term monitoring. Amadey is a modular malware loader that can download additional malicious software, collect credentials, monitor clipboard activity, and provide remote access. StealC is an information stealer that targets browser credentials, session cookies, cryptocurrency wallets, browser extensions, and files selected by its operators. Both are distributed through malware-as-a-service (MaaS) models, allowing different criminal affiliates to operate their own infrastructure and campaigns. ESET's analysis identified 53 distinct Amadey clusters and 73 StealC clusters. This fragmented infrastructure presents a challenge for disruption because individual affiliates can operate separate C2 servers and generate different malware builds. ESET reported that Operation Endgame affected approximately 50 domains and nearly 200 active IP-based C2 servers associated with Amadey and StealC. The two operations demonstrate the value of combining government cyber capabilities, law-enforcement coordination, private-sector intelligence, and long-term malware tracking. However, disconnecting a controller does not remove malware from infected devices, reverse earlier data theft, or eliminate independently operated botnets.

Written by VEDANABHATLA SAI SWETHA·Published Oct 29, 2026

1. Description

The disruption of Amadey and StealC highlights the continuing threat posed by malware services that support credential theft, unauthorized remote access, and the delivery of additional malicious software.

Amadey has been offered to cybercriminals since 2018. It primarily functions as a loader, allowing affiliates to distribute additional payloads to compromised systems. Its capabilities also include credential theft, clipboard monitoring, and remote access through VNC-related functionality. An Amadey infection can therefore become an entry point for additional malware and subsequent compromise.

StealC, introduced on a darknet forum in February 2023, specializes in information theft. It can collect credentials from browsers, email and FTP clients, gaming platforms, cryptocurrency wallets, and browser extensions. Its configurable file-grabber feature also allows affiliates to specify patterns for files they want to collect.

The two malware families operate as services, but their affiliates are responsible for deploying their own administration panels and infrastructure. This makes the ecosystem more fragmented than a centrally managed service and complicates attempts to disable every operator simultaneously.

During Operation Endgame, ESET supplied technical intelligence to help identify and cluster the infrastructure used by Amadey and StealC affiliates. In a separate development reported on October 27, 2026, Australia's ASD disclosed that it had accessed an Amadey operator's backend and disconnected its controller from approximately 180,000 infected computers.

These actions interrupt criminal operations at the infrastructure level. Organizations must nevertheless investigate potentially infected endpoints and exposed accounts because stolen credentials and session cookies can remain useful long after the original malware connection has been disrupted.

2. Technical Description

2.1 Amadey malware

Amadey is a modular malware loader advertised on darknet forums under the account name InCrease, according to ESET. It has been actively maintained since 2018.

Its primary purpose is to deliver additional malware to compromised computers. Depending on the sample and its configuration, it can also provide:

  • Credential-stealing functionality.

  • Clipboard monitoring.

  • VNC-based remote access.

  • Additional payload downloads and execution.

  • System-information collection.

  • Communication with an affiliate-controlled C2 server.

Amadey has evolved over time. ESET highlighted version 1.99.5 in August 2020 as a major codebase rewrite. Version 5.03, released in October 2024, introduced additional capabilities, including reverse-connect hVNC, silent MSI installation support, RDP enabling, command execution with SYSTEM privileges, and encrypted-payload support.

The malware's continued development and repeated adjustments to avoid antivirus detection demonstrate why defenders should not depend exclusively on signatures for older samples.

2.2 StealC information stealer

StealC is an information-stealing MaaS offering advertised by an operator using the moniker plymouth.

Its targets include:

  • Browser-stored passwords and autofill information.

  • Browser cookies and session data.

  • Email-client and FTP-client credentials.

  • Gaming-platform data.

  • Cryptocurrency-wallet files and browser extensions.

  • Files matching operator-defined patterns.

  • Other information specified in the malware's configuration.

StealC's configurable file grabber allows affiliates to define which local files should be collected. Its C2 configuration can also control whether the malware captures a screenshot, downloads an additional payload, or self-destructs after completing its tasks.

ESET reported that StealC version 2, introduced in March 2025, brought major changes to the network protocol and configuration structure. Version 2.22.1 was observed by June 2026.

2.3 Malware-as-a-Service operating model

Both families are distributed through MaaS models, but the business arrangements differ.

Amadey

ESET reported that a single license cost approximately US$600 in Bitcoin, with an additional US$50 charged for each rebuild. Affiliates could request a new compiled sample when they needed to rotate their C2 infrastructure. They were not given a general-purpose build tool in the model described by ESET.

StealC

StealC offered subscription pricing of approximately US$300 per month, US$700 for three months, or US$1,000 for six months. Its subscription included unlimited build generation, making it easier for affiliates to generate samples and rotate infrastructure.

In both cases, affiliates operated their own administration panels and servers. This model gave them direct control over payload distribution and victim data, but it also created many separate infrastructure clusters that had to be identified individually.

2.4 Infection vectors

ESET telemetry identified several common delivery methods for both malware families:

  • Fake software-update prompts.

  • Cracked-software installers.

  • Third-party malware loaders.

  • Trojanized software packages and installers.

  • Additional payloads distributed through established malware infrastructure.

The delivery method varies by affiliate. A detection or disruption affecting one distribution campaign therefore does not necessarily prevent other affiliates from infecting new victims.

3. Attack Overview

3.1 Timeline of key developments

DateEvent
October 2018Amadey was advertised on darknet forums, according to ESET.
February 2023StealC was introduced on a darknet forum.
March 2025StealC version 2 introduced major protocol and configuration changes.
Q4 2025–H1 2026ESET collected and analyzed malware statistics and technical intelligence later shared for the disruption effort.
May 2026Microsoft reported that Amadey and StealC were associated with more than 140,000 infected computers globally during the first two weeks of the month.
June 15–19, 2026Operation Endgame targeted infrastructure associated with Amadey, StealC, and SocGholish.
June 24, 2026ESET published details of its technical contribution to the Amadey and StealC disruption.
October 27, 2026The Hacker News reported that Australia's ASD had accessed an Amadey operator's backend and disconnected the controller from approximately 180,000 infected computers.

The Australian operation and the June Operation Endgame action should be treated as separate developments. The available reporting does not establish that the Australian controller disruption was part of the June action week.

3.2 General attack lifecycle

The following sequence summarizes how these malware families can operate together in a cybercrime ecosystem. It is not a claim that every infection follows exactly the same sequence.

  1. A victim encounters a malicious installer, fake update, cracked application, or another malware-delivery mechanism.

  2. Amadey executes on the compromised computer.

  3. The loader communicates with its affiliate's C2 server and registers information about the infected system.

  4. The server returns tasks instructing the malware to download or execute additional payloads.

  5. A payload such as StealC may collect browser credentials, session cookies, wallet data, or other files.

  6. Stolen information is transmitted to infrastructure controlled by the relevant criminal affiliate.

  7. Credentials may be sold, reused, or passed to other operators for further unauthorized access.

Not every Amadey infection includes StealC. ESET observed Amadey distributing multiple malware families, including RATs and other infostealers.

3.3 Disruption strategy

The disruption effort addressed the infrastructure that supports malware operations rather than relying solely on detecting individual infections.

The main components were:

  1. Malware analysis: Extracting embedded configuration, encryption keys, identifiers, and communication details from samples.

  2. Infrastructure tracking: Identifying C2 servers, domains, URL paths, and related infrastructure.

  3. Affiliate clustering: Grouping samples according to configuration values and infrastructure relationships.

  4. Intelligence sharing: Providing findings to law enforcement and private-sector partners.

  5. Infrastructure disruption: Targeting the servers used to control infected systems and support malware distribution.

  6. Continued monitoring: Tracking attempts by operators to rebuild infrastructure following the disruption.

4. Technical Analysis

4.1 Australia's Amadey controller disruption

The Hacker News reported on October 27, 2026, that ASD gained access to an Amadey operator's backend and disconnected the controller from approximately 180,000 infected computers.

According to the report, the action prevented that operator from continuing to access or steal data through the affected controller. ASD's offensive cyber operations require explicit Australian government approval and can be used to disrupt criminal infrastructure overseas.

The reported number describes the computers associated with the affected controller. It should not be interpreted as the total global number of Amadey infections or proof that all affected computers were cleaned.

The report does not provide a complete technical description of the controller-access method, a confirmed list of the targeted server addresses, or a malware-removal mechanism deployed to the affected computers.

4.2 Operation Endgame

Operation Endgame is an international law-enforcement and private-sector initiative aimed at disrupting cybercrime infrastructure.

The June 15–19, 2026 action week targeted servers associated with Amadey, StealC, and SocGholish. ESET reported that the operation affected approximately 50 domains and nearly 200 active IP-based C2 servers associated with Amadey and StealC.

ESET's contribution included:

  • Technical analyses of malware samples.

  • Statistical information covering Q4 2025 through H1 2026.

  • Known C2 server addresses.

  • Encryption keys.

  • Campaign and build identifiers.

  • Embedded URL paths and other configuration values.

  • Intelligence to distinguish affiliates and infrastructure clusters.

This information helped partners prioritize infrastructure for disruption and identify relationships between otherwise separate malware deployments.

4.3 Amadey command-and-control communication

ESET's analysis describes Amadey as communicating with its C2 server over HTTP using POST requests.

The communication process consists of three high-level stages.

Stage 1: Initial beacon

The infected system sends an initial request containing the value st=s. The server responds with a sleep interval, for example 10, instructing the malware to wait before its next check-in.

Stage 2: Registration

The malware sends system information encrypted with RC4. The reported information includes:

  • Operating-system version.

  • Username and computer name.

  • Installed antivirus product.

  • Administrative privileges.

  • The sd value.

  • Other host information.

The RC4 key is embedded in the malware sample and is not transmitted over the network. ESET observed that a server did not serve tasks for more than one RC4 key at a time in its telemetry, suggesting that the C2 server needed to know the expected key for the corresponding sample.

Stage 3: Tasking

The server responds with a task list containing structured commands. Tasks are delimited by <c> and <d> tags, with individual commands separated by # characters.

Depending on the task, the malware can download and execute an EXE, start a VNC component, or run a credential-stealing plugin. Tasks can also include parameters such as a privilege-escalation flag, target directory, and payload URL.

This task-based model allows Amadey affiliates to use the same malware family for different objectives and payload-delivery campaigns.

4.4 Amadey configuration and affiliate clustering

ESET identified three important configuration values in Amadey samples:

  • C2 URLs.

  • RC4 keys used to encrypt C2 communication.

  • An sd value transmitted during the initial handshake.

The sd value is a six-character hexadecimal string matching the pattern:

[0-9a-f]{6}

Although it has sometimes been called a campaign ID or Amadey ID, ESET's analysis suggests that it more accurately represents a build identifier.

Amadey's C2 URLs commonly follow this pattern:

http(s)://<C&C>/<random_path>/index.php

ESET observed that the same URL path component was sometimes reused across different C2 servers. This provided a useful clue that the servers could belong to the same affiliate cluster.

The researchers used graph modeling to combine these configuration values and infrastructure relationships. Their analysis identified 53 distinct Amadey clusters.

The research also found that each sd value was associated with exactly one RC4 key, while rebuilds could preserve the key and change the sd value. RC4 keys and reused URL paths therefore offered useful ways to group related samples and identify infrastructure that might be operated by the same affiliate.

4.5 The largest Amadey cluster

ESET identified one Amadey cluster that accounted for nearly 34% of the processed samples. It was also the only cluster active throughout the entire analyzed period.

This cluster was notable for the number of payloads it delivered. ESET estimated that samples belonging to the cluster delivered an average of approximately 14 payloads per victim in a single execution.

The payloads included a broad range of malware families, from information stealers and remote-access trojans to malware protected by complex code-protection mechanisms.

ESET also observed that multiple Lumma Stealer samples attributed to different affiliates were sometimes delivered to the same victim. This meant several affiliates could obtain the same stolen data. The researchers inferred that the operators behind the largest Amadey cluster may have operated their own pay-per-install model, monetizing access to infected computers.

This is an analytical conclusion from ESET's observed telemetry, not proof that every Amadey affiliate operated such a model.

4.6 StealC command-and-control communication

StealC communicates with its C2 server using HTTP and RC4-encrypted JSON objects.

ESET reported that current versions contained two separate RC4 keys:

  1. A key used to decrypt obfuscated strings at runtime.

  2. A key used to encrypt C2 network communications.

StealC samples also contain a build identifier representing an individual campaign. The C2 address and URL path are stored among encrypted strings and can be extracted through malware configuration analysis.

The initial request contains three main values:

  • build: The build identifier.

  • hwid: A fingerprint of the compromised machine.

  • create: The request type used during initial registration.

The machine fingerprint is derived from the system's volume serial number and formatted as a UUIDv4 string.

The C2 server responds with a JSON configuration describing which features the malware should execute. The response includes a randomly generated access_token that must be supplied in subsequent requests.

ESET described three additional request types:

  • upload_file: Sends collected files to the C2 server.

  • loader: Retrieves and executes an additional payload.

  • done: Signals that the operation has completed.

The server configuration can also specify whether the malware should capture a screenshot or self-destruct after finishing its tasks.

4.7 StealC affiliate clustering

Unlike a centrally managed infrastructure, StealC affiliates operate separate C2 servers and generate their own builds.

ESET applied graph modeling to configuration values extracted from samples and identified 73 distinct StealC clusters operating since March 2025.

These clusters were generally small, often centered on one or a few C2 servers and associated with only a small number of build identifiers or URL paths.

This fragmentation complicates infrastructure disruption. Removing a single server may interrupt one affiliate's operations without affecting other affiliates using independent infrastructure.

4.8 Why disruption does not equal eradication

The Australian operation and Operation Endgame interrupt the attackers' ability to control infected systems through the targeted infrastructure. They do not necessarily remove the malware from those systems.

Several risks remain:

  • Previously stolen passwords may still be valid.

  • Stolen session cookies may permit access to authenticated accounts.

  • Other Amadey botnets may continue operating.

  • Affiliates may rebuild their C2 infrastructure.

  • Additional payloads already deployed may operate independently.

  • Stolen information may be sold or reused months after the original infection.

The Hacker News also reported a separate ASD case in which the agency received a tip that approximately five terabytes of stolen business data were being offered for sale. The business was reportedly unaware of the compromise. ASD said it accessed the criminal operation and destroyed the data before it could be sold, including an estimated 4.8 million files stolen from Australians and hundreds of thousands from victims in other countries.

This was a separate case, not evidence that the data was stolen by Amadey or StealC.

5. Indicators of Compromise (IOCs)

ESET's June 2026 report published historical file hashes and network indicators associated with Amadey and StealC. The indicators below are reproduced from that report.

Important: These are historical indicators associated with the research and disruption period. Their publication does not establish that the listed infrastructure remains active today or that every indicator was part of the specific Australian controller disruption reported in October.

5.1 File indicators — SHA-1

SHA-1FilenameESET detection nameDescription
11A42EF076686CB27BA2C8845301943652A5AADCKB.14.804.8407.exeWin64/Stealc.AStealC infostealer
32D0C3300825B0BB991C4A8F1E6244F0AD2DA989yinkaroj.exeWin64/Stealc.AStealC infostealer
5F3F99B14243404C7CF57B40BB101244CCE394BFMusNotification.exeWin64/Stealc.BStealC infostealer
B4101027BF2F1261402BF6318C6EB016CE249037Patch.exeWin32/Spy.Agent.QOLStealC infostealer
F61E3A643F2417E1A1AB2C83BBDBFC8A7CB96756VeloTeam_x32.exeWin32/Spy.Agent.QOLStealC infostealer
09002D4668A778853E8DA5C488C6E421C0628357Not specifiedWin32/TrojanDownloader.Amadey.AAmadey
87867AD29E621BF9EBF57E1757F75090842458BENot specifiedWin32/TrojanDownloader.Amadey.AAmadey
38D744543B2051E6F749AF171B5EF8D6DF8AAC7BNot specifiedWin64/TrojanDownloader.Amadey.AAmadey
C0E178D26E1E613985A9C67E649D71D54642E0EEDNot specifiedWin64/TrojanDownloader.Amadey.AAmadey
FF8D2AFD9D7F0A822092FEE34CA55D1A3542F7EDNot specifiedWin32/TrojanDownloader.Amadey.AAmadey

5.2 Network indicators

IP addressDomainFirst seenAssociated malware
62.60.226[.]159Not specified2026-04-13Amadey C2
64.188.91[.]237Not specified2026-03-19StealC C2
94.154.35[.]25Not specified2026-03-26Amadey C2
95.85.238[.]4Not specified2026-04-09StealC C2
176.111.174[.]140Not specified2026-03-04Amadey C2
176.124.199[.]207Not specified2026-03-31StealC C2
188.114.96[.]1mi.overlapsnowbound[.]com2026-04-02Amadey C2
193.156.1[.]16Not specified2026-02-24Amadey C2
194.26.192[.]191Not specified2026-02-20StealC C2
196.251.107[.]130Not specified2026-04-17StealC C2

These network indicators are included for threat hunting and historical correlation. Validate their current status and relevance through trusted threat-intelligence sources before using them for production blocking.

5.3 Configuration and behavioral indicators

IndicatorValue or behaviorSignificance
Amadey build identifierSix hexadecimal characters, matching [0-9a-f]{6}Identifies a particular Amadey build in the reported configuration model
Amadey C2 URL patternhttp(s)://<C&C>/<random_path>/index.phpURL structure observed by ESET
Amadey communicationHTTP POST requestsUsed for beaconing, registration, and task delivery
Amadey encryptionRC4Used to encrypt C2 communication and system information
StealC communicationHTTP with RC4-encrypted JSONUsed for registration, configuration, and data transfer
StealC initial requestbuild, hwid, createIdentifies the sample, infected system, and request type
StealC request typesupload_file, loader, doneUsed for data upload, payload retrieval, and completion signaling

These are technical behavior indicators, not standalone proof of infection. They should be correlated with sample analysis, endpoint activity, and network telemetry.

5.4 IOC limitations

ESET stated that a comprehensive collection of indicators and samples was available through its GitHub repository. The indicators reproduced above are a subset from its report.

The available reporting does not provide a confirmed IOC list for the specific October Australian controller-access operation. Do not automatically attribute the historical IP addresses in this section to that later operation.

6. Potential Impact

6.1 Credential theft

Amadey and StealC can collect credentials from browsers and other applications. Stolen passwords can be used for account takeover, unauthorized access, and further compromise.

6.2 Session hijacking

StealC can collect browser cookies and session information. A valid stolen session cookie may allow an attacker to reuse an authenticated session without completing a new login, potentially bypassing ordinary MFA prompts.

6.3 Remote access and further malware delivery

Amadey's remote-access and loader capabilities can allow an operator to install additional payloads, execute tasks, or maintain access to compromised systems.

6.4 Financial and identity fraud

Stolen wallet data, account credentials, personal information, and application sessions may enable unauthorized transactions, fraud, or identity abuse.

6.5 Business-network compromise

Credentials stolen from an employee workstation may provide access to business applications, cloud services, or privileged accounts. The extent of the impact depends on the credentials and permissions exposed.

6.6 Continued activity after disruption

An interrupted C2 connection does not guarantee that a compromised endpoint is clean. Malware may remain installed, other payloads may continue running, and attackers may attempt to rebuild infrastructure.

6.7 Wider criminal ecosystem effects

MaaS offerings allow different affiliates to reuse the same malware family. Disrupting one infrastructure cluster can reduce criminal capability, but other affiliates may continue to operate independently.

7. Recommendations

7.1 Immediate Actions

1. Identify Amadey and StealC infections

Use EDR, antivirus, endpoint telemetry, and trusted threat-intelligence feeds to identify systems with evidence of either malware family. Review both current alerts and historical detections.

2. Isolate affected systems

Where infection is confirmed or strongly suspected, isolate the affected endpoint according to the organization's incident-response process. Preserve forensic evidence before performing destructive cleanup.

3. Investigate additional payloads

Do not assume that removing Amadey or blocking its C2 connection is sufficient. Inspect the endpoint for StealC, other infostealers, RATs, downloaded executables, and suspicious persistence mechanisms.

4. Reset exposed credentials

From a known-clean device, change passwords that may have been exposed. Revoke application tokens, refresh tokens, and active sessions where appropriate. Prioritize administrator accounts, business email, cloud identities, and financial services.

5. Review authentication activity

Investigate unfamiliar sign-ins, unexpected session reuse, suspicious access locations, and account activity following the suspected infection period.

6. Hunt for validated C2 indicators

Search DNS, proxy, firewall, and endpoint records for the historical indicators in the IOC section. Verify current reputation and operational status before applying broad blocks.

7. Investigate follow-on compromise

Review whether exposed credentials were used to access other systems. Examine cloud audit logs, email activity, remote-access records, and privileged account usage.

8. Preserve evidence

Retain malware samples, process records, file timestamps, network telemetry, authentication logs, and incident timelines. Share validated indicators with trusted partners through appropriate security channels.

7.2 Preventive Actions

1. Restrict untrusted software

Discourage cracked software, unofficial installers, and suspicious update prompts. Use trusted software-distribution channels and application controls where practical.

2. Maintain endpoint security

Keep operating systems, browsers, and applications updated. Ensure endpoint protection and monitoring tools are configured to detect malware loaders, suspicious executables, and unauthorized process behavior.

3. Enforce strong authentication

Use multifactor authentication, preferably phishing-resistant methods where supported. Combine MFA with session management, device protections, and rapid token revocation because stolen cookies may permit session reuse.

4. Apply least privilege

Limit administrative rights and avoid storing privileged credentials on ordinary user endpoints. Reduce the permissions available to service accounts and automation identities.

5. Monitor software installation behavior

Detect fake update installers, suspicious downloads, and executable launches originating from untrusted software. Review software-distribution channels used by affected employees.

6. Monitor for additional malware

Treat an Amadey detection as a potential sign of broader compromise. Check for secondary payloads, remote-access tools, credential stealers, and suspicious persistence.

7. Integrate threat intelligence

Use current intelligence feeds to identify known C2 infrastructure, malware hashes, and configuration indicators. Validate indicator freshness before making blocking decisions.

8. Prepare for infrastructure rotation

Build detections around malware behavior, configuration patterns, and endpoint activity instead of depending only on fixed IP addresses or domains that attackers may replace.

9. Respond to credential exposure quickly

When an infostealer infection is confirmed, revoke sessions and rotate exposed credentials promptly. Monitor the affected accounts for delayed misuse because stolen data may be retained for months.

8. Detection and Threat-Hunting Guidance

Security teams should correlate endpoint, network, and identity evidence to identify infections and determine their full scope.

Detection areaInvestigation focus
Endpoint telemetryAmadey or StealC detections, suspicious executable launches, and malware-loader behavior
Network telemetryConnections to validated C2 infrastructure and unusual HTTP POST activity
Amadey configurationEmbedded C2 URLs, RC4 keys, and six-character hexadecimal build identifiers
StealC configurationBuild identifiers, encrypted C2 settings, and suspicious upload or loader requests
Software installationFake update prompts, cracked installers, and untrusted executable downloads
Credential activityUnusual logins, session reuse, and unauthorized access after a suspected infection
Additional payloadsNew executables, suspicious child processes, and downloaded malware
Post-disruption activityAttempts to reconnect to replacement infrastructure or evidence that malware remains on the host

Infrastructure clustering

ESET's research shows that C2 clustering can reveal relationships between apparently separate servers.

For Amadey, analysts can compare:

  • RC4 keys embedded in samples.

  • The six-character sd build identifier.

  • C2 URL paths, particularly reused random-path components.

  • The server addresses and domains associated with those configurations.

For StealC, analysts can compare:

  • The two RC4 keys embedded in samples.

  • Build identifiers.

  • C2 addresses and URL paths.

  • Related sample configurations and communication patterns.

Such analysis can help identify infrastructure that may belong to the same affiliate. These values should be extracted and correlated through authorized malware-analysis workflows, not used as isolated proof that a server remains malicious.

Disruption and incident response

Infrastructure disruption is most effective when paired with endpoint and identity remediation. After a C2 server becomes unavailable, organizations should continue checking for installed malware, stolen credentials, suspicious sessions, and independently operating payloads.

The Australian action and Operation Endgame also demonstrate the importance of intelligence sharing. Malware samples, configuration data, C2 records, and cluster relationships can help authorities and defenders identify high-impact infrastructure and prioritize disruption.

9. Conclusion

The disruption of an Amadey controller by Australia's ASD and the earlier Operation Endgame action demonstrate how coordinated technical intelligence and infrastructure access can interrupt malware operations at scale.

ESET's long-term analysis helped partners identify the infrastructure and configurations used by Amadey and StealC affiliates. Its identification of 53 Amadey clusters and 73 StealC clusters also illustrates why malware-as-a-service operations cannot always be dismantled through a single takedown.

The Australian action reportedly disconnected one Amadey controller from approximately 180,000 infected computers. Operation Endgame separately targeted a broader set of infrastructure associated with Amadey, StealC, and SocGholish. These are distinct developments, and neither should be interpreted as proof that all malware infections were removed or every operator was eliminated.

Organizations should combine endpoint investigation, credential rotation, session revocation, threat-intelligence monitoring, and least-privilege controls. A successful infrastructure disruption is an important step, but the lasting security outcome depends on whether infected devices and exposed identities are also remediated.

MITRE ATT&CK Mapping

T1204.002 — Malicious FileT1059.003 — Windows Command ShellT1106 — Native APIT1129 — Shared ModulesT1547.001 — Registry Run Keys / Startup FolderT1055.002 — Portable Executable InjectionT1027 — Obfuscated Files or InformationT1555.003 — Credentials from Web BrowsersT1552.001 — Credentials In FilesT1528 — Steal Application Access TokenT1539 — Steal Web Session CookieT1005 — Data from Local SystemT1008 — Fallback ChannelsT1071.001 — Web ProtocolsT1573.001 — Symmetric CryptographyT1020 — Automated ExfiltrationT1041 — Exfiltration Over C2 ChannelT1219.002 — Remote Access Software