< Back to blog
high🎣Phishing
investigatedMarch 8, 2026publishedMarch 8, 2026

Same Mutex, Three Lures: Tracking an AsyncRAT Operator Targeting Young Users with Spotify and Roblox Bait

#phishing#asyncrat#c2#exploit#apt

TL;DR: Three AsyncRAT 0.5.8 samples -- two disguised as Spotify, one as a Roblox cheat -- were submitted to MalwareBazaar within 5.5 hours on March 7, 2026. Identical mutexes, PBKDF2 salts, PE timestamps, imphashes, and a shared self-signed TLS certificate prove a single operator compiled all three from the same builder session. The C2 infrastructure spans three domains registered within days of each other, all behind Cloudflare on port 80, all already flagged as suspected phishing.


Why This Cluster Matters

AsyncRAT is ubiquitous, which makes individual samples unremarkable. What makes this cluster worth documenting is the targeting: the operator is luring minors. Spotify piracy and Roblox cheat tools are distribution vectors that overwhelmingly reach teenagers and children -- demographics with minimal security awareness and often no endpoint protection beyond Windows Defender.

The operator's tradecraft is low-sophistication but operationally disciplined: three C2 domains registered across different registrars and TLDs, Cloudflare CDN for IP obfuscation, port 80 for traffic blending, and WHOIS privacy on all registrations. The 8-day infrastructure setup cycle (domain registration through sample deployment) suggests a practiced workflow, not a first-time builder.

All three C2 domains were flagged by Cloudflare within hours of the samples appearing on MalwareBazaar. The operator's infrastructure is currently burned. This report documents the cluster for future pivoting when the operator inevitably rebuilds.

Attack Chain

1. LURE β€” Fake popular software targeting young users
   Filenames: Spotify.exe, RobloxHack.exe
   Distribution: Likely Discord, YouTube tutorials, piracy forums
   ↓
2. EXECUTION β€” .NET assembly, 46,592 bytes
   No obfuscation   |   Anti-analysis: disabled   |   BDOS: disabled
   Internal name: Stub.exe (default AsyncRAT builder output)
   ↓
3. SANDBOX EVASION β€” timeout.exe delay
   3-second delay before payload execution
   ↓
4. PERSISTENCE β€” Dual mechanism
   Scheduled Task β†’ %AppData%\Spotify.exe
   Registry Run key (reversed string to evade static detection)
   ↓
5. C2 β€” AsyncRAT 0.5.8 over port 80
   TLS-encrypted (self-signed RSA-4096/SHA512 cert)
   Proxied through Cloudflare CDN
   ↓
6. POST-COMPROMISE β€” Standard AsyncRAT capabilities
   Keylogging, screen capture, file exfil, plugin execution

Sample Matrix

#File NameSHA256First Seen (UTC)C2 Domain(s)
1Spotify.exe3efd7528...d3812026-03-07 18:15:35malotabcn.com, www.malotabcn.com, malware.malotabcn.com
2Spotify.exe9c970c29...30b22026-03-07 18:06:13www.webcottages.co.uk, malware.webcottages.co.uk
3RobloxHack.exea4019387...d31f2026-03-07 23:34:34indotech.it.com

All three samples are 46,592 bytes with imphash f34d5f2d4577ed6d9ceec516c1f5a744. The ~9 minute gap between Sample 1 and Sample 2 submissions, followed by Sample 3 five hours later, suggests the operator was actively testing C2 connectivity.

Extracted Configuration

RAT King parser successfully decrypted the embedded configuration from all three samples. The shared fields prove a single builder session:

Shared Config (All Samples)

FieldValue
AsyncRAT Version0.5.8
C2 Port80/TCP
Install Path%AppData%\Spotify.exe
MutexfhtrbleYfAeC
PBKDF2 Saltbfeb1e56fbcd973bb219022430a57843003d5644d21e62b9d4f180e7e6c33941
GroupDefault
Delay3 seconds
Anti-Analysisfalse
BDOSfalse
PE Compile Time2026-03-06 09:13:00 UTC (0x69aa9a9c)
Internal NameStub.exe
File Size46,592 bytes
Imphashf34d5f2d4577ed6d9ceec516c1f5a744

Embedded TLS Certificate

CN:         AsyncRAT Server
Algorithm:  SHA512withRSA / RSA-4096
Created:    2026-03-05 18:04:40 UTC
SHA256:     1b1f3aabc166086bbff364f669c1fa80cce9ea0f6f99cba049191f980536bb09
SHA1:       D9:19:25:1B:29:F8:1A:61:10:6E:CF:1C:B3:33:12:CA:72:20:74:33

The self-signed certificate was created on March 5, the PE was compiled on March 6, and samples appeared on March 7. The operator's build-to-deploy cycle is approximately 48 hours.

Per-Sample Differences

Only encryption keys and C2 host lists differ between samples, which is expected -- AsyncRAT regenerates AES keys per build while reusing the builder configuration (mutex, salt, cert):

FieldSample 1Sample 2Sample 3
AES Key0YREVY2fEe7gelluVJNIfjGJ1Ypykq5Mi1ETgT0as851XPZ6tnxINDgzpn53OKHh(extracted via Triage sandbox)
Config Keye57121fe...1558afa5...(different)
C2 Hostsmalotabcn.com (+2 subdomains)webcottages.co.uk (+1 subdomain)indotech.it.com

The .NET assembly structure is consistent across all three: 92 base64-encoded strings at identical offsets for non-config values.

C2 Infrastructure

All three domains follow the same playbook: registered in late February, pointed at Cloudflare, Let's Encrypt certificates issued on the same day, and C2 running on port 80 to blend with HTTP traffic.

Domain 1: malotabcn.com

FieldValue
RegistrarOnamae.com (GMO Internet, Japan)
Created2026-02-28 19:20:47 UTC
PrivacyOnamae.com Privacy Protection Service
Nameserversada.ns.cloudflare.com, yoxall.ns.cloudflare.com
TLSLet's Encrypt E7, issued 2026-03-02
DNS A172.67.131.136, 104.21.10.147 (Cloudflare)
HTTP Status403 -- "Suspected phishing site"

The domain name likely encodes "Malo Barcelona" (malo = "bad" in Spanish, bcn = Barcelona IATA code). Whether this is meaningful or random is unclear.

Domain 2: webcottages.co.uk

FieldValue
RegistrarNamecheap, Inc.
Created2026-01-01
ValidationFAILED (Nominet could not verify registrant)
Nameserversguy.ns.cloudflare.com, harmony.ns.cloudflare.com
TLSLet's Encrypt E7, issued 2026-03-02
DNS A172.67.216.44, 104.21.53.188 (Cloudflare)
HTTP Status403 -- "Suspected phishing site"

The failed Nominet validation is notable. UK .co.uk domains require registrant identity verification through Nominet. The operator either provided false information or failed to respond to verification requests, which typically triggers suspension.

Domain 3: indotech.it.com

FieldValue
TypeSubdomain of it.com (SLD registry service)
TLSLet's Encrypt E7, issued 2026-03-02
DNS A104.21.24.97, 172.67.218.40 (Cloudflare)
HTTP Status403 (Cloudflare blocked)

Using it.com as a second-level domain provider is an interesting OpSec choice. It avoids direct WHOIS exposure entirely -- the domain owner is it.com itself, not the subdomain registrant.

Infrastructure Timeline

2026-01-01  webcottages.co.uk registered (Namecheap)
2026-02-28  malotabcn.com registered (Onamae.com)
2026-03-02  Let's Encrypt certs issued for all three domains (same day)
2026-03-05  Self-signed AsyncRAT server certificate created
2026-03-06  PE compiled (all three samples, single builder session)
2026-03-07  Samples uploaded to MalwareBazaar (18:06 - 23:34 UTC)
2026-03-07  Cloudflare flags all domains as suspected phishing

The operator registered webcottages.co.uk two months before use, suggesting either advance planning or a previously registered domain repurposed for this campaign.

Attribution: Single Operator (HIGH Confidence)

Ten independent indicators confirm all three samples originate from one operator:

EvidenceConclusion
Identical mutex (fhtrbleYfAeC)Same builder config
Identical PBKDF2 saltSame builder config
Identical self-signed TLS cert (created Mar 5)Same AsyncRAT server instance
Identical PE timestamp (0x69aa9a9c)Same compilation session
Identical file size (46,592 bytes)Same builder, same options
Identical imphashSame import table / same binary template
Identical .NET structure (92 base64 strings)Same code generation
All submissions from Germany (DE)Same upload origin
All submitted within 5.5 hoursSame operational window
Anti-analysis + BDOS disabledSame risk tolerance

Operator Profile

  • Skill: Low-to-moderate. Default AsyncRAT 0.5.8 builder, no packer, no obfuscation, anti-analysis disabled, default group name ("Default"), unchanged internal name ("Stub.exe").
  • OpSec: Moderate for the skill level. WHOIS privacy across registrars, Cloudflare proxying, multiple C2 domains for redundancy, port 80 for traffic blending, it.com subdomain to avoid WHOIS.
  • Targets: Young users. Spotify piracy and Roblox cheats are vectors that primarily reach minors.
  • Distribution: Not directly observed. Probable vectors: Discord servers, YouTube "free Spotify premium" tutorials, Roblox exploit forums.
  • Geography: Mixed signals. Japanese registrar (Onamae.com), UK domain (Namecheap), possible Spanish reference in domain name, submissions from Germany. The use of multiple international registrars may be deliberate diversification rather than geographic indication.

Detection Opportunities

Network Signatures

AsyncRAT on port 80 through Cloudflare creates a distinctive pattern: persistent TCP connections to Cloudflare IP ranges with TLS-encrypted payloads that do not conform to HTTP request/response semantics. EDR products that perform TLS inspection will see the self-signed CN=AsyncRAT Server certificate before the Cloudflare tunnel wraps the outer connection.

# Snort/Suricata rule concept
alert tcp $HOME_NET any -> $EXTERNAL_NET 80 (
  msg:"ASYNCRAT C2 - Known Mutex Campaign";
  flow:established,to_server;
  content:"|16 03|"; depth:2;  # TLS handshake on port 80
  reference:md5,550bf59eaf9f3dac8a873278d3c273f6;
  sid:2026030701; rev:1;
)

Host Indicators

# File on disk
%AppData%\Spotify.exe (46,592 bytes, unsigned)

# Mutex
fhtrbleYfAeC

# Scheduled Task
schtasks /create ... %AppData%\Spotify.exe

# Registry persistence (reversed string)
HKCU\Software\Microsoft\Windows\CurrentVersion\Run

YARA Pivot Points

imphash: f34d5f2d4577ed6d9ceec516c1f5a744
PE compile timestamp: 0x69aa9a9c
.NET internal name: Stub.exe
File size: 46,592 bytes

Any combination of imphash + compile timestamp + file size should surface additional samples from this operator's builder if they reuse the same AsyncRAT version.

Vendor Detection (as of 2026-03-07)

VendorDetection
ClamAVWin.Packed.AsyncRAT-9856570-1
ReversingLabsByteCode-MSIL.Backdoor.AsyncRAT (80.56%)
TriageAsyncRAT (behavioral)
CAPEAsyncRAT (behavioral)
VMRayMalicious
KasperskyAsyncRAT
Cloudflare"Suspected phishing site" (all C2 domains)

The 80% detection rate is typical for unobfuscated AsyncRAT. The 20% miss rate is concerning given the target demographic -- these users are unlikely to be running anything beyond default Windows Defender, which was not tested against these specific samples.

MITRE ATT&CK

TacticIDTechniqueCampaign Detail
Initial AccessT1204.002User Execution: Malicious FileFake Spotify/Roblox executables
ExecutionT1059Command and Scripting Interpreter.NET assembly execution
PersistenceT1053.005Scheduled Task/JobTask creation for %AppData%\Spotify.exe
PersistenceT1547.001Boot or Logon Autostart: Registry Run KeysReversed string value to evade static scans
Defense EvasionT1036.005Masquerading: Match Legitimate NameSpotify.exe filename
Defense EvasionT1497Virtualization/Sandbox Evasiontimeout.exe delay (3s)
Defense EvasionT1140Deobfuscate/Decode FilesAES config decryption with PBKDF2 derivation
DiscoveryT1082System Information DiscoveryOS version, system language
DiscoveryT1518.001Security Software DiscoveryAV product enumeration
DiscoveryT1010Application Window DiscoveryActive window title capture
C2T1071.001Application Layer Protocol: WebPort 80 traffic blending
C2T1090.002Proxy: External ProxyCloudflare CDN as C2 proxy
C2T1573.001Encrypted Channel: Symmetric CryptographyTLS-encrypted C2

IOCs

File Hashes

SHA256

3efd75280f8f0c640d174d0fb55df5f3d17a10c4248bbb705281bd74bdf2d381
9c970c29df4fb1398940809e6e7a9bc5088eaca54eed4cdd878c06fd0ed030b2
a40193b7b352fe3a14cfe1ca65c9b5250c663f0240cbcda9be70b7898e57f31f

MD5

550bf59eaf9f3dac8a873278d3c273f6
8accd8a3915e3bbda7689143aacc8f54

SHA1

0f5a6a04f00ec390d62907b82375fa469c68882a
e6c26ce0aef9a6953806a966f3e8e7d3736cdb0e

Domains

malotabcn[.]com
www.malotabcn[.]com
malware.malotabcn[.]com
webcottages[.]co[.]uk
www.webcottages[.]co[.]uk
malware.webcottages[.]co[.]uk
indotech[.]it[.]com

Network

Port:     80/TCP
Imphash:  f34d5f2d4577ed6d9ceec516c1f5a744
Mutex:    fhtrbleYfAeC

TLS Certificate

CN:         AsyncRAT Server
SHA256:     1b1f3aabc166086bbff364f669c1fa80cce9ea0f6f99cba049191f980536bb09
SHA1:       D9:19:25:1B:29:F8:1A:61:10:6E:CF:1C:B3:33:12:CA:72:20:74:33
Not Before: 2026-03-05 18:04:40 UTC
Algorithm:  SHA512withRSA / RSA-4096

PBKDF2 Salt

bfeb1e56fbcd973bb219022430a57843003d5644d21e62b9d4f180e7e6c33941

Investigation by breakglass.intelligence | 2026-03-08

Share: