hollows_hunter
v0.4.0 open-sourceThe section your link pointed to isn't on hollows_hunter's page any more, so we've brought you to the top.
hollows_hunter is a command-line tool that scans running processes to recognize and dump malicious implants, shellcodes, hooks, and in-memory patches.
./hollows_hunter.exe /cache /i ./hollows_hunter.exe /pignore "suspicious_process.exe" hollows_hunter --ptimes 300 hollows_hunter.exe /process <pid> /dnet hollows_hunter.exe /suspend ./hollows_hunter.exe /dir C:\cyber\dumps ./hollows_hunter.exe /uniqd
Summary
hollows_hunter is an open-source, BSD 2-Clause licensed command-line tool for Windows that scans running processes for malicious implants such as replaced or injected PEs, shellcodes, hooks, and in-memory patches. Built on the PE-sieve scanning engine, it extends that tool's single-PID scanning into broader targeting by process list, name, or creation time, and can scan every running process if none is specified; it also supports continuous monitoring through a loop mode or as an ETWETWEvent Tracing for Windows, a Microsoft kernel-level logging framework that lets applications and drivers emit structured events; cyber tools use it to observe process, network, and file activity without installing additional sensors. listener. It is aimed at malware analysts and incident responders who need to catch process-hollowing and injection techniques on live systems rather than in static files. First committed in 2018 and still actively maintained, with 54 commits from 5 contributors in the past year.
hollows_hunter is a command-line tool that scans running processes to recognize and dump malicious implants, shellcodes, hooks, and in-memory patches.
How hollows_hunter helps
Which processes on this machine are currently running injected or hollowed code?
scans every running process by default, using the PE-sieve engine to flag replaced or implanted PEs, shellcodes, hooks, and in-memory patches, and dumps each suspicious region for later review
Is this specific set of processes clean, without scanning the whole machine?
accepts a list of PIDs or process names and restricts the scan to just those, so a targeted check does not have to wait on a full sweep
Did anything get injected right after this process launched?
can target processes by creation time relative to when the scan started, catching implants dropped into freshly spawned processes
Is a live intrusion still active on this host right now?
runs continuously in a loop, rescanning at intervals so implants that appear after the first pass are still caught
Can this host be watched for injection as it happens, instead of checked periodically?
runs as an ETW listener on 64-bit systems, reacting to process events as they occur rather than polling on a schedule
Which memory regions were flagged, and where's the evidence for the incident report?
dumps the suspicious PE or shellcode content it finds to disk, giving an analyst the actual bytes behind each detection rather than just a verdict
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for hollows_hunter, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail hollows_hunter puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
25 entries
No entries match these filters.
- December 20241
- February 20241
- November 20232
- November 20221
- February 20221
- January 20221
- December 20211
- June 20211
- April 20211
- July 20202
- June 20202
- April 20201
- March 20201
- December 20191
- October 20191
- August 20191
- June 20192
- May 20191
- December 20181
- November 20182
Project health
Issue, contributor and maintainer activity in hasherezade/hollows_hunter, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 1 −1 vs prior 12 months
- Maintainers 1 +0 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close not measured first maintainer reply 12 hours
- Open backlog 2 of 19 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 2
- Contributors / month 0
- Commits / month 0
- Stars 2,404
- other 100%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.