Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
MalwareRansomwareUsed by 1 actor

UX-Cryptor

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

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

View more details
Key Group

For example, UX-Cryptor added itself to the registry as shown below.

via securelistsecurelist.com
MITRE ATT&CK

Techniques & procedures

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

Persistence

2 techniques
T1112Modify RegistryEvidence1

For example, UX-Cryptor added itself to the registry as shown below. HKU \ $ usersid \ Software \ Microsoft \ Windows NT \ CurrentVersion \ Winlogon "Shell" = "$selfpath" HKU \ $ usersid \ Software \ Microsoft \ Windows \ CurrentVersion \ Run "WindowsInstaller" = "$selfpath -startup"

T1547.001Registry Run Keys / Startup FolderEvidence1

For example, the persistence mechanism was always via the registry, but the exact implementation differed by family. Most of the time, autorun was used, but we’ve also seen them using the startup folder.

Privilege Escalation

1 technique
T1547.001Registry Run Keys / Startup FolderEvidence1

For example, the persistence mechanism was always via the registry, but the exact implementation differed by family. Most of the time, autorun was used, but we’ve also seen them using the startup folder.

Defense Impairment

1 technique
T1112Modify RegistryEvidence1

For example, UX-Cryptor added itself to the registry as shown below. HKU \ $ usersid \ Software \ Microsoft \ Windows NT \ CurrentVersion \ Winlogon "Shell" = "$selfpath" HKU \ $ usersid \ Software \ Microsoft \ Windows \ CurrentVersion \ Run "WindowsInstaller" = "$selfpath -startup"

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 matching

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

Threat actor attribution1

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 mapping2

Every documented technique, ranked by evidence weight.

Researcher chatter

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