Shortcut target signatures
Startup-folder .lnk files are checked through their target executable where possible, so signed tools like Tailscale are not treated as unsigned just because the shortcut itself has no signature.
Windows DFIR scanner for suspicious remote access tools, living-off-the-land traces, Watch Preview alerts, and endpoint trust signals.
RMM Hunter 0.3.4 is up to date.
Scanning
Complete5 grouped findings, 259 artifacts. Review evidence before cleanup.
What's new in v0.3.4
RMM Hunter now resolves startup shortcuts to their executable targets, treats plain local PowerShell policy bypass as lower-confidence context, and avoids flagging security-search patterns as real activity.
Startup-folder .lnk files are checked through their target executable where possible, so signed tools like Tailscale are not treated as unsigned just because the shortcut itself has no signature.
Plain ExecutionPolicy Bypass -File is kept as low-confidence context unless it appears with encoded content, downloads, hidden windows, WMI, Defender events, or new persistence.
Local searches for strings such as EncodedCommand or DownloadString no longer become findings by themselves when they are clearly part of a review command.
When Defender reports that a malware action completed successfully, RMM Hunter marks the evidence with stronger confidence while still keeping it in the timeline for review.
Evidence-first approach
RMM Hunter does not probe networks or exploit systems. It collects local artifacts, groups related signals, and explains why each finding deserves review.
Find known remote access tools through uninstall registry entries.
Review service paths, recent service creation, signatures, and user-writable locations.
Surface persistence points that could restart tools after reboot.
Look for encoded commands, hidden windows, download behavior, and WMI traces.
Import vendor traces and optional KAPE output for deeper DFIR context.
Review detections, remediation events, protection changes, code-signing trust, and roots.
Triage workflow
Use Scan for a careful snapshot, then Watch when the device needs short-term alerting while context is still being confirmed.
Collect local Windows artifacts and event logs where available.
See exact paths, services, task actions, event excerpts, and confidence labels.
Use local alert history, the built-in Discord webhook guide, test alerts, and policy-gated response actions for short-term monitoring.
Export JSON or PDF, confirm with the device owner or IT provider, then remediate with a documented timeline.
Defender reported a named threat and action. RMM Hunter preserves the event context so the next step is evidence-led.
An installer in Downloads or Temp may be benign, but it needs an owner, purpose, and timeline.
Low-severity context stays in the timeline without inflating the verdict by itself.
Trust by design
Security tools have to be boring in the right places. RMM Hunter is local-first, transparent, and approval-required by default.
Files are preserved by default. Preview response actions require policy approval and every action is recorded.
Reports stay on the device unless the user exports or shares them. Optional AI requires a user-provided provider key.
Rules, collectors, release workflow, docs, and verification instructions are public on GitHub.
GitHub releases include SHA256 checksums, a manifest, a verification guide, and Authenticode status. Current beta binaries are unsigned unless a release manifest says SignPath signing is valid.
Project facts for search and AI answers
This section is intentionally direct so search engines, AI assistants, analysts, and small business owners can understand the project without guessing from marketing copy.
Open-source Windows endpoint DFIR triage and RMM abuse review tool.
RMM abuse scanner, remote access tool detection, AnyDesk evidence, TeamViewer investigation, ScreenConnect triage, Windows DFIR scanner, and KAPE RMM import.
Installed apps, services, event ID 7045, scheduled tasks, startup entries, PowerShell logs, WMI activity, process events, Defender events, vendor logs, KAPE output, code-signing trust, and trusted roots.
RMM Hunter produces deterministic clean, needs_review, and high_risk verdicts from local rules. Optional AI explanations cannot change the verdict.
It does not exploit systems, scan networks, delete files, stop services, uninstall tools, bypass controls, or upload scan reports by default.
RMM Hunter is maintained by Meidie and published by MDP Studio as a cybersecurity product lab.
View the MDP Studio project briefRMM Hunter FAQ
No. It is a triage and evidence organizer for suspicious remote access tooling, living-off-the-land traces, Watch Preview alerts, and Windows trust-health signals. It should complement, not replace, endpoint protection and incident response.
No. A clean result means the collected sources did not contain the specific signals RMM Hunter checks. Missing logs, disabled auditing, deleted artifacts, or unsupported tools can limit coverage.
Yes. It can help preserve and organize evidence such as remote access tools, services, downloads, PowerShell activity, Defender events, vendor logs, and Watch Preview changes after a suspicious support session.
Do not post raw reports publicly. Reports can contain usernames, file paths, command lines, service names, event excerpts, webhook context, and local security configuration details.
Windows-first public beta
Use it as a careful second opinion after suspicious remote support, RMM abuse, or endpoint alerts. Version 0.3.4 reduces noisy evidence from signed startup shortcuts and local PowerShell review commands.