Loading malware…
Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.
11 distinct techniques documented for this family, organized by ATT&CK tactic.
This spam campaign using QRAT malware has multi-stage downloaders. The first one is a JAR file that may arrive as an email attachment or can be downloaded from a link contained in a spam message.
The QRAT qnode-win32-ia32.js has the following functionalities: obtain system information perform file operations acquire credentials of certain applications... chrome, firefox, thunderbird, and outlook are supported in this QRAT’s password-recovery functionality
The QRAT qnode-win32-ia32.js has the following functionalities: obtain system information... Some of the information, like the machine’s UUID, tags, and labels generated by the malware, will be written in the config file
15 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.
Other indicator types observed in public reporting.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Mentioned as one of the malware families delivered by the loader system.
A remote access trojan marketed via the Quaverse/QHub ecosystem. In this campaign it uses a multi-stage infection chain: an obfuscated Java JAR downloader installs Node.js, retrieves a second-stage script (wizard.js), establishes persistence, and downloads/executes the main QRAT payload. The payload can obtain system information, perform file operations, steal credentials from applications such as Chrome, Firefox, Thunderbird, and Outlook, and communicate with C2 over WebSocket.
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.