Skip to main content
Mallory
MalwareUsed by 2 actors

Tickler

Tickler is a custom multi-stage backdoor used by the Iranian state-sponsored threat actor Peach Sandstorm, which Microsoft assesses operates on behalf of the IRGC. Microsoft observed Tickler deployed between April and July 2024 in campaigns targeting organizations in the satellite, communications equipment, oil and gas, and U.S. federal and state government sectors, with victims in the United States and the United Arab Emirates. Reporting also describes targeting of defense, space, education, government, energy, telecommunications, and satellite-related entities in overlapping Peach Sandstorm activity.

Tickler uses attacker-controlled Azure infrastructure for command and control, including fraudulent or compromised Azure subscriptions and Azure App Service resources. Microsoft observed the malware communicating with attacker-controlled Azure resources, and Peach Sandstorm used compromised education-sector accounts to access existing Azure subscriptions or create new Azure for Students subscriptions to host operational infrastructure.

Observed delivery included a decoy-laden ZIP archive such as "Network Security.zip" containing benign PDF documents and a malicious executable named "YAHSAT NETWORK_INFRASTRUCTURE_SECURITY_GUIDE_20240421.pdf.exe." Microsoft identified at least two Tickler samples. An initial 64-bit C/C++ PE sample traversed the PEB to locate kernel32 functionality, launched a benign PDF decoy, collected host and network information, and sent it to a C2 URI via HTTP POST. A later sample, "sold.dll," acted as a Trojan dropper that downloaded additional payloads from C2, including legitimate signed binaries such as msvcp140.dll, LoggingPlatform.dll, vcruntime140.dll, and Microsoft.SharePoint.NativeMessaging.exe, likely to support DLL sideloading.

Tickler establishes persistence via a batch script that adds a registry Run key for "SharePoint.exe" and uses legitimate Windows-signed binaries to evade detection. Reported backdoor capabilities include beaconing to Azure App Service, downloading additional payloads, host and network discovery, directory listing, command execution, file deletion, configurable beacon interval, and file upload/download. Explicitly observed commands include systeminfo, dir, run, delete, interval, upload, and download.

Associated tradecraft in the same campaigns included password spraying against thousands of organizations, use of the user agent "go-http-client," sign-ins from commercial VPN infrastructure after credential validation, and LinkedIn-based reconnaissance and possible social engineering by Peach Sandstorm. High-confidence malware-related indicators directly mentioned in the content include the archive "Network Security.zip," the executable "YAHSAT NETWORK_INFRASTRUCTURE_SECURITY_GUIDE_20240421.pdf.exe," the DLL "sold.dll," and persistence via a Run key for "SharePoint.exe."

Share:
For your environment

Hunt this family in your stack

Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.

THREAT ACTORS

Groups observed using it

2 distinct threat actors attributed by public researchers. Open in Mallory to see the full evidence chain and overlapping campaigns.

View more details
APT33

Between April and July 2024, Microsoft observed Iranian state-sponsored threat actor Peach Sandstorm deploying a new custom multi-stage backdoor, which we named Tickler.

via microsoft security blogmicrosoft.com
Fatimiyoun Electronic Team

In 2024, they... deployed Tickler malware against US and UAE satellite, government, and energy sectors.

via polyswarmblog.polyswarm.io
MITRE ATT&CK

Techniques & procedures

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

T1583.004ServerEvidence1

APT33 uses Azure Active Directory (AAD) and Azure subscriptions as C2 infrastructure. Their custom malware, Tickler, was observed communicating with attacker-controlled Azure resources.

Initial Access

2 techniques
T1566PhishingEvidence1

Multiple Iran-nexus APT groups are described as using spear-phishing: e.g., Charming Kitten uses “spear-phishing with fake personas and compromised emails… phishing via benign PDFs for credential harvesting”; several others use “spear-phishing with malicious documents/attachments/links.”

T1566.001Spearphishing AttachmentEvidence1

The first sample was contained in an archive file named Network Security.zip alongside benign PDF files used as decoy documents.

Persistence

1 technique
T1547.001Registry Run Keys / Startup FolderEvidence1

The batch script adds a registry Run key for a file called SharePoint.exe, likely used to load the malicious DLL files above, thus setting up persistence

T1547.001Registry Run Keys / Startup FolderEvidence1

The batch script adds a registry Run key for a file called SharePoint.exe, likely used to load the malicious DLL files above, thus setting up persistence

Stealth

1 technique
T1036MasqueradingEvidence1
TacticStealth

The archive file contained: YAHSAT NETWORK_INFRASTRUCTURE_SECURITY_GUIDE_20240421.pdf.exe – the Tickler malware

Discovery

1 technique
T1082System Information DiscoveryEvidence1
TacticDiscovery

The sample collects the network information from the host and sends it to the C2 URI via HTTP POST request

T1071Application Layer ProtocolEvidence2

Peach Sandstorm deployed a new custom multi-stage backdoor, Tickler, and leveraged Azure infrastructure hosted in fraudulent, attacker-controlled Azure subscriptions for command-and-control (C2).

T1071.001Web ProtocolsEvidence1

The sample collects the network information from the host and sends it to the C2 URI via HTTP POST request

T1105Ingress Tool TransferEvidence1

The malware downloads additional payloads from the C2 server, including a backdoor, a batch script to set persistence for this backdoor

INDICATORS OF COMPROMISE

IOCs tracked for this family

5 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Full values are available in Mallory.

View more in app
Hashes
5 tracked

File hashes (MD5, SHA-1, SHA-256) from samples and reports.

TypeValueLatest sighting
hash.sha256●●●●●●●●●●●●View more in app2 months ago
hash.sha256●●●●●●●●●●●●View more in app2 months ago
hash.sha256●●●●●●●●●●●●View more in app2 months ago
hash.sha256●●●●●●●●●●●●View more in app2 months ago
hash.sha256●●●●●●●●●●●●View more in app2 years ago
What this page doesn’t show

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 matching5

Match every observed IP, domain, and hash against your live telemetry.

Threat actor attribution2

Named campaigns wielding this family, with evidence pinned to each claim.

Exploited vulnerabilities

CVEs this family uses for access and lateral movement.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

MITRE ATT&CK mapping9

Every documented technique, ranked by evidence weight.

Researcher chatter

Reddit, Mastodon, and CTI community discussion around this family.