Muhammed Yıldız
vulnerability research & reverse engineering
I take software apart to find where its assumptions break. Most of that time goes to native code on Windows: reversing binaries, mapping attack surface, and turning “this looks wrong” into a reproducible bug.
Computer engineering student. Everything here is written in public: research write-ups when a finding is worth the long form, notes when it is not.
- focus
- memory safety · binary exploitation · reverse engineering · malware analysis
- tooling
- IDA · x64dbg · WinDbg · Ghidra · Python · YARA
- location
- Turkey
- elsewhere
- mail/github/x/discord
- 2025-03-18RedLine Stealer v5 — Credential Harvesting via Fake Software Installers
Static and dynamic breakdown of a ConfuserEx-packed RedLine build distributed as a cracked installer: config extraction, exfiltration path, and indicators.
- 2026-04-17DawgCTF - Data Needs Splitting Write-up
I loved this question and wanted to make a write-up, from queryig TXT Records to Reverse Engineering .jar file
- 2025-03-01Setting Up a Malware Analysis Lab on a Budget
How I built an isolated analysis environment using free tools and a spare machine — no expensive licenses needed.
Automated triage feed. Samples pulled daily, scored without a human in the loop.
| 2026-08-03 | 000f85d150af662ada1c4e92… | suspicious | 95% |
| 2026-08-03 | 022a8f905615a6a98f5a9d8e… | suspicious | 95% |
| 2026-08-03 | 0a50174b6ef5b50a5d26fd07… | suspicious | 95% |
| 2026-08-03 | 0cc87edf5dd17fe02cb5fa89… | suspicious | 95% |
| 2026-08-03 | 0ce366b7463e6b3c9d389d1c… | suspicious | 95% |
I am a computer engineering student working toward vulnerability research full time. That means a lot of hours in a disassembler, a lot of crashes that turn out to be nothing, and occasionally one that does not.
My background is in malware analysis, which is where I learned to read compiler output and stop trusting file formats. The interest has since shifted from what did this sample do to why did this code let it. Memory corruption, parser bugs, and the seams between trust boundaries.
If you have a target worth looking at, a bug you want a second pair of eyes on, or you just want to argue about heap grooming, write to 0xblackrose@proton.me.
- reading
- Windows kernel internals, allocator behaviour, published root-cause analyses
- building
- fuzzing harnesses and small triage tooling
- practising
- CTF reversing and pwn, one category at a time
- next
- a first CVE worth writing up properly