Loading vulnerability…
A remote code execution vulnerability exists in ZZ Inc. KeyMouse Windows versions 3.08 and prior due to the application's failure to authenticate update requests. An attacker can exploit this by triggering an update process on a vulnerable installation, allowing execution of arbitrary code.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a working proof-of-concept exploit for CVE-2022-24644, a remote code execution vulnerability in ZZ Inc. KeyMouse 3.08 for Windows. The exploit leverages the application's insecure update mechanism, which fetches update information and binaries from www.keymouse.com over HTTP without authentication or signature verification. The attacker sets up a malicious HTTP server (cve-2022-24644_poc.py) that mimics the legitimate update server, serving a crafted versions.txt and a malicious executable (proof.exe, compiled from proof.c). The README details the steps: the target's hosts file or DNS must be manipulated to redirect www.keymouse.com to the attacker's server. When the KeyMouse application checks for updates, it downloads and executes proof.exe as Administrator, resulting in a command shell being opened at high integrity. The repository contains three files: a README with exploitation instructions, a Python HTTP server script, and a C source file for the payload. The exploit is operational and demonstrates real code execution on the target.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.