Rancor is a Windows-focused threat associated with the use of native system utilities for execution and persistence. Reported activity includes abuse of the Microsoft Installer utility msiexec to download and execute malicious installer packages over HTTP, a technique that can blend malicious activity with legitimate signed Windows binaries and support defense evasion. Rancor has also used the Windows command interpreter to execute commands on compromised hosts and has established persistence through scheduled tasks created with schtasks. These behaviors indicate a malware or intrusion set capability set centered on post-compromise execution, persistence, and evasion through living-off-the-land techniques on Windows systems. High-confidence reporting in the available material supports these behaviors, but does not establish a more specific malware family classification, delivery vector, or broader victimology with sufficient certainty.
Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.
99 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Full values are available in Mallory.
File hashes (MD5, SHA-1, SHA-256) from samples and reports.
Other indicator types observed in public reporting.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Malware that used msiexec to download and execute malicious installer files over HTTP.
Malware/tool that uses cmd.exe to execute commands.
Gains persistence by creating a scheduled task via schtasks.
Match every observed IP, domain, and hash against your live telemetry.
Named campaigns wielding this family, with evidence pinned to each claim.
CVEs this family uses for access and lateral movement.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Every documented technique, ranked by evidence weight.
Reddit, Mastodon, and CTI community discussion around this family.