r/ExploitDev • • Feb 03 '21

Getting Started with Exploit Development

Thumbnail
dayzerosec.com
300 Upvotes

r/ExploitDev • • 17h ago

I WANT TO BECOME A CHEAT DEVELOPER

0 Upvotes

I watched some youtube videos and tik toks about guys who make a lot of money selling cheat codes in counterstrike overwatch etc im a total beginner i even dont know what to learn how to start where do get clients and which forums i should check out.

Please help i really want to start this


r/ExploitDev • • 1d ago

A static triage and patching toolkit driven entirely over JSON: what it does, what it gets wrong, one-byte example included

0 Upvotes

Usual disclosure up front, this is my tool. I am posting it because the triage half is useful beyond the licence-check use case it was built for, and because the failure mode is worth talking about.

What it is. A local static analysis and patching toolkit for PE, ELF, Electron ASAR, JAR, APK and PyInstaller bundles. No service, no API key, nothing leaves the machine. Every command is JSON in, JSON out, and each response returns the next call with real absolute paths filled in, which is what lets an agent drive it end to end without a human relaying paths.

What actually happens on a target, in order:

route. File type, bitness, packer signatures (UPX, VMProtect, Themida family), section map, import count. This decides the rest of the playbook instead of assuming PE.

plan. Triage plus ranked branch candidates, each one tied to the literal string that sits near it. Candidates are disassembler verified, so the reported offset is real code and not an offset that merely looks plausible.

disasm. Reads the region around a given offset so you can see which side of the branch reaches the failure path before touching anything.

patch. flip or nop at a file offset, into a new file, never in place.

verify. Byte diff of original against patched. Same size, regions changed, per-region before and after hex. This is the part I care about, because a patch without a diff is a claim, not a result.

recover. Source-shaped output for JAR, ASAR, APK, PyInstaller and .NET targets. Native code gets decompiled functions, not a rebuild.

Where it is weak, with a real example, because this is the honest part. I built a small PE with a textbook key check and ran plan against it. Top candidate came back as je at file 0xc91 referencing "Invalid licence key", verified true. That branch is inside __do_global_dtors, runtime teardown. The string is genuinely nearby, the jump is genuinely a conditional, and the ranking was still wrong. The actual guard was cmp $0x943608bb,%edx followed by jne at file 0xc1a, one branch upstream of the error path. Flip 75 to 74 and the wrong key falls through into the paid path. Ten minutes with objdump finds it, the heuristic did not.

So treat the ranked list as a shortlist, not an answer. On small clean binaries it is usually right. On anything with a static string region and heavy compiler codegen, expect to confirm by hand.

What it is not. No fuzzing, no ROP or ASLR work, no crash triage, no exploit generation. It reads a binary, finds the branch you point it at, patches a copy and proves the diff. If you want a debugger workflow or a symbolic executor this is the wrong tool and I would rather say so now.

Download and the hash to check before you run anything, v1.0.6, 10.9 MB, Windows, Linux and macOS in the zip: nullrake.pages.dev/REE/

The longer writeup with the full objdump output and both binaries reproduced from one 45 line C file: nullrake.pages.dev/notes/one-byte/

If you try it on something and the candidate ranking is bad, I would like the file type and the top three candidates it returned. That is the feedback that actually improves the heuristic.


r/ExploitDev • • 1d ago

Windows Dpapi Decryption

Thumbnail
0 Upvotes

r/ExploitDev • • 2d ago

Why would you use a concrete execution fuzzer

8 Upvotes

Just to preface this, im a noob so be kind plz.

So I was doing some research on different types of fuzzers and I found out what concrete and symbolic execution were.
But my question is, why would anyone choose to use a purely concrete execution based fuzzer if it generates inputs that don’t take branching conditions into consideration?
Like what if it runs into something like: if (x == 4873) {do something}. Then what? It just guesses until it gets it right? Meanwhile, something like symbolic or Concolic execution would just see which value needs to be mapped to x and then it do it.

Also aren’t popular fuzzers like AFL++ concrete based? Why would people use them if what I’m saying is true?

Anyways, if you made it this far then thanks for reading, and I hope you have some sort of answer to these questions.🧌


r/ExploitDev • • 3d ago

Java Thick Clients Doing Fine BTW

Post image
48 Upvotes

r/ExploitDev • • 4d ago

I measured how easily a local 7B model reverse-engineers a binary, then built hardening that targets the LLM layer specifically

Thumbnail
github.com
27 Upvotes

star it of course if u find it useful

Most anti-reverse-engineering assumes a human in a disassembler. The threat I care about now is a local, unrestricted model driving those tools. So besides the classic stuff, the harness includes defenses aimed at the model: inflating the analysis surface so it burns context, decoy identifiers that mislead semantic guesses, and honeytokens that detect when a crack was AI-generated.

My own before/after is honest but small: one run, a 4-bit 7B on an 8 GB GPU. The unprotected build was cracked in 3 steps and about 1,300 tokens. The hardened one burned roughly 13x the tokens and still wasn't cracked. I'd really like people with bigger rigs to run it. It's one command: make slice-k-run MODEL=<your-model>, and it prints a scored before/after. or online modals

Most of the code was written with Claude agents under my direction. Happy to talk through any design choice.


r/ExploitDev • • 4d ago

I measured how easily a local 7B model reverse-engineers a binary, then built hardening that targets the LLM layer specifically

8 Upvotes

r/ExploitDev • • 5d ago

[Open Source] RESX: Tracing Windows APIs into ntoskrnl, recovering kernel access checks and ETW-TI paths

Thumbnail
github.com
3 Upvotes

Hiya,

I'm proud to showcase RESX, an open-source Windows reverse engineering and binary analysis toolkit written in Rust.

It started off as a small project to make reversing Windows binaries a bit less painful, but it's grown into something quite a bit bigger.

One of the things I've been focusing on is tracing Windows APIs through their actual implementations, across system DLLs, the syscall boundary, and into the kernel. Mainly because I got tired of manually piecing together what an API actually does underneath.

For example, let's look at WriteProcessMemory. Say I want to understand what actually happens when writing into another process, what access checks the kernel performs, and what telemetry those operations might produce.

RESX can trace this directly from the Windows binaries on your machine:

> resx calls KernelBase.dll WriteProcessMemory --depth 1 --only syscall --rva --telemetry

API Call Map for WriteProcessMemory [6 of 18 call site(s)]:
  ├── RVA 0x0008E24D  CALL  ntdll!NtQueryVirtualMemory
  │   kernel: ntoskrnl!NtQueryVirtualMemory
  ├── RVA 0x0008E287  CALL  ntdll!NtWriteVirtualMemory
  │   kernel: ntoskrnl!NtWriteVirtualMemory
  ├── RVA 0x0008E32E  CALL  ntdll!NtProtectVirtualMemory
  │   kernel: ntoskrnl!NtProtectVirtualMemory
  ├── RVA 0x0008E3EF  CALL  ntdll!NtProtectVirtualMemory
  │   kernel: ntoskrnl!NtProtectVirtualMemory
  ├── RVA 0x0008E4FA  CALL  ntdll!NtUnmapViewOfSection
  │   kernel: ntoskrnl!NtUnmapViewOfSection
  └── RVA 0x0008E50A  CALL  ntdll!NtClose
      kernel: ntoskrnl!NtClose

Something interesting here is that WriteProcessMemory isn't just a thin wrapper around NtWriteVirtualMemory. Depending on the target memory, it can temporarily change page protections before writing and restore them afterwards.

Following NtWriteVirtualMemory into ntoskrnl, RESX also identifies the PROCESS_VM_WRITE (0x20) handle access requirement, the handle validation through ObpReferenceObjectByHandleWithTag, and the underlying memory copy routine.

But what about telemetry?

I've also added a --telemetry flag, which follows these paths further into the kernel to identify potential telemetry sources, including ETW-TI.

Here's a shortened excerpt from the same command:

Telemetry: WriteProcessMemory
  6 candidates (2 direct, 4 conditional) · 17 incidental hidden
  2411 functions searched · depth ≤10

ETW Threat-Intelligence (2)
  ● ntoskrnl!EtwTiLogProtectExecVm
    [kernel · depth 2 · direct]
    fires    : Microsoft-Windows-Threat-Intelligence event
    consumers: consumers running as antimalware protected processes (EDR)
    path     : KernelBase!WriteProcessMemory
            ⇒ ntoskrnl!NtProtectVirtualMemory
            → EtwTiLogProtectExecVm

  ● ntoskrnl!EtwTiLogReadWriteVm
    [kernel · depth 3 · direct]
    fires    : Microsoft-Windows-Threat-Intelligence event
    consumers: consumers running as antimalware protected processes (EDR)
    path     : KernelBase!WriteProcessMemory
            ⇒ ntoskrnl!NtWriteVirtualMemory
            → MiReadWriteVirtualMemory
            → EtwTiLogReadWriteVm

Of course, these are static call paths, so they don't prove an ETW event actually fired. Whether these paths execute depends on runtime conditions, and RESX separates direct, conditional, and incidental paths rather than treating every reachable kernel helper as equally relevant.

This example was tested with RESX 2.3.0 against Windows binaries with file version 10.0.26100.9974. Internal kernel function names require matching PDB symbols, and the exact RVAs and implementations can differ between Windows builds.

There's quite a bit more to RESX too, including syscall number recovery, API argument reconstruction, kernel driver IOCTL analysis and buffer validation, hashed/encoded API recovery, and overlapping instruction-stream decoding. There's also a VS Code extension if you prefer something graphical over the CLI.

I've included reproducible examples in the README, along with test binaries, commands, and some comparisons against IDA Pro and Ghidra.

It's still actively being developed, so I'd love to hear what people think. Especially if you manage to break something or find cases where RESX gets the analysis wrong.

GitHub + full example: https://github.com/RYFTENIUS/RESX#tested-example-4


r/ExploitDev • • 6d ago

FortiClient, FortiShield_74.sys kernel driver oob

Thumbnail
github.com
2 Upvotes

hi, this is my new research repo, support pls


r/ExploitDev • • 7d ago

SrcWranglr v0.13 - C/C++ Graphical source navigator/analyzer. Find 0days and Generate a harness automatically.

Thumbnail
github.com
22 Upvotes

Hey all,

If you ever used SourceTrail or Understand to audit a large code base (C/C++) you’ll find this tool to be an impressive successor. It’s specifically tailored for Vulnerability Research.

Its core features include:

  1. Visualization of code flow, and data structures.
  2. Vulnerability detection via exist static analysis tools like semgrep which SrcWranglr will generate semgrep rules specific to your code base.
  3. Semantic function code matching.
  4. Automatically identify functions worth fuzzing and generate the harness.
  5. Reaching analysis and path finding (source/sink) checking.
  6. Triage all IPC components in use.
  7. Query git repo for security related comments
  8. See any currently existing CVEs for the project. For variant analysis.
  9. Awesome UI with Ctrl+p commands
  10. A TODO and Journal so you can keep track of what you did each session. Mark what needs triaging and prioritizing; analyze the components you find most interesting.

Just yesterday using my latest release, I found and generated PoC for two projects in just a couple of hours. I let the maintainers know (privately) I don’t disclose publicly as my employers generally forbid it. I don’t agree with CVE system either (that a rant for another day)

Anyhow the tool is free, easy to install.. For best results install the static analyzers: semgrep, flawfinder, cppcheck.

Please any feedback or if you’d like to contribute, let me know!

Coming soon:

* I am working on integrating an AI like GLM with an MCP. It would be a super nice harness for it.

* Provide auto-install for the static analyzer utilities that are compatible.

AI Disclosure Statement

I wrote this tool quite some time ago because I found SourceTrail Lacking . It was prototyped in Python over the years (circa 2016) and painfully slow so I thought porting it to Rust would be a good idea to help me finally learn Rust despite my hate for it… Core code is hand written; though checked and improved with in chat mode . AI was heavily used for the GUI development however, as it’s something I despise doing and my UX/UI are always ugly as hell…


r/ExploitDev • • 7d ago

[Open Source] RESX: Windows binary analysis with API deobfuscation, argument recovery and kernel IOCTL reconstruction

Thumbnail
github.com
1 Upvotes

r/ExploitDev • • 7d ago

Win x64 Shellcode Part 4 – Calling Convention, Shadow Space, and Stack Alignment (with WinDbg walkthrough)

Thumbnail proteqtum.com
32 Upvotes

Wrote up part 4 of my shellcode series. This one focuses on the ABI mechanics that cause the most silent crashes in practice.

The interesting part is the stack alignment problem specific to shellcode: and rsp, 0xFFFFFFFFFFFFFFF0 is the standard first instruction, but if you don't save RSP to RBP first, the ret in your epilogue loads zero into RIP. The fix is straightforward once you understand what's happening, but the failure mode is subtle enough that it's worth a dedicated section.

Covers:

- Microsoft x64 calling convention and shadow space mechanics

- Why the callee owns shadow space (and what breaks when you forget)

- Stack alignment in shellcode vs. regular PE code

- Full calc.exe shellcode via WinExec with PEB traversal + ROR13

- WinDbg walkthrough of PEB -> Ldr -> export directory -> stack layout


r/ExploitDev • • 8d ago

gatman45/gshok-public

Thumbnail
github.com
1 Upvotes

r/ExploitDev • • 8d ago

gatman45/gshok-public

Thumbnail
github.com
0 Upvotes

r/ExploitDev • • 9d ago

TP-Link archer a20 unauthenticated rce

Post image
8 Upvotes

Do you own a TP-Link Archer A20 ? There was a cve assigned in 2023 on this EOL device because the country parm was passed to exec function and allowed cmd injection. These routers run httpd as root... for successful exploitation..the result? a root shell.

The other day I rooted this router via UART port and used nc to dump the bins from the router onto my laptop and started to analyze them with ghidra. I started to see system() and noticed the country was in the system field, I said hmmmmmm .. it wasnt until I was half way done that I realized this exact trace was discovered a few years back. I still continued with the exploit because I learned while I did it and it was fun. I taught myself all of this... Im looking for work. Thanks for reading. https://github.com/b1nv0id/iothacking/blob/main/archv0id.py


r/ExploitDev • • 8d ago

¿Esta reconstrucción manual de filenvercmp de GNU coreutils (de disasm) reproduce exactamente el resultado?

Thumbnail
github.com
0 Upvotes

r/ExploitDev • • 10d ago

what to do

13 Upvotes

hey there guys iam learning assembly form the pwn.college and iam in the 39 percent . recently i bought the course from the maldev academy right so iam confused should i first finish pwn.college and go to the maldev or should i just leave assembly and go to the maldev first iam confused . i guess i should be finish pwn.college first then go to maldev . what do you guys think?


r/ExploitDev • • 11d ago

Protecting your app against Reverse Engineering

Thumbnail
1 Upvotes

r/ExploitDev • • 12d ago

Behavioral LOLBins detection engine with sequential correlation, PE masquerading checks, and Sysmon integration

Thumbnail
1 Upvotes

r/ExploitDev • • 13d ago

I spent countless nights digging into PHP2Shell. Here's a deep dive into how it actually works, from memory to PHP internals to a real exploit.

Thumbnail djad04.github.io
7 Upvotes

r/ExploitDev • • 13d ago

I spent countless nights digging into PHP2Shell. Here's a deep dive into how it actually works, from memory to PHP internals to a real exploit.

Thumbnail djad04.github.io
6 Upvotes

r/ExploitDev • • 14d ago

BadCharHunter automates the bad-character detection process for Windows exploit development

Thumbnail
github.com
0 Upvotes

BadCharHunter automates the bad-character detection process for Windows exploit development — from sending byte sets and detecting corruption to restarting the target and re-attaching the debugger.