The HyperDbg course is now accessible on YouTube. For the most comprehensive experience, including full lab instructions, please utilize it at https://ost2.fyi/Dbg3301. ✨

This tutorial will guide you through the initial steps of using HyperDbg, covering essential concepts, principles, and debugging functionalities as well as numerous reverse engineering methods achievable by using HyperDbg, along with practical and real-world examples.

Check it out here: 🔗 https://www.youtube.com/watch?v=RDlp0PCFgxI&list=PLUFkSN0XLZ-kF1f143wlw8ujlH2A45nZY

Slides are available at: https://gitlab.com/opensecuritytraining/dbg3301_hyperdbg_slides_and_files

Happy to announce @HyperDbg v0.10! 🎉🎊✨

This version comes with numerous bug fixes and stability improvements, plus new features like running assembly code directly in the events (VMX root-mode) and two new commands.

Check out the latest version: https://github.com/HyperDbg/HyperDbg/releases

For more information,

Assembly codes in conditions:
- https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-a-condition

Assembly codes in code sections:
- https://docs.hyperdbg.org/using-hyperdbg/prerequisites/how-to-create-an-action

Assemble virtual address:
- https://docs.hyperdbg.org/commands/debugging-commands/a

Assemble physical address:
- https://docs.hyperdbg.org/commands/extension-commands/a

# Changelog

## Added
- Support using assembly conditions and codes in all events
- Added the assembler command 'a' for virtual memory
- Added the assembler command '!a' for physical memory
- Providing a unified SDK API for reading memory in the VMI Mode and the Debugger Mode
- Export SDK APIs for reading/writing into registers in the Debugger Mode
- Export SDK API for writing memory in the VMI Mode and the Debugger Mode
- Export SDK API for getting kernel base address
- Export SDK API for connecting to the debugger and from debuggee in the Debugger Mode
- Export SDK API for starting a new process
- Add and export SDK API for unsetting message callback
- Event commands are coming with more examples regarding noscripts and assembly codes
- Add message callback using shared memory
- Add maximum execution limitation to the noscript IRs (#435)

## Changed
- Fix clearing '!monitor' hooks on a different process or if the process is closed (#409)
- Fix triggering multiple '!monitor' hooks with different contexts (#415)
- Fix the problem of repeating commands once kHyperDbg is disconnected
- Fix step-over hangs if the process terminates/excepts within call instruction (#406)
- Fix crash on editing invalid physical addresses (#424)
- Fix exporting VMM module load and install it in the SDK
- Fix function interpretation issues and update the parser and the code execution (#435)

Hi everyone!

We've updated the list of things for which we need contributions from the community in HyperDbg!

If you have some free time, you're more than welcome to join and contribute to the HyperDbg debugger. 😊✨

Check it out:

https://github.com/HyperDbg/HyperDbg/blob/dev/CONTRIBUTING.md

Hi guys!

FYI, the #Discord server and #matrix group are added (and synchronized) to the HyperDbg groups. 🎉🥂

Telegram Group: https://news.1rj.ru/str/HyperDbg

Discord Server: https://discord.gg/anSPsGUtzN

Matrix Group: https://matrix.to/#/#hyperdbg-discussion:matrix.org

Twitter: https://twitter.com/HyperDbg

This is why you should always consider using HyperDbg's noscript engine to avoid what we refer to as "unsafe behavior".

Read more:
https://docs.hyperdbg.org/tips-and-tricks/considerations/the-unsafe-behavior

It's been a while since HyperDbg's first release, and we realized our initial assumptions for the command parser won’t fully meet new demands. After redesigning and extensive testing, HyperDbg v0.10.1 now comes with a brand-new parser! 💫😼

Check it out:
https://github.com/HyperDbg/HyperDbg/releases/tag/v0.10.1

Changelog
————————————

## [0.10.1.0] - 2024-09-08
New release of the HyperDbg Debugger.

### Added
- Added feature to pause the debuggee immediately upon connection
- The '.debug' command now supports pausing the debuggee at startup
- Export SDK API for assembling instructions
- The 'struct' command now supports a path as output
- Export SDK API closing connection to the remote debuggee
- Automated tests for the main command parser
- Export SDK APIs for stepping and tracing instructions
- Export SDK APIs for tracking execution

### Changed
- HyperDbg command-line comment sign is changed from '#' to C-like comments ('//' and '/**/')
- Integrating a new command parser for the regular HyperDbg commands
- Fix showing a list of active outputs using the 'output' command
- Fix the issue of passing arguments to the '.start' command
- Fix the problem with parsing multiple spaces within the events (#420)
- Fix the problem with escaping '{' in the command parser (#421)
- Fix nested brackets issues in the main command parser
- Fix noscript engine bugs on order of passing arguments to functions (#453)
- Fix the noscript test case for factorial computation
- Fix the noscript test case for computation iterative Fibonacci
- Fix miscomputation of physical address width for physical address validity checks (#469)

We are celebrating today as we've reached 200,000 lines of code! A big thank you to all the friends and contributors who made this possible! 🤗

https://github.com/HyperDbg/HyperDbg

HyperDbg v0.10.2 is released!

This release comes with lots of bugfixes and improved stability, check it out here:

https://github.com/HyperDbg/HyperDbg/releases/tag/v0.10.2

Guys, just because HyperDbg’s '!monitor' command can technically monitor unlimited address ranges doesn’t mean you can monitor any memory range you want. So let’s not go wild, alright? 😅

https://docs.hyperdbg.org/commands/extension-commands/monitor