v1.0-beta · CS2 build 2026-05-13
Read-only external overlay for Counter-Strike 2.
Pure mouse driven. Zero memory writes.
Process handle is opened with PROCESS_VM_READ +
QUERY_LIMITED_INFORMATION. There is literally no
write code path in the binary. Every active feature
(aimbot, trigger, bhop) goes through SendInput.
That means anti-cheat sees a normal process reading public memory regions. No injection, no module map mismatch, no hooked syscalls inside CS2.
Aim path is a cubic bezier curve with min-jerk easing, Fitts's-law timing and 1D coherent noise overlaid. Every lock generates a fresh curve with a small intentional overshoot at the end.
Not "smooth aim with a lerp". Different shape every shot, because that's how a wrist actually moves.
DirectX 11 + ImGui rendered into a layered transparent window
sitting on top of CS2. Marked
WDA_EXCLUDEFROMCAPTURE so OBS, ShadowPlay and
the Windows snip tool see nothing.
Watermark shows AETHER + K/HS/$ + FPS. Toggle from menu.
Most external "wallhacks" get caught not because of what they do but because of how they look on the way in. AETHER drops the obvious tells:
PROCESS_VM_WRITE against cs2.exe
even if they never write. We never request it.
NtReadVirtualMemory in the IAT. Functions
are looked up via PEB walk + FNV-1a hash. Static-string
scanners find nothing.
SetWindowDisplayAffinity(WDA_EXCLUDEFROMCAPTURE)
— your overlay does not appear in screenshots, OBS,
ShadowPlay, or the Windows snipping tool. Streaming is
safe.
We don't claim to be undetected forever. We claim to be the smallest, quietest read-only overlay you'll find — and to patch within hours when CS2 ships an offset shift.
Currently invite-only through the Discord. Free during the whole beta. Anyone who joins now gets the OG tier at 1.0 launch — permanent 50% off any subscription tier, no expiry.
#downloads opens — grab the build/bug — get OG faster
Maybe. AETHER is read-only and uses SendInput
for active features, which is the lowest-risk approach
available. There is no public-domain "guaranteed safe"
overlay for CS2 because Valve does not publish their
criteria. Use an alt. If you put your main on the line you
accepted the risk.
Because every cheat-ring with a team is also a cheat-ring with a leak surface. Nobody else has the source. Nobody else has the offsets. There is no support agent in another timezone re-uploading the binary to a Telegram channel for $5.
First draft of the listing was written with help from a language model and someone called it out, fairly. The actual code, offsets, render path and aim engine were hand-written. We rewrote the listing. We're not going to pretend we don't use tools — we just don't ship slop.
When the build is stable across two consecutive CS2 patches
with no critical bugs in #bug-reports for
seven days. Best estimate: 4–6 weeks from now. Beta
members get OG at launch and keep their seat.
No free tier. The cost of doing this safely is paying for a single developer to actually update the build the day a patch lands. Free overlays are free because nobody's paying for anyone to update them, which is why they all get caught.
No. Per-customer watermarks (HWID + canary strings) ship with 1.0 — leaked builds will trace back to whoever bought the seat. During the free beta the deterrent is community: leak = perma + #wall-of-shame + your Steam URL publicly listed.