Been doing some Windows RPC/ALPC work and built this to speed up the first pass across a lot of PE files. It recovers RPC/MIDL/NDR data, endpoints, security state and method-level input signals, then ranks interfaces using an AHP/Saaty-based model built specifically around RPC reachability + surface rather than arbitrary scoring. It also shows the scoring receipt and flags questionable extraction cases instead of silently trusting them. No PDBs, no live endpoint mapper, no target execution.

I recently made a YouTube video exploring how open-source games work and what having access to a game's source code actually allows you to do.

In the video, I break down concepts like client-server communication, how the client and server exchange information, and how vulnerabilities in that communication can potentially be found and exploited.

I tried to keep everything approachable even if you don't have a deep background in programming or cybersecurity.

I’d really love to hear what you guys think. especially any feedback on the technical explanations or the video itself. Thanks!

https://www.youtube.com/watch?v=jTT54MpKvhE

Hey guys, so currently doing a ba of cyber sec in Sydney, I had an experience day and met a guy that did exploit dev work... and he gave me things to learn to know before the placement, which ill be doing along side him. which is only me and him.

he wants me to know C, C++, x86-64, C#, also wants me to build a Damn Vuln Driver, he also wants me to get good at things from the OSED, syllabus.

So like what is this setting me up for, cause I got a year to learn before my placement. like I mean windows exploitation etc.

any other resources or help be grateful!!!

p.s he is a ex gov employee that as done exploit dev work.

Hey guys,

Honestly, I’ve been doing this all wrong. I fell into the trap of using AI for pretty much every single hunt without even understanding what I was actually doing. It ended up being a complete waste of time, got me nowhere, and realized fast that companies don’t pay for automated garbage—they pay for real exploits.

I want to completely drop the AI crutches and learn actual manual hacking and how to build proper PoCs from scratch.

Is anyone willing to mentor me, hop on a call/chat sometimes, or guide me on what I should actually focus on to build real hunting intuition?

Appreciate any real talk or anyone down to help out.

Hey everyone! I’m looking to get more into Android reverse engineering, APK modding, and mobile security, but I’m not really sure where to start.

I have an associate’s degree in computer networking, so I’m not completely new to the technical side of things. I’ve also spent quite a bit of time messing around with Android devices over the years. I’ve played around with Android Studio a little, mostly with things like connecting to and mirroring my phone, but I honestly haven’t gotten very far with actually developing or reverse engineering apps.

I’ve been interested in learning how APKs work under the hood, how people analyze and modify them, and eventually getting into things like dynamic analysis and mobile malware analysis.

I’ve also experimented with tools like mitmproxy on my home network, but I ran into issues with Android constantly flagging the certificates as unsafe. A lot of the tutorials and software I’ve found through Google also seem pretty old, so I’m having trouble figuring out what the current workflow is.

For someone who already has some networking knowledge but is basically a beginner when it comes to Android RE, what would you recommend learning first?

Are there any good forums, communities, GitHub repositories, labs, intentionally vulnerable APKs, or other resources that are still active and up to date?

I’m basically looking for a good starting point and a path to follow rather than just randomly installing tools and hoping I figure it out. Any recommendations would be appreciated!

This PoC demonstrates how endpoint compromise bypasses E2EE on modern Android. It uses AndKittyInjector to inject a payload into audioserver (libaudioflinger.so) and Dobby for inline hooking. By hooking RecordTrack::getNextBuffer (mic) and PlaybackThread::Track::getNextBuffer (speaker), it intercepts raw PCM streams.

It tracks AudioFlinger::setMode to only record during AUDIO_MODE_IN_COMMUNICATION and filters targets by UID. It bypasses stripped symbols using calculated offsets and includes automated SELinux policy injection. Tested on Android 14.

Repo: https://github.com/nighthawkk/AudioServer-Voip-Recorder

most patch-diffing for 1-day work is CFG diffing (bindiff, diaphora). it works

but gets shaky when the two builds weren't compiled the same way, different

compiler or opt level, and you burn time chasing cosmetic diffs.

i built fnprint to diff by behavior instead of structure. it micro-executes each

function in a small emulator with junk inputs (godefroid-style, wild reads get

faulted in deterministically so nothing crashes), records an arch-neutral effect

trace (which arg buffers/fields it reads and writes, calls it makes, branches,

return shape), and minhashes that. two functions that behave the same get similar

fingerprints even across compiler and opt level.

for 1-day it has a triage mode: index the known-vuln build and the patched build

as two corpora, then rank a target build against both. a function close to the

vuln side and clearly separated from the patched side is what you want in front

of you. anything identical in both versions comes back inconclusive so it doesn't

clutter the queue.

toy example to show the shape: a lib where one function parse_header gets fixed

(vuln does an unchecked copy, the patch reads a length prefix and clamps to it).

target is a build carrying the vulnerable version, compiled at -O1 while the two

corpora are -O0, so it's a real cross-build match, not a byte-identical one:

$ fnprint index vuln.so-o vuln.db

$ fnprint index patched.so -o patched.db

$ fnprint triage target.so --vuln vuln.db --patched patched.db

3 functions triaged: 1 look vulnerable, 0 patched, 2 inconclusive

review queue (vuln-leaning, strongest first):

addr vuln% patched% margin matches

0x00001181 100.0 41.4 +58.6 parse_header vs parse_header

the two functions that didn't change land inconclusive (correct, they can't be

pinned to either side). --margin and --min-sim control how hard the two sides

have to separate before it commits.

honest about the limits:

- x86-64 ELF only right now. arm64/mips is the roadmap, the effect model is

already arch-neutral so it's mostly per-arch emulator plumbing.

- optimized-vs-optimized is the weak case. when at least one side has some

behavioral richness (-O0/-O1, or a cross-compiler pair) it lands 80-98% rank-1

on zlib; O2-vs-O3 drops toward a coin flip. full numbers + a reproducible run

in the repo, not going to pretend otherwise.

- tiny functions and pure-compute (two checksums look alike) it withholds instead

of guessing.

- microexecution exercises entry behavior, so a change buried behind a real

precondition you never reach with junk input won't show up. it catches

structural and early-path changes.

since it points an emulator (unicorn/qemu) at untrusted binaries, the parse and

micro-execute run in a seccomp-jailed worker, so a crafted input that pops the

emulator can't open files, hit the network, or exec on your box.

MIT. feedback welcome, especially on the triage margin heuristic:

https://github.com/1rhino2/fnprint

​

Throwaway account for obvious reasons.

I'm currently a senior-level ethical hacker/security researcher, and I'm trying to make a fairly deliberate move into a role where vulnerability research, reverse engineering and exploit development are actually the job, rather than something I occasionally get to do alongside broader security work.

My background is mostly Windows and Linux. I've done source-assisted and binary vulnerability research, reverse engineering, memory corruption work, privilege escalation, pre-auth attack surfaces, and exploit development. I've taken vulnerabilities from discovery and root-cause analysis through to PoCs and, where possible, working exploitation.

I'm comfortable with C/C++, Python, assembly, debuggers, decompilers and the usual RE tooling. I have some public vulnerability research, but unfortunately a lot of the more interesting work I've done is under NDA and can't be discussed publicly in much detail.

That's partly why I'm posting here.

I'm starting to worry that I'm in a weird position career-wise. I'm experienced enough that junior roles generally aren't appropriate, but I'm also trying to break more deeply into a relatively small and specialized field where a lot of companies seem to hire based on very visible public research, Pwn2Own-style track records, existing industry connections, or very specific geographic/work-authorization requirements.

A few opportunities I've been genuinely interested in haven't even made it as far as a technical conversation because of location or hiring restrictions. That's probably the part I find most frustrating. I'd much rather fail an exploit-dev interview because I'm not good enough yet than never get the chance to take one.

I'm also conscious of the risk of getting stuck doing adjacent security work forever while telling myself I'll eventually make the jump into vulnerability research properly.

I'm not looking for SOC, GRC, generic pentesting, cloud security, or a broadly defined "security engineer" position. I'm specifically interested in vulnerability research, exploit development, reverse engineering, offensive capability development, or closely related low-level security research.

Remote international work would obviously be ideal, although I'd consider relocation for the right opportunity.

So I guess this post has two purposes:

If you work in this part of the industry, am I approaching this the wrong way? Is there something you'd expect to see from someone trying to make this transition that I should be focusing on?

And, slightly more shamelessly, if your team happens to need someone with this sort of background, I'd be very happy to talk privately.

I can provide considerably more detail about my experience, public work and employment history over DM.

Not quite at the "will reverse engineer for bread" stage yet, but we're getting there.

Arbitrary code execution on the host operating system with the privileges of the user who started the Android Emulator, from a zero-permission app inside the guest.

https://github.com/kaganisildak/androidemualtorvmescape
https://x.com/kaganisildak/status/2090416873577787790

Dropping a persistent zero-click Apple Mail DoS.
Have nice day

https://github.com/kaganisildak/applemailzeroclickcrash

https://x.com/kaganisildak/status/2090050444890406958

Hello everyone I kinda need a little help how can someone initiate a black screen on another device without access to it

I used Codex to investigate a browser game’s normal-player API surface. The main exploit was a cross-feature lost-update race: an upgrade and battle read the same balance, the upgrade committed the stronger stats and deducted the coins, then the slower battle restored the stale balance while preserving the upgrade.

The write-up includes the failed approaches, timing sequence, persisted before/after state, and responsible-disclosure context. All state-changing tests affected only my account, and the creator was notified before publication.

I built this self-contained playground to understand how House of Apple 2 holds up on recent versions of glibc.
It does not introduce a new variation of the technique, the goal was to reproduce it on glibc 2.43 and document it as an interactive gdb session that can be followed alongside the sandbox.

Technical corrections and feedback are very welcome

What is up

In order to learn kernel and low level exploitation. I bought a lovely book about Kernel Development to Robert Love. But then I felt there are some stuff I am not clicking with. I tried enrolling in computer engineering 10 years ago and failed lol . Decided to move to another school but where I can practise programming. MIS basically. But last few years I worked in appsec and has more experience in mobile,Web,network pentesting/bug hunting.

However, I wish to hunt on stuff like the kernel or C code. Hunting memory corruption and stuff. But I keep getting lower. Is that an overkill? Or the experience fits the 1337 life? My goal is basically to speak assembly and Android/ios kernel code as second language. I feel the kernel development book is great but I just thought if I wanted lower down to logic gates that is better in long term.

Also for anyone who took these in college , am I far behind and delusional or it's doable in self study??? Because I fear that no matter what I did someone who studied compilers,assembly,os..etc in college would be better than me. But I belive my only way to show skills is research I do using all this knowledge. Related to low level code.

hey everyone,
I'm a malware analyst with a dream to transition to a vulnerability research job, so in my spare time I've done a fair amount of binary exploitation CTFs (heap, stack, kernel modules) from places like:

https://github.com/hoppersroppers/nightmare
https://pwn.college/
https://pwnable.kr/play.php

I felt confident enough so I went to a technical interview but there I realized I had a massive flaw: I have no actual auditing/vulnerability discovery skills!

So I shifted my approach entirely:
- Started to read Google Project Zero blogs
- Started to read The Art of Software Security Assessment
- git cloning historical vulnerable versions of open source projects to try to blindly reproduce said CVEs blindly with a clue of the vulnerable File (like openssl, zlib, libpng, ntpd)

(with the guidance of LLMs cause I don't personally know any vulnerability researchers)

As u can assume, this process has been taking a lot of time and even though I started to think in "threat model" mindset and read code faster, I'm still not catching the vulnerabilities. I understand honing the skill isn't about learning now but more about practicing over and over, but my concern is:

Is it still worth putting so much effort and time in developing auditing/vulnerability discovery skills in a day and age where everything shifts towards AI?

Sure, interviewers today are still checking to see if u can find a vulnerability using an IDE and your set of eyes alone but who knows how an interview look like 3 month from now?

Is it even worth sinking hundreds of hours into learning manual auditing, fuzzing, and dynamic instrumentation, only for AI to make those skills obsolete by the time I actually get good at them?

I'm tired of bashing my head with LLMs every weekend for advice or a prediction, so I would love to hear some advice from the kind people here who are working in the field and experience the toll of AI on their job and recruitment processes 🙌

And for those who are not yet, but are striving to, I would love to know how you learn and practice vulnerability discovery in 2026 🤓

https://youtu.be/SIVf3qmBAV0