
We like hypnotizing computers. #HyperDbg https://xitter.cf/t.co/FXulXKTGjp • https://xitter.cf/t.co/u6lVGzQpCE • https://xitter.cf/t.co/47t9Iyaigl
Joined December 2011
- Tweets228
- Following3
- Followers4.2K
- Likes343
HyperDbg retweeted
Debug beyond conventional limits.
Explore Hypervisor-Assisted Reverse Engineering workshop at Hardwear.io N L2026 and uncover low-level Windows behavior through hypervisor-level visibility.
Register now: hardwear.io/nl-2026/talks-sp…
#HardwearNL2026
HyperDbg retweeted
This one is really crazy. They're spreading malware disguised as a hypervisor debugger through a vibe-coded website, vt01[.]com. If you download it, it's malware. The sad part is that they're comparing it with @HyperDbg. 👀
> be me
> get dm
> its my friend @Intel80x86
> author of @HyperDbg
> wtf i love him
> open message
> "smelly i got goop"
> wtf i love goop
> "i found malware campaign"
> wtf i love malware campaigns
> "The Threat Actor(s) have created a website which is specifically tailored to malware analysts, or reverse engineers, who utilize hypervisor-based frameworks. Their malware campaign appears to have begun about 8 days ago. I became aware of the issue when their "product" compared themselves to HyperDbg. Their website is clearly vibe coded, however parts appear to be in Mandarin"
> wtf theyre targeting people who like goop
> sends url to website
> vt01[.]com
> look inside
> lol ai slop
> go to download page
> vt01[.]com/en/download
> immediately flagged as malware by firefox
> allow download plz
> split nanosecond touches the disk
> windows: OMFG MALWARE!!!
> ??? this malware STINKS
> sha256: 5934d1a64afd62e7d1badb81e8613e01efe9cf9c7d6748271c6d0761e3b11eb7
> look inside
> delphi, weird PE sections
> throw into triage
> YARA rules IMMEDIATELY identify the malware family
> XRed
> wtf is XRed?
> cant remember any family named XRed
> December, 2025: XRed impersonates Indian Ministry of Finance and Income Tax Department
> December, 2025: XRed targets US and UK companies that do business in India
> March, 2025: XRed targets manufacturing companies in the United Kingdom
> May, 2025: Threat Actors compromise ProColored, their driver update was compromised to push XRed
> July, 2025: Threat Actors compromise video game mouse company, push malware to video game players who use EndGame Gear for gaming
this is strange goop
HyperDbg retweeted
> be me
> get dm
> its my friend @Intel80x86
> author of @HyperDbg
> wtf i love him
> open message
> "smelly i got goop"
> wtf i love goop
> "i found malware campaign"
> wtf i love malware campaigns
> "The Threat Actor(s) have created a website which is specifically tailored to malware analysts, or reverse engineers, who utilize hypervisor-based frameworks. Their malware campaign appears to have begun about 8 days ago. I became aware of the issue when their "product" compared themselves to HyperDbg. Their website is clearly vibe coded, however parts appear to be in Mandarin"
> wtf theyre targeting people who like goop
> sends url to website
> vt01[.]com
> look inside
> lol ai slop
> go to download page
> vt01[.]com/en/download
> immediately flagged as malware by firefox
> allow download plz
> split nanosecond touches the disk
> windows: OMFG MALWARE!!!
> ??? this malware STINKS
> sha256: 5934d1a64afd62e7d1badb81e8613e01efe9cf9c7d6748271c6d0761e3b11eb7
> look inside
> delphi, weird PE sections
> throw into triage
> YARA rules IMMEDIATELY identify the malware family
> XRed
> wtf is XRed?
> cant remember any family named XRed
> December, 2025: XRed impersonates Indian Ministry of Finance and Income Tax Department
> December, 2025: XRed targets US and UK companies that do business in India
> March, 2025: XRed targets manufacturing companies in the United Kingdom
> May, 2025: Threat Actors compromise ProColored, their driver update was compromised to push XRed
> July, 2025: Threat Actors compromise video game mouse company, push malware to video game players who use EndGame Gear for gaming
this is strange goop
A list hook like this is a reminder of how much deep knowledge modern systems demand. It demands a solid understanding of:
>CPU architecture and privileged instructions
>Paging and EPT
>VMX/VT-x and the VMCS
>Windows kernel internals
>Exception handling and interrupt delivery
HyperDbg retweeted
HyperDbg !epthook command can be used inside Hyper-V Windows Server 2025 VM.
(Testing patches)
HyperDbg retweeted
Part 4 of the hypervisor based game cheat series is up.
This part gets into why hypervisor based game cheats are hard in practice.
What has to stay current across per vCPU VMCS and VMCB state.
Why SMP turns a clean demo into a distributed state problem.
How EPT and NPT views go stale across TLBs, VPID, ASID, PCID, and sibling cores.
Why interrupts, APIC, AVIC, SynIC, posted interrupts, timers, MSR bitmaps, debug state, PMU state, and branch tracing all become part of the cheat mechanics.
Also touched on nested Hyper-V, VBS, VTL, HVCI, SEV-SNP, and TDX as boundary lessons.
No actual cheat code.
The point is to understand what a hypervisor based cheat would need the machine to keep coherent before any game-facing feature can work.
As always, really really grateful to @Intel80x86 @HyperDbg for the great HyperDbg work on hardware assisted debugging, EPT hidden hooks, transparent memory hooks, and monitor style tracing.
Also grateful to memN0ps, DarthTon, Gbps, jonomango, Panicos Karkallis, Jorge Blasco Alis, and the researchers behind HECKLER, WeSee, RMPocalypse, and Fabricked for the excellent public work that helped shape this part.
Couldn’t tag everyone without knowing all of their X accounts. My apologies. 🙏
Give it a light read if this area is interesting. If anything looks wrong, feedback is always welcome. 😇
kernullist.github.io/kernull…
HyperDbg retweeted
Part 3 of the hypervisor based game cheat series is up.
This is where the series starts moving from hypervisor primitives into actual game cheat mechanics.
This part covers EPT hooks, VM exits, VMI, monitoring loops, overlay and input delivery paths, and the point where a low level memory or execution event starts becoming cheat relevant.
Also started touching the actual game cheat side more directly this time, but this is about technical principles and mechanics, not actual code.
Big thanks and credit to @Intel80x86 @HyperDbg for the great HyperDbg work on hardware assisted debugging, EPT hidden hooks, transparent memory hooks, and VM exit based monitoring.
Can't imagine how lost it would've been without HyperDbg. Seriously a lifesaver!
Also grateful to Panicos Karkallis and Jorge Blasco Alís for the VIC research on virtual machine introspection cheats.
For a bit of context, this entire series is originally a single Korean document. Splitting it up due to the length, and it’ll probably be around 8 or 9 parts total.
Translating from the original Korean made the English version feel a bit awkward in earlier parts, so spent some extra time polishing this one. Really hope it’s a much smoother read. 🙏
Please take it as a light read. If anything is wrong or too wordy, feedback is always welcome. 😇
kernullist.github.io/kernull…
HyperDbg retweeted
Part 2 of the hypervisor based game cheats series is up.
This one walks through EPT and NPT as second stage translation, split memory views, EPT violations, EPT misconfigurations, AMD nested page faults, stale TLB views, large page splitting, PML, SPP, TDX, SEV SNP, and why a second stage fault is still not a game fact by itself.
Huge thanks and credit to @Intel80x86 @HyperDbg for the great HyperDbg research and notes.
Please take it as a light read. If anything is wrong or too verbose, feedback is always welcome. 😇
kernullist.github.io/kernull…
HyperDbg retweeted
I'm pleased to announce @HyperDbg v0.19.
This release introduces a new module, HyperTrace, which brings hypervisor-level integration w/ tracing technologies such as Last Branch Record (LBR) & Processor Trace (PT).
LBR is now available, with more coming.
github.com/HyperDbg/HyperDbg…
HyperDbg retweeted
Learn to use a debugger that runs *beneath* the OS using Intel VT-x. Hidden hooks, TLB splitting, EPT-based monitoring: reverse engineering's secret weapon. Debuggers 3301: HyperDbg ost2.fyi/Dbg3301 by @Intel80x86
HyperDbg retweeted
Slides and recordings for our @FOSDEM talks are up! Join an in-depth introduction into @HyperDbg 's features and internals, or find out what's the latest in anti-anti-debugging techniques and HV transparency for malware reversing:
fosdem.org/2026/schedule/eve…
fosdem.org/2026/schedule/eve…
HyperDbg retweeted
Curious about anti-anti-debugging techniques and hiding hypervisors from malware? Or simply looking for an in-depth introduction to @HyperDbg? Join @Intel80x86 and my @FOSDEM talks tomorrow:
fosdem.org/2026/schedule/eve…
fosdem.org/2026/schedule/eve…
HyperDbg retweeted
Our paper "TRM: The Reversing Machine" has been accepted to @asiaccs2026!
TRM is developed on top of @HyperDbg and exposes stealthy sub-OS malware using transparent hypervisor introspection, detecting threats missed by 24 AV engines.
Preprint arxiv.org/abs/2405.00298
@Intel80x86
HyperDbg retweeted
We have received reports @HyperDbg's latest release shows unexpected behavior. As it turns out, this is due to a compiler optimization bug in Visual Studio 17.14.8 and 17.14.9. We have pushed a temporary workaround fixing the build. Thanks for reporting! (1/2)
HyperDbg retweeted
I'm happy to announce that @HyperDbg v0.14 is released!
This version includes HyperEvade (beta preview), fixes Win11 24H2 compatibility issues, and adds multiple timing functions to the script engine (Special thanks to @0Xiphorus).
Check it out: github.com/HyperDbg/HyperDbg…
(1/3)
HyperDbg retweeted
Curious about anti-anti-debugging techniques and hiding hypervisors from malware? Slides are up for ECOOP/DEBT 2025 talk where we present HyperEvade, our upcoming hypervisor transparency extension for @HyperDbg : github.com/HyperDbg/slides/b… (1/2)
HyperDbg retweeted
We're excited to announce a major new release of x64dbg!
The main new feature is support for bitfields, enums and anonymous types, which allows all types in the Windows SDK to be represented and displayed 🔥
HyperDbg retweeted
🔥 TitanHide has been updated to support the latest VMProtect 3.9.4 changes!
The service name is now used as the device name as well, so the check for \\.\TitanHide will fail if you name the service differently 🧠




























