Thread hijack
The entry point runs on a thread opened inside RobloxPlayerBeta.exe. No CreateRemoteThread, no APC queue, no loader lock in your own process.
A driverless x64 loader for Roblox. The client opens the target, reserves a region inside a signed Microsoft module, maps your DLL by hand and starts its entry through a hijacked thread. No kernel driver, no service, no file written into the game folder. Five pages and one demo module that draws a watermark over the window.
The chain opens the target once, validates the file, reserves the stomp region and maps the image. Any failure stops before the next write.
The entry point runs on a thread opened inside RobloxPlayerBeta.exe. No CreateRemoteThread, no APC queue, no loader lock in your own process.
A signed Microsoft module is loaded into the target to reserve a region with the right size and protection. d3d10warp.dll is the default; mshtml.dll gives more room for large images.
Read, write, protect and allocate go through resolved Nt* routines, not the Win32 wrappers. The loader carries its own syscall numbers and context.
DOS signature, PE signature, machine AMD64, IMAGE_FILE_DLL, section table and image size are checked before a byte enters the target.
CounTroubleModule.dll creates a topmost, click-through watermark over the Roblox window. It lives twelve seconds, paints the Countrouble mark and destroys itself. Nothing is persisted.
Dashboard, injection, target, log, about. The dashboard shows the live chain; the target page reads PID and RobloxPlayerBeta.dll base every two seconds.
Captured from the demo build at 1160×760 — sample target, injection disabled, same widgets.
The dashboard refreshes the process every two seconds, reads the module base and validates the selected file before the inject button is armed. Nothing is opened until you press it.
One executable and one demo DLL, static CRT, no service left behind. The module is mapped by hand: sections, imports, relocations, TLS and exception tables, then the entry runs on a hijacked thread.
Free zip, one exe, one demo DLL. The client needs an administrator token; Roblox has to be open.
Zip · 1.15 MB · Windows 11 / 10 x64 · Roblox running · administrator required.
A5E57DC5426A2AF1D7DB4233F6718E4DFDE8D739E0AFB3D4EADFC137F0247708Grab countrouble-client-2.0.0.zip and extract it to a folder you keep. It holds CounTroubleClient.exe, CounTroubleModule.dll and the readme.
Start Roblox and wait for the home screen. Run CounTroubleClient.exe and accept the UAC prompt. The dashboard should show the PID and the module base.
Open Injection or press Choisir une DLL and select CounTroubleModule.dll. The page reports architecture, file size and image size. Only x64 PE DLLs pass.
Press Injecter. The seven-stage chain runs: ntdll, process, handle, DLL, stomp, Roblox module, mapping. The demo watermark appears over the game for twelve seconds.
Current build is 2.0.0. The exe version and the zip name match.
No. The whole chain is user mode: direct ntdll calls, a handle, a stomp region and a manual map. There is no kernel driver, no service and no test-signing step.
The manifest requests elevation because OpenProcess needs full rights on the Roblox process. Without an elevated token the open fails and the chain stops at stage 03.
x64 PE files with the DLL flag and imports that resolve inside the target. Managed, packed or runtime-dependent images may fail at mapping. Large images can be tried with mshtml.dll as the stomp host.
It lives in the process memory until Roblox closes. No game file is patched and nothing is written to the Roblox folder. The demo module removes its own window after twelve seconds.
Close Roblox. The mapped image and the hijacked thread go with the process. The client keeps only settings.ini and journal.log under %LOCALAPPDATA%\CounTrouble\Client.
--demo fills the panel with sample values, disables DLL selection and injection, and never opens a handle. --page=N picks a page; --shot=path.bmp captures the backbuffer and exits.