HyperDbg
v0.25 open-sourceThe section your link pointed to isn't on HyperDbg's page any more, so we've brought you to the top.
Open-source hypervisor-assisted debugger for Windows using Intel VT-x and EPTEPTExtended Page Tables: an Intel CPU feature that lets a hypervisor give each VM its own second-level address translation in hardware, removing the need for software shadow page tables and cutting VM-exit overhead., supporting kernel/user-mode debugging, EPT hooks, syscall hooking, and hardware t
da 0xffff8000`deadbeef dps 0xfffff803`12340000 uin 0x64 1 db <address> uin <port> !dq <physical_address> ucpuid ucpuid ucpuid !xsetbv p eval <script_name> !a <virtual_address> "nop; jmp 0x1234" a <physical_address> "mov eax, 1; ret" !monitor <address> <length> event_clear(42) !cpuid <eax_index>
Summary
HyperDbg is an open-source, GPLv3-licensed hypervisor-assisted debugger for Windows, with Linux support in progress, run as a command-line debugger rather than a hosted service. It uses Intel VT-x and Extended Page Tables to virtualize an already-running system, and pairs that with Intel Processor Trace for tracing and virtual machine introspection beyond what a conventional user-mode or kernel-mode debugger offers, including EPT hooks and syscall tracing. It targets reverse engineers and researchers doing fuzzing or low-level system analysis rather than general incident responders, and its own docs describe it as an alternative to traditional debuggers built for these hardware-assisted techniques. Recent work adds struct-aware scripting, floating-point types in its script engine, linked-list traversal commands, and per-process Intel PT filtering. With 65 contributors, 344 commits in the past year, and a release 19 days ago, it is under active development.
Open-source hypervisor-assisted debugger for Windows using Intel VT-x and EPT, supporting kernel/user-mode debugging, EPT hooks, syscall hooking, and hardware t
How HyperDbg helps
What is a piece of malware actually doing on a system that keeps deceiving conventional debuggers?
virtualizes the already-running machine with VT-x and EPT and steps through code with hardware-assisted breakpoints, so anti-debug tricks that detect a conventional user-mode or kernel-mode debugger have nothing to catch
What path did a corrupted or malicious data structure take through kernel memory?
walks a linked list directly from virtual or physical addresses and prints each node, without needing hand-written pointer-chasing scripts
Which process is responsible for a burst of suspicious execution across the whole machine?
filters processor-trace output by process name or by thread and process IDs, so the trace covers one process instead of the entire system
What did a piece of code just pass to or get back from a CPUID call, without disturbing its execution context?
runs CPUID in the user-mode context on demand and reports the result inline, without requiring a manual privilege-level switch
Is a HyperDbg module still attached before I try to remove it?
the unload command checks and reports whether any module is currently loaded before attempting the unload
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 HyperDbg, 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 HyperDbg 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
35 entries
No entries match these filters.
- November 20261
- September 20262
- August 20261
- July 20264
- April 20261
- February 20261
- November 20251
- September 20251
- August 20251
- July 20251
- May 20251
- April 20251
- February 20251
- January 20251
- December 20241
- October 20241
- September 20241
- July 20241
- June 20242
- May 20241
- February 20241
- January 20241
- December 20231
- November 20231
- August 20231
- July 20231
- June 20231
- May 20232
- May 20221
Project health
Issue, contributor and maintainer activity in HyperDbg/HyperDbg, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 17 +2 vs prior 12 months
- Maintainers 3 +4 joined · −3 left, last 12 months
- Bus factor 2 committers behind half the commits
- Community-filed 38% of issues opened, last 12 months
- Median time to close 15 days first maintainer reply 7.4 hours
- Open backlog 27 of 187 issues ever filed
- Issues opened / month 1 · 0 communitymaintainers
- Open backlog 27
- Contributors / month 1
- Commits / month 7
- Stars 4,064
- bugs 6%
- features 60%
- other 34%
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.