๐ด๐ ๐๐๐๐๐๐ ๐ด๐ ๐ป๐๐โ๐๐๐๐ retweeted
Proper old-school hacker energy.
If you're into Windows internals, exploit development, malware memory or reverse engineering, Forrest Orr's (@_ForrestOrr) work is absolutely worth bookmarking.
The FREE archive covers:
- Windows memory corruption
- Stack overflows + ROP
- DEP, ASLR + CFG
- Shellcode development
- Windows internals
- Malware memory artifacts
- Phantom DLL Hollowing
- Process injection + hollowing
- Memory scanner evasion
- Moneta memory analysis
- PE internals
- Browser exploitation
- Chrome UAF exploitation
- Firefox / IE exploit chains
- Sandbox escapes
- Defensive memory analysis
And unlike a lot of modern security content, there are actual tools, PoCs, shellcode and exploit-development experiments to go with the research.
Blog:
forrest-orr.net/
ExploitDev repo:
github.com/forrest-orr/Exploโฆ
Some of this is older material, but that's part of what makes it good. Proper fundamentals and low-level research that still teaches you how the machinery actually works.
Huge credit to Forrest Orr (@_ForrestOrr) for keeping it publicly available.
#ExploitDevelopment #WindowsInternals #ReverseEngineering
๐ด๐ ๐๐๐๐๐๐ ๐ด๐ ๐ป๐๐โ๐๐๐๐ retweeted
TBH, Iโm sceptical about โhuman-onlyโ CTF boards when thereโs no reliable way to verify how people solve the tasks. As long as we reward speed, thereโs a strong incentive to use AI, and inevitably some will cheat. If we want to preserve the human challenge, we need to put more emphasis on learning, and less on who solved the fastest.
๐ด๐ ๐๐๐๐๐๐ ๐ด๐ ๐ป๐๐โ๐๐๐๐ retweeted
If you're learning Windows internals, malware analysis or reverse engineering, bookmark @vollragm 's FREE archive.
It goes from beginner-friendly reversing all the way into some seriously useful Windows internals:
GhostDebug: build a stealthier Windows debugger using VEH, then test it against common anti-debugging techniques, x64dbg and ScyllaHide.
LargePageDrivers: page tables, Windows kernel loading and executing code inside valid kernel modules.
PTView: visually browse live Windows page tables, PTEs and physical memory mappings.
KernelSharp: writing Windows kernel drivers in C# with NativeAOT.
Kernel-mode MessageBox: reversing the path from user32 through NtRaiseHardError and into the kernel.
Then there is Task Manager reversing, Windows 7 Minesweeper, Unity/.NET reversing and Web API reversing.
For malware analysts, the anti-debugging, exception handling, memory and kernel material is especially useful.
For reverse engineers and Windows internals people, there is a lot here to learn from.
FREE:
vollragm.github.io/
#WindowsInternals #ReverseEngineering #MalwareAnalysis
๐ด๐ ๐๐๐๐๐๐ ๐ด๐ ๐ป๐๐โ๐๐๐๐ retweeted
Replying to @NahamSec
Pick a niche, become an expert, find bugs maybe even 0days or reverse n-days, and write blogs. Even if you donโt hit those $100k bounties, itโll be a stepping stone toward a $100k job.
What niche? How to pick? Examples?
infosec being so vast from web3 sec to web2, mobile, desktop, recon, client-side, server-side, cryptography and so on. These are umbrella terms, but if we zoom in, there are specific areas where spending a lot of focused time will make you a top 20 expert -- 100% sure.
The key thing is, that the current top 20 experts in any niche will eventually be replaced as they get bored or burned out. This leaves room for you, and the easiest way to pick a niche is to learn from an existing expert in the niche, take inspiration, and grind to build on top of it.
1. For instance, I got into the client-side JS niche by following @terjanqโs work. From there, I went down even further to focus specifically on ElectronJS.
2. Another example: @rootxharsh and @iamnoooob their niche is in reversing n-days and finding new ones based on that knowledge. I donโt think anyone in India can compete with them on reversing n-days, writing blogs, and submitting findings to bounty programs.
3. And off the top of my head, @ajxchapman, from his tweets, seems to have a specific niche in V8 n-day exploits. I donโt think thereโs anyone else in the web security scene who can write V8 exploits ๐
.
4. Like @orange_8361 , pick a complex target and grind on it for months eventually uncovering mind-blowing findings.
5. Or, like @albinowax, choose a complex specification, such as HTTP, and find bugs from every aspect of it from top to bottom
(Sorry for tags xD)
I could list so many more people, but my point is this: if you look at the top bug bounty hunters or experts, thereโs a pattern. Their blogs or tweets consistently focus on a specific niche (or two) for years and years. No one ever becomes a pro in a night.
How to Become an Expert in a Specific Niche?
Spend a lot of time. Thereโs no shortcut. Follow the work of the expert you picked for inspiration, read their blogs, dive into the blogs they learned from, and explore everyone else in that specific niche. Solve CTFs and write about them.
For example, not to make it all about myself, but just as an example. Iโve read every blog from the people I listed as inspirations(blog.s1r1us.ninja/inspiratioโฆ) while learning client-side security.
If itโs taking time to understand, youโre likely on the right path. Thatโs where most people give up, so keep pushing. Just dedicating days to it will put you ahead of at least 100 others. Itโs that simple.
Expert = Spent Time ร IQ
Find Bugs or 0days, Reverse n-days, and "Write Blogs
Once youโre an expert, finding bugs will start to feel natural. But letโs be real, sometimes you might not get lucky. When that happens, reverse other n-days and write about it. I mean write about anything. Nothing gives you as much exposure as writing blogs: youโre helping others, plus youโre building a network that will eventually help you land a $100k job or $100k bounties.
๐ด๐ ๐๐๐๐๐๐ ๐ด๐ ๐ป๐๐โ๐๐๐๐ retweeted
New blog
Spent way too much time reverse engineering CrowdStrike Falcon.
Somewhere along the way, I found a bug. It's low and not practically exploitable... but a bug is a bug :)
Publishing soon
0xdbgman.github.io/posts/insโฆ
๐ด๐ ๐๐๐๐๐๐ ๐ด๐ ๐ป๐๐โ๐๐๐๐ retweeted
New blog post is up looking at how LLMs are making local EDR rulesets, YARA rules, and behavioral detections trivial to extract. This post focuses on how simple the harness can be. Buckle up h4xx0rs, the next few months are gonna get interesting! specterops.io/blog/2026/06/2โฆ
๐ด๐ ๐๐๐๐๐๐ ๐ด๐ ๐ป๐๐โ๐๐๐๐ retweeted
CVE-2021-31956 is a Windows kernel privilege escalation vulnerability in NTFS ("ntfs.sys") caused by an integer underflow while processing Extended Attributes (EA). The resulting paged pool corruption can be turned into arbitrary kernel read/write primitives.
What makes NCC Group's research particularly interesting is that it demonstrates exploitation without relying on the CVE-2021-31955 kernel address leak. Instead, it leverages the Windows Notification Framework (WNF) to build reliable exploitation primitives, making it an excellent study of NTFS internals, WNF, kernel pool corruption, and modern Windows exploit development.
๐ด๐ ๐๐๐๐๐๐ ๐ด๐ ๐ป๐๐โ๐๐๐๐ retweeted
Abusing GitLab CI runners as a C2 framework โ legitimate signed binary, 0 VT detections, outbound HTTPS only.
PoC + detection section (Wazuh/Sysmon + MITRE mapping) for blue teamers.
๐ vrls.ws/posts/abusing-gitlabโฆ
๐ด๐ ๐๐๐๐๐๐ ๐ด๐ ๐ป๐๐โ๐๐๐๐ retweeted
It's the bug of the month for June 2026! CVE-2026-45657 - A CVSS 9.8 vulnerability in Kernel that allows remote, unauthenticated code execution at SYSTEM without user interaction. Yikes!
๐ด๐ ๐๐๐๐๐๐ ๐ด๐ ๐ป๐๐โ๐๐๐๐ retweeted
Hi! I just published UNCanny, a small Windows research experiment around a new coercion primitive I found while digging through AppX and InstallService internals, with an LPE exploitation angle that comes from the same weird path.
Because of the limitation that comes with it (which is that Developer Mode needs to be enabled for unsigned loose-package registration) I decided to publish my notes anyway. it might still be helpful for someone digging into the same area, even if it is not something I would consider reliable or useful for your ops. Read more: github.com/0xHossam/UnCanny #redteam
๐ด๐ ๐๐๐๐๐๐ ๐ด๐ ๐ป๐๐โ๐๐๐๐ retweeted
exciting stuff from @JoshB96009544
github.com/0xjbb/ModuleStompโฆ
๐ด๐ ๐๐๐๐๐๐ ๐ด๐ ๐ป๐๐โ๐๐๐๐ retweeted
We are releasing Tracebit @x33fcon - a POC sensor aiming to fingerprint implants in memory
using only lowlevel runtime telemetry.
No signatures, no scanning. Only pagefaults.
github.com/threathunters-io/โฆ
๐ด๐ ๐๐๐๐๐๐ ๐ด๐ ๐ป๐๐โ๐๐๐๐ retweeted
This is kinda dope github.com/wesmar/KernelReseโฆ
@wesmarpl
๐ด๐ ๐๐๐๐๐๐ ๐ด๐ ๐ป๐๐โ๐๐๐๐ retweeted
CI/CDใฎใใณใในใใซ้ขใใ็ฅ่ญใคใใใใชใจๆใฃใฆ่ฏใๆๆใใชใใ่ชฟในใฆใใใCTFๅฝขๅผใงๅญฆในใcicd-goatใใฟใคใใ๐
Dockerไธใงๅใใฎใงใๆๅ
ใซDocker็ฐๅขใใใใฐใตใฏใใจ้ในใฆใใๆใใ
github.com/cider-security-reโฆ






































