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

It's been a while since we passed 3,000 stars on GitHub, but we couldn’t let it go uncelebrated! 🌟🎉

We raise our glass to the awesomest community and those who supported and contributed to HyperDbg. 🍾🥂

https://github.com/HyperDbg/HyperDbg

HyperDbg v0.13 is out! 🎉

This version comes with a new command '!pcicam' for dumping and interpreting PCIe CAM, new anti-anti-hypervisor methods, improved MMIO noscripting, plus lots of bug fixes & improvements.

Big thanks to @0Xiphorus & @AbbasMasoumiG.

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


More details are available here:
https://docs.hyperdbg.org/commands/extension-commands/pcicam

HyperDbg v0.13.1 has been released. 💫

This version includes improved mitigations against anti-hypervisor techniques used to detect nested virtualization environments, along with various bug fixes.

Check it out:
https://github.com/HyperDbg/HyperDbg/releases