Skip to main content
Mallory
Malware1 associated actor

HazyBeacon

Tracked since Dec 4, 2025 · Updated 4 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
Vulns0Associated
Actors1Associated
ATT&CK19Techniques
IOCs7Tracked
Type
Backdoor
Capabilities
KeyloggingExfiltrationPersistencePost exploitationDefense evasionReconnaissanceDLL sideloading
Platforms
Windows

HazyBeacon is a previously undocumented Windows backdoor associated with the CL-STA-1020 cyber-espionage cluster and used in operations targeting government entities in Southeast Asia since at least late 2024. The campaign has been assessed as focused on covert intelligence collection, including theft of sensitive government information related to tariffs and trade disputes.

On compromised Windows systems, HazyBeacon operates as a lightweight backdoor that profiles the host, establishes command-and-control over HTTPS, receives remote commands, and downloads additional payloads. A notable characteristic of the campaign is its use of AWS Lambda Function URLs as command-and-control relays, allowing malicious traffic to blend with legitimate communications to Amazon infrastructure. Reporting also indicates the broader operation abused compromised AWS accounts and publicly accessible Lambda Function URLs, relying on weak cloud identity and configuration practices rather than vulnerabilities in AWS itself.

Initial execution on victim hosts has been linked to DLL sideloading using a legitimate Microsoft .NET executable to load a malicious DLL. Persistence was maintained through creation of a Windows service so the backdoor would relaunch after reboot. After establishing command-and-control, operators deployed follow-on tooling for file collection and staging. Observed post-compromise activity included targeted file discovery, collection of documents matching selected extensions and time ranges, archive creation and splitting, and attempted exfiltration through common cloud storage services. Additional reporting attributes to HazyBeacon capabilities including remote command execution, document theft, and keystroke capture.

HazyBeacon exemplifies a cloud-enabled espionage tradecraft model in which trusted third-party infrastructure is repurposed to conceal command-and-control and complicate detection. Its targeting, stealthy command channel design, and follow-on collection behavior are consistent with a state-aligned intelligence-gathering operation against Southeast Asian government networks.

Is this in your environment?See whether this family's indicators match your telemetry and which of your assets are exposed to the CVEs associated with it.
Check your exposure
Threat actors

Associated threat actors

1 distinct threat actor Mallory has associated with this family across public reporting. Open in Mallory to see the full evidence chain and overlapping campaigns.

View more details →
CL-STA-1020

A malicious campaign attributed to the group “CL-STA-1020” has been observed targeting government agencies in Southeast Asia, leveraging a previously undocumented Windows backdoor, dubbed HazyBeacon.

via ncert phncert.gov.ph
MITRE ATT&CK

Techniques & procedures

19 distinct techniques documented for this family, organized by ATT&CK tactic.

Resource Development

1 technique
T1583.006Web ServicesEvidence1

Attackers compromise AWS accounts belonging to unrelated organizations and plant lightweight serverless functions inside them as hidden relay points.

Initial Access

3 techniques
T1078Valid AccountsEvidence1

Attackers exploit stolen IAM credentials to create Lambda functions in compromised AWS accounts.

T1078.004Cloud AccountsEvidence1

Attackers validate stolen keys with quiet API calls, upload a zipped Python or Node.js payload as a Lambda function with a benign name like “UpdateWorker,” and deploy it in a low-scrutiny AWS region to avoid detection.

T1566PhishingEvidence2

Credential compromise: IAM keys are stolen from exposed repositories or phishing campaigns.

Execution

3 techniques
T1059Command and Scripting InterpreterEvidence1

HazyBeacon is a lightweight backdoor that profiles systems, executes remote commands, and exfiltrates data, including documents and keystrokes.

T1059.003Windows Command ShellEvidence1

It receives encrypted commands to run shell instructions or pull down further payloads.

T1648Serverless ExecutionEvidence1

The core of this attack is the abuse of AWS Lambda Function URLs... Attackers choose this option to spin up a public HTTPS relay inside AWS infrastructure within seconds.

Persistence

3 techniques
T1078Valid AccountsEvidence1

Attackers exploit stolen IAM credentials to create Lambda functions in compromised AWS accounts.

T1078.004Cloud AccountsEvidence1

Attackers validate stolen keys with quiet API calls, upload a zipped Python or Node.js payload as a Lambda function with a benign name like “UpdateWorker,” and deploy it in a low-scrutiny AWS region to avoid detection.

T1543.003Windows ServiceEvidence1

The threat actor created a Windows service for persistence to ensure that the malicious DLL would load even after rebooting the compromised system.

Privilege Escalation

3 techniques
T1078Valid AccountsEvidence1

Attackers exploit stolen IAM credentials to create Lambda functions in compromised AWS accounts.

T1078.004Cloud AccountsEvidence1

Attackers validate stolen keys with quiet API calls, upload a zipped Python or Node.js payload as a Lambda function with a benign name like “UpdateWorker,” and deploy it in a low-scrutiny AWS region to avoid detection.

T1543.003Windows ServiceEvidence1

The threat actor created a Windows service for persistence to ensure that the malicious DLL would load even after rebooting the compromised system.

Stealth

3 techniques
T1027Obfuscated Files or InformationEvidence1

Relay setup: Public Function URLs are enabled for command transmission. C2 communication: Malware sends encrypted requests to Lambda, which forwards them to attacker-controlled servers and relays responses back.

T1078Valid AccountsEvidence1

Attackers exploit stolen IAM credentials to create Lambda functions in compromised AWS accounts.

T1078.004Cloud AccountsEvidence1

Attackers validate stolen keys with quiet API calls, upload a zipped Python or Node.js payload as a Lambda function with a benign name like “UpdateWorker,” and deploy it in a low-scrutiny AWS region to avoid detection.

Credential Access

3 techniques
T1056.001KeyloggingEvidence2

HazyBeacon is a lightweight backdoor that profiles systems, executes remote commands, and exfiltrates data, including documents and keystrokes.

T1528Steal Application Access TokenEvidence1

Attackers steal static IAM access keys from exposed GitHub repositories or phishing campaigns, then use those keys to build a relay inside a compromised cloud account.

T1552Unsecured CredentialsEvidence1

Credential compromise: IAM keys are stolen from exposed repositories or phishing campaigns.

Discovery

1 technique
T1082System Information DiscoveryEvidence2

HazyBeacon is a lightweight backdoor that profiles systems, executes remote commands, and exfiltrates data, including documents and keystrokes.

Collection

1 technique
T1056.001KeyloggingEvidence2

HazyBeacon is a lightweight backdoor that profiles systems, executes remote commands, and exfiltrates data, including documents and keystrokes.

Command and Control

4 techniques
T1071Application Layer ProtocolEvidence3

This backdoor leverages a novel C2 technique in which the backdoor establishes C2 communication via AWS Lambda URLs.

T1071.001Web ProtocolsEvidence1

In this campaign, compromised systems communicate with AWS-hosted Lambda Function URLs. Because the traffic flows through trusted AWS domains, it appears benign to most security tools, effectively bypassing conventional network defenses.

T1090ProxyEvidence2

Use these functions as proxies to relay encrypted communications from malware.

T1105Ingress Tool TransferEvidence2

Once the malicious DLL(mscorsvc.dll) has established connections to the C2 server, it can now receive commands and download additional payloads to the compromised system.

Exfiltration

2 techniques
T1041Exfiltration Over C2 ChannelEvidence2

HazyBeacon is a lightweight backdoor that profiles systems, executes remote commands, and exfiltrates data, including documents and keystrokes.

T1567.002Exfiltration to Cloud StorageEvidence1

In this campaign, the threat actor was observed exfiltrating the collected files via cloud services such as Google Drive and Dropbox.

Indicators of compromise

Observables

7 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Values are masked here and available in full in Mallory.

View all in app →
Indicator values are available in Mallory. Pivot on every hash, domain, URL, and IP, or pipe them straight into your SIEM.View all in Mallory
Activity feed

Recent activity

7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+3 more in the timeline. Sign up to see them
Is this in your environment?See whether this family's indicators match your telemetry and which of your assets are exposed to the CVEs associated with it.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets match these IOCs, which detections are missing, which campaigns to expect next, and what to do in the next 30 minutes.
IOC matching7Match every observed IP, domain, and hash against your live telemetry.
Associated threat actors1Groups linked to this family, with evidence pinned to each claim.
Associated vulnerabilitiesCVEs linked to this family, with the reporting behind each link.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
MITRE ATT&CK mapping19Every documented technique, ranked by evidence weight.
Researcher chatterReddit, Mastodon, and CTI community discussion around this family.