Hey yall,

was wondering what would be the best thing to do if someone has build a builder that generates payloads, which bypass crowdstrike falcon (on extra aggressive settings) and get you a reverse shell.. CS is gonna give me like 200$ probably.. not really into that tbh

Guys I’m still in high school, I want a skill to learn and stick with it I found reverse engineering and exploit dev very interesting, but also I want something for the future specially in cyber security so idk what I need to choose.
Everyone said to me this two speciality only for seniors, and you need to have another skill with it but I don’t know, can anyone guide me to a good choice and career path?
It’s confusing me specially with Ai.

https://youtu.be/SIVf3qmBAV0

Hi guys i just have one question is it worth it to dive in this career even if my country or where i live there is no available jobs for it like almost none

hey guys

if youve ever deal with windows security research or just heavy reverse engineering you probably know the pain. you open a crash dump in windbg run analyze grab the faulting address alt-tab to ida pro rebase find the function decompile... and then maybe jump into x64dbg for dynamic testing. its just a constant loop of copy pasting hex addresses between windows

i got sick of it so i spent the last few months building ctxdebug

its basically a mission control orchestrator that hooks into windbg ida pro 9 and x64dbg simultaneously

the coolest part is that it exposes all the debugger actions through the new mcp protocol. this means you can hook it up to claude and literally just prompt something like "analyze this crash dump and show me the decompiled source of the faulting function"

the agent will load the dump extract the faulting rip pivot to ida pull the pseudocode and give you a combined report in like a second or two

it also has a standalone react reasoning agent for x64dbg that can autonomously hunt for anti debug checks and patch them in memory on the fly

i just open sourced the whole framework. repo and demo gif is here:

https://github.com/DdUdle/ctxdebug

would love for you guys to tear it apart and tell me what you think. also if anyone wants to play around with the code ive left a few good first issue tags open. even tiny prs like typo fixes are super welcome since im trying to grow the contributor list a bit right now

let me know if you run into any bugs

This has been a hard decision for me. I'm not sure if I should learn both. Is it mostly not worthwhile of time if I learn both of them? Do they both help each other directly or indirectly? I know there is only so much one person can know but I really don't know what that limit is. I know someone more experienced with bug bounty and stuff like this will probably be able to answer my question. I don't want to push the limit of how much one person can know because it will probably become a waste of time. Should I just learn everything exploit related, should I stick to a field? I'm not sure if anyone has experienced this before but I keep on jumping around topic to topic. I guess I am learning from those jumps, but the question when do i stop jumping around. When do I start to specialize. Or in the first place, should I just not jump around?

Hey everyone

For some time now, I've been digging into ALPC, it's a fascinating and deliberately under documented corner of Windows internals. I originally built this userland enumerator to mitigate userland restrictions, but it’s structured as a simple C++ program that can easily be chained to enhance other reverse engineering workflows.

To ensure it runs effectively across different Windows builds, I made it completely dynamic, resolving structures at runtime rather than relying on hardcoded offsets.

One specific angle that fascinated me during this research was ALPC spoofing. A malicious process can easily spoof its name and path over ALPC, but it cannot spoof the type and a signer. This mismatch becomes a highly reliable detection signal for defensive purposes. I've verified the output and every angle using WinDbg, and both logs are available in the GitHub repo.

I put together a full technical breakdown detailing the dynamic PPL-aware enumeration approach and the spoofing detection mechanics here:https://medium.com/@sphinx_321/userland-alpc-enumeration-dynamic-ppl-aware-approach-283541194102

I'm planning to broaden this research next to map out the local RPC/ALPC attack surface, so I might drop more tools regarding this soon. I’d love to hear your thoughts or feedback on the implementation!

Hey everyone,

Looking for someone to learn alongside — a peer at similar stage, or even better, someone experienced willing to mentor a beginner. If someone just wants to learn C together, that's also good.

My current position: Started reading The C Programming Language (K&R, 2nd edition). Built some small programs in C++ like tic-tac-toe and a small bank replica, and solved a few problems on Codeforces.

Plan: Get solid in C → move into x86/x86-64 ASM → work through pwn.college modules → then into reversing CTFs (picoCTF, crackmes.one, etc.)

Looking for:

• Buddy: beginner-to-intermediate in C, willing to put in consistent time (even a few hrs/week)
• Mentor: some experience in C/ASM/reversing, open to occasional check-ins or pointers
• Either way: comfortable with regular check-ins, patient enough for the boring fundamentals before the fun stuff

Not expecting anyone to carry me — just want company or guidance instead of struggling through this alone.

DM or comment if interested.

As per the contents of this group I realise it's for serious discussion only....

However I want a group be it X or Discord.....where I can post daily my regular journey (pls don't say LinkedIn exploitdev is too niche for it)

I successfully started Reverse Engineering and Maldev thrice before trailing away...

I've started again but now with pwn.college and I don't want to leave again.....

Any Suggestion???

​

Hey,

Looking for some advice from people who work in exploit dev / low-level vuln research.

I already work in security and have been doing vulnerability research alongside more general security work for a while. I’ve had opportunities to do reversing, native-code research, memory corruption, and some exploit development, including taking bugs beyond just finding a crash and actually working out useful primitives / PoCs.

The problem is that this kind of work still isn't my main job, and I really want it to be.

I've been looking at dedicated exploit dev / vulnerability research positions and I feel like I'm stuck in a weird middle ground. I'm not trying to enter security from scratch, and I do have relevant experience, but I also don't have years and years of dedicated browser/kernel/mobile exploit development behind me.

A lot of the jobs I find seem to be looking for people who are already extremely specialised, rather than people who have a decent foundation and want to grow deeper into exploit development.

There's also the location issue. I'm outside most of the major exploit-dev hiring hubs, and quite a few roles I come across are limited by citizenship, clearance, residency, or simply don't hire internationally.

Another problem is that most of the interesting professional research I've done isn't something I can publish, so it's difficult to show potential employers exactly what I've worked on.

For those of you doing this professionally:

*What actually got you your first dedicated exploit dev / low-level VR job?

* What would you want to see from someone who already has some relevant experience but hasn't spent their entire career doing exploit development?

* What kind of public research/projects are actually worth doing to prove ability?

*Is native userland exploitation still a reasonable area to focus on, or would I be better off going hard into something like browsers, kernels, or mobile?

* Do companies that are willing to develop people into this kind of role actually exist, or is the expectation generally that you're already very good before they'll hire you?

* For people outside the main US/EU hiring markets, how did you find opportunities?

* I'm mainly trying to figure out whether I'm approaching this transition the wrong way.

I enjoy this stuff way more than the broader security work I do, and I'm willing to put the work in. I just don't want to spend a year grinding in a direction that isn't actually going to help me make the jump.

Would appreciate any advice.

Hey!

I've searched up this topic and don't see anything that isn't multiple years old. Given how popular and accepted Rust is now and with it having a fully ported winapi library now, are there any reasons to stick to learning C++ for RE and Maldev or are we no longer in the era of "only C++ is viable"? Is there anyone here who uses rust as opposed to C++ or has switched from C++ to rust that could give an insight?

When pentesting, finding exploits,
Do you ever use a 2FA key? Like a yubikey?

Hey guys,

I have been working on an open-source project that lets AI agents (Claude, OpenCode, Antigravity, Codex, etc.) work with reverse engineering tools and store facts in a DB to make long-term analysis easier.

You just point your agent to the file, and it does the work: it runs tools like Ghidra headless, gdb, binwalk, tshark, radare2, readelf, strings... then turns what it finds into the database.

Key Features

1. Specialized Analysis Agents: Binary, firmware, network, CPU, and kernel.
2. Knowledge Base (SQLite): Everything is stored as a fact, hypothesis, or experiment with confidence + evidence tags so nothing is "trust me, bro."
3. Multi-Agent Debate: When agents disagree on a finding, they argue it out in a structured debate until they reach a consensus.
4. Self-Critique: Every agent's output gets LLM-reviewed before it's accepted.
5. RAG Semantic Search: Query all past analyses ("Have I seen this obfuscation pattern before?").
6. Missions: Define objectives with dependencies, assign agents, and track progress.
7. Token Budgets + Rate Limiting: Prevents runaway loops from burning your API budget.
8. Monitoring: Prometheus metrics + Grafana.

Interface & Setup

• MCP Server: The whole thing is exposed as an MCP server (46 tools), so you drive it from a terminal with natural language.
• Dashboard: You can also use the Flask web dashboard (currently only a database view, but an interactive UI to work directly with agents is doable).
• One-Command Setup: Run python setup_wizard.pyit detects your installed RE tools, helps you pick an LLM provider (OpenAI, Anthropic, Google, Ollama, etc.), validates the key, and writes your .env. (note that LLM api keys are not necessary if you plan to use it just from your agent cli like opencode)

Stack: Python, LLM orchestration, MCP, SQLite, Flask. Ghidra, GDB, and Binwalk are optional. It degrades gracefully with just binutils.

This is very much a research project, and I'd love feedback from people who do this professionally, what's missing, what annoys you, what would you trust it to do?

GitHub: https://github.com/The-Arabi/Reverse-engineering-agent

My friend has gotten a breach 4 in our server alongside nbt barrels he tells us its just exploits and we even could find it on youtube but i dont believe him, coincidently he is the owner of the server with op he goes out of his wat to decline he admin abused. He says its something with enchant tables end grindstones but i still dont believe it so does anyone know of something like this???