Back to reports

APT41 Winnti ELF Cloud Credential Harvester: Alibaba Typosquat Infrastructure & 6-Year Lineage

PublishedApril 10, 2026

APT41 Winnti ELF Cloud Credential Harvester: Alibaba Typosquat Infrastructure & 6-Year Lineage

Executive Summary

A zero-detection ELF backdoor attributed to APT41 (Winnti) has been identified targeting Linux cloud workloads across AWS, GCP, Azure, and Alibaba Cloud environments. The implant uses SMTP port 25 as a covert command-and-control channel, harvests cloud provider credentials and metadata, and phones home to three Alibaba-themed typosquat domains hosted on Alibaba Cloud infrastructure in Singapore. A selective C2 handshake validation mechanism renders the server invisible to conventional scanning tools like Shodan and Censys.

Credit for the initial lead goes to @TuringAlex, whose work surfaced the sample. @Xlab_qax provided the original Winnti classification and family linkage.

What This Report Adds to the Public Record

This report extends the existing body of work with:

  • Infrastructure mapping — Alibaba Cloud Singapore C2 hosting, NameSilo registration burst pattern across a 24-hour window (Jan 20-21, 2026)
  • Campaign timeline — A 6-year Winnti ELF lineage tracing from PWNLNX (2020) through intermediate variants to this sample
  • Typosquat analysis — Breakdown of three domains impersonating Alibaba Cloud services (Qianxin, Aliyun)
  • Selective handshake validation — Technical analysis of the C2 protocol's scanner-evasion mechanism

We acknowledge that prior researchers identified and classified this sample first. This report aims to complement that work with additional infrastructure and lineage context.


Technical Analysis

Implant Overview

The ELF binary is a stripped, statically linked x86-64 executable designed for persistence on Linux cloud instances. At the time of analysis, it carries zero detections on VirusTotal.

PropertyValue
File typeELF 64-bit LSB executable, x86-64
MD5f1403192ad7a762c235d670e13b703c3
VT detections0/72
CompilationGCC, stripped symbols
Target environmentsAWS, GCP, Azure, Alibaba Cloud

Cloud Credential Harvesting

The implant enumerates cloud provider metadata services and credential stores:

  • AWS: Queries 169.254.169.254/latest/meta-data/iam/security-credentials/ for IAM role credentials, reads ~/.aws/credentials
  • GCP: Queries metadata server for service account tokens, reads application default credentials
  • Azure: Queries IMDS endpoint for managed identity tokens, reads ~/.azure/ profiles
  • Alibaba Cloud: Queries ECS metadata for RAM role credentials, reads Alibaba CLI config

Harvested credentials are encrypted with a hardcoded AES-256 key and staged locally before exfiltration.

SMTP Port 25 Covert C2

Rather than using conventional HTTPS callbacks, the implant establishes C2 communication over SMTP port 25. This is a deliberate choice:

  • Port 25 traffic is expected in cloud environments running mail services
  • Many cloud security tools do not deeply inspect SMTP traffic for C2 patterns
  • Egress filtering on port 25 is inconsistent across cloud providers

The implant constructs SMTP-formatted messages with encoded payloads in the message body, directed at the C2 server. Commands are returned in SMTP reply codes and extended status messages.

Selective C2 Handshake Validation

The C2 server at 43[.]99[.]48[.]196 implements a selective handshake mechanism that rejects connections lacking a valid client-side token in the initial EHLO string. Connections from scanners, crawlers, or probes that do not present the correct token receive a standard SMTP banner and are immediately closed after a benign 220 response.

This means:

  • Shodan/Censys see a generic SMTP server and move on
  • Automated threat feeds do not flag the IP as malicious
  • Only implants with the correct token receive tasking

This is a meaningful evolution in Winnti operational security for Linux implants.

Lateral Movement via UDP Broadcast

The implant periodically sends UDP broadcast packets to 255.255.255.255:6006 within the local network segment. These broadcasts contain an encoded beacon that other compromised hosts can receive, enabling peer-to-peer coordination and lateral tasking distribution without additional C2 traffic.


Infrastructure Analysis

C2 Server

PropertyValue
IP43[.]99[.]48[.]196
HostingAlibaba Cloud
RegionSingapore (ap-southeast-1)
Port25/tcp (SMTP)
Scanner visibilityNone (selective handshake)

Typosquat Domains

Three domains impersonate Alibaba Cloud services and Chinese cybersecurity brand Qianxin:

DomainImpersonatesRegistrarRegistration Date
ai[.]qianxing[.]coQianxin (qianxin.com)NameSilo2026-01-20
ns1[.]a1iyun[.]topAliyun / Alibaba Cloud (aliyun.com)NameSilo2026-01-20
ai[.]aliyuncs[.]helpAlibaba Cloud CDN (aliyuncs.com)NameSilo2026-01-21

All three domains were registered through NameSilo within a 24-hour burst window (January 20-21, 2026) with privacy protection enabled. This registration pattern is consistent with APT41 infrastructure procurement tradecraft — bulk registration through budget registrars with WHOIS privacy, followed by immediate deployment.

The a1iyun typosquat substitutes the numeral 1 for the letter l — a classic homoglyph technique. The aliyuncs[.]help domain mimics the legitimate Alibaba Cloud CDN domain aliyuncs.com used in China's cloud ecosystem.


Campaign Timeline: 6-Year Winnti ELF Lineage

APT41's investment in Linux/ELF tooling is not new. This sample fits within a documented lineage:

YearVariantKey Characteristics
2020PWNLNXFirst documented Winnti ELF implant, basic reverse shell, XOR encoding
2021-2022Winnti 4.0 LinuxModular plugin architecture, kernel rootkit components
2023KEYPLUG (Linux)Reported by Mandiant, HTTPS C2, cloud-aware
2024Intermediate variantsImproved evasion, initial cloud metadata collection
2025-2026This sampleFull cloud credential harvesting, SMTP C2, selective handshake, typosquat infrastructure

This trajectory shows a consistent 6-year investment in making Winnti's Linux tooling cloud-native — progressing from basic reverse shells to purpose-built cloud credential harvesters with scanner-resistant C2.


Indicators of Compromise

File Indicators

TypeValue
MD5f1403192ad7a762c235d670e13b703c3

Network Indicators

TypeValueContext
IPv443[.]99[.]48[.]196C2 server (Alibaba Cloud SG)
Domainai[.]qianxing[.]coTyposquat / C2
Domainns1[.]a1iyun[.]topTyposquat / C2
Domainai[.]aliyuncs[.]helpTyposquat / C2
Port25/tcpSMTP C2 channel
Port6006/udpLateral movement broadcast
Broadcast255.255.255.255:6006Peer discovery

MITRE ATT&CK Mapping

TacticTechniqueID
Initial AccessExploit Public-Facing ApplicationT1190
ExecutionCommand and Scripting Interpreter: Unix ShellT1059.004
PersistenceBoot or Logon Autostart ExecutionT1547
Credential AccessUnsecured Credentials: Cloud Instance Metadata APIT1552.005
Credential AccessCredentials from Password StoresT1555
DiscoveryCloud Infrastructure DiscoveryT1580
DiscoverySystem Network Configuration DiscoveryT1016
Lateral MovementRemote ServicesT1021
Command and ControlApplication Layer Protocol: Mail ProtocolsT1071.003
Command and ControlNon-Standard PortT1571
ExfiltrationExfiltration Over C2 ChannelT1041

Confidence Assessment

AssessmentConfidenceBasis
APT41 attributionHIGHWinnti family classification by @Xlab_qax, code lineage from PWNLNX, infrastructure patterns
Cloud credential harvesting purposeHIGHDirect observation of metadata API queries and credential file reads
SMTP C2 mechanismHIGHNetwork traffic analysis and binary string extraction
Selective handshake as evasionHIGHDifferential testing: scanner-like vs. implant-like connection behavior
NameSilo burst registration patternMODERATETemporal correlation; registrar choice consistent with prior APT41 campaigns
6-year lineage from PWNLNXMODERATECode similarity analysis and capability progression; some intermediate samples lack strong attribution

Detection Guidance

Network-Based

  • Monitor for outbound SMTP (port 25) traffic from non-mail workloads — cloud instances not designated as mail servers should not initiate port 25 connections
  • Alert on UDP broadcast traffic to port 6006 — this is not a standard service port and broadcast usage in cloud VPCs is anomalous
  • Block or monitor connections to 43[.]99[.]48[.]196 and the three typosquat domains

Host-Based

  • Audit for unexpected reads of cloud credential files (~/.aws/credentials, ~/.azure/, GCP application default credentials, Alibaba CLI config)
  • Monitor cloud instance metadata API calls from non-standard processes — legitimate SDKs and CLIs have known process names
  • Hunt for stripped, statically linked ELF binaries in unexpected locations (/tmp, /var/tmp, /dev/shm)
  • Check for cron entries or systemd services referencing unknown ELF binaries

Cloud-Native

  • Enable CloudTrail / Cloud Audit Logs and alert on credential usage from unexpected source IPs
  • Review IAM role assumption events for anomalous patterns
  • Implement IMDSv2 (AWS) to require session tokens for metadata access, raising the bar for credential theft

Prior Art & References

  • @TuringAlex — Initial identification and lead on this sample
  • @Xlab_qax — Winnti family classification and technical analysis
  • Mandiant — KEYPLUG Linux variant reporting (2023)
  • Chronicle / Google TAC — APT41 operational patterns and infrastructure procurement

Breakglass Intelligence | GHOST Offensive Intelligence

We don't wait for advisories. We map the infrastructure before it moves.

Share