Loading malware…
MatrixDoor is a Rust-based Windows backdoor used by the Feral Wolf cybercriminal group during ransomware intrusions against Russian retail, construction, manufacturing, and information-technology organizations in 2026. It communicates with operator-controlled infrastructure using the Matrix protocol and executes received commands through the Windows command interpreter. MatrixDoor can establish persistence as a Windows service and encrypts its configuration using ChaCha20-derived key material tied to the host's MachineGuid value. It also removes its original plaintext configuration after storing the encrypted configuration, reducing configuration exposure. Feral Wolf used MatrixDoor alongside MQTTDoor and RDP-based tunneling capabilities during compromises that culminated in GenieLocker ransomware deployment.
Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.
1 distinct threat actor attributed by public researchers. Open in Mallory to see the full evidence chain and overlapping campaigns.
10 distinct techniques documented for this family, organized by ATT&CK tactic.
3 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Full values are available in Mallory.
IPs, domains, and DNS infrastructure linked to this family.
File hashes (MD5, SHA-1, SHA-256) from samples and reports.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Backdoor used by Feral Wolf that uses the Matrix communication platform or protocol for command-and-control communications.
Custom backdoor using Matrix communications for command-and-control, intended to make hostile traffic more difficult to distinguish from routine activity.
A backdoor used by Feral Wolf for command-and-control communications through Matrix infrastructure.
Rust-based Windows backdoor that uses the Matrix protocol for C2. It persists as a fake Windows Telemetry Aggregator Service, stores encrypted configuration data in the registry, executes CMD commands received in a Matrix room, and exfiltrates command output and system telemetry.
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.