Robert Chen (@NotDeGhost) profile picture

founder @osec_io | web/pwn with @redpwnctf + @dicegangctf | prev @dfsec_com

Joined September 2018
Photo by Robert Chen (@NotDeGhost)Photo by Robert Chen (@NotDeGhost)Photo by Robert Chen (@NotDeGhost)Photo by Robert Chen (@NotDeGhost)Photo by Robert Chen (@NotDeGhost)Photo by Robert Chen (@NotDeGhost)Photo by Robert Chen (@NotDeGhost)Photo by Robert Chen (@NotDeGhost)Photo by Robert Chen (@NotDeGhost)Photo by Robert Chen (@NotDeGhost)
block the binance exploiter on your frontends!
The Binance hacker is depositing stolen $USDT on Aave and borrowing $ETH against it. He’s never paying it back. Doesn’t need to. USDT can be frozen by Tether. ETH can’t.
4
19
1,423
the binance hacker is hodling SOL
this would be the largest crypto hack in history by at least a multiple if confirmed actually might be the largest cyberattack in general for all internet regardless of crypto one silver lining is that binance is rich enough to make everyone whole
15
4
5
159
30,458
There's dozens of critical, latent vulnerabilities lying deep in the modern software stack This was one of the scariest ones yet, full compromise of bash, lp, cp, rm, and tons more.. Great work @S1r1u5_ and @HacktronAI!
What if you could backdoor Bash, ls, cp, rm, and other GNU software used by millions of systems? Our research led us to hack GNU Savannah, the infrastructure hosting their source code. The xz backdoor that never happened 🧵
1
33
2,115
the future of auditing
2
1
25
1,258
future of hacking = exploiting 1days in all your dependencies the internet is no longer for humans
The internet’s current security regime, which was built on the assumption that attackers are human, is obsolete in the face of AI. View article
3
1
51
2,848
i wonder how true this is. (without knowing any details) i would hope that exploitation of these bugs is super noisy, and Cathedral was only able to pull that chain off because they participated in an authorized bug bounty. but with all of the RL env escapes, it's a bit hard to believe that lab monitoring is particularly strong. especially around 3rd party dependencies maybe somebody from anthropic can comment..
fact check: even truer rumor is Cathedral got a lot of Slack, maybe all of research. what the fuck are we doing guys
1
15
1,521
thanks for the laptop @0xSigil!
All AI should be free, so I’m giving away the first RTX laptop for free, signed by NVIDIA Founder @UnderdogAI gives everyone a free, capable & private AI. 100% on-device To enter: 1) Retweet and like this post 2) Sign up for Underdog giveaway: underdog.ai/spark 3) follow @UnderdogAI so we can dm u
2
5
12
1,316
lots of noise with new CVEs. I hope we'll see more challenges like stealmybitcoin.com to prove how exploitable these issues are, especially with open models my sense is the nodejs brotli bug is an order of magnitude easier to exploit than php2shell. with cheap tokens, perhaps we can get a more insightful measure of exploitability. as opposed to just indexing off of CVSS rating..
php2shell is one of the most impactful bugs in recent times, yet threat actors aren’t mass exploiting it the bug is so complex that even porting the exploit between targets takes serious skill, human or ai so i benchmarked how well open and frontier models can do it. 🧵
4
3
43
3,569
once again hacker news is proven wrong. nice job @killa! crazy how even w/ such a bad challenge setup (initial deployment wasn't exploitable, tons of concurrent traffic, and surprise: the wallet was setup incorrectly), this was solved in a few hours
stealmybitcoin was just solved by @killa. Or rather solved a few hours ago. He was confused because the wallet address was wrong. Turns out the server didn't have the right wallet :P
5
7
2
146
16,870
if this was a real ctf challenge, I think you could see compromise by a determined hacker in < 1 hour. the CVEpocalypse is real
1
15
1,642
the future of hacking. good thing i was a CTF challenge author
My current LLM cyber jailbreak is to just spin up a local CTFD instance and write up challenges with the things I want hacked, and then point the hermes at it.
6
3
1
248
13,381
i was surprised at how exploitable this was. the primitive is quite good (arb offset, arb write), nodejs has no-pie, heap offset to tcache chunk is deterministic so its easy to convert could've been a hard ctf challenge 1-2 years ago. anybody who has done heap pwn could probably do this with open models..
100% reliability nodejs brotli exploit takes 5 hours of /goal. No human involvement required
3
7
160
13,158
100% reliability nodejs brotli exploit takes 5 hours of /goal. No human involvement required
I'll be the first to admit I'm mediocre at exploit development, but I am in contact with enough extremely talented exploit developers to say this for certain: Anyone claiming they were "easily" able to generate a working php2shell exploit with AI is either: a) a world-class exploit developer with an extreme case of imposter syndrome. b) currently looking at some very confident-sounding but wrong LLM output. I'm rather certain it's the latter based on the number of AI-hallucinated exploits I've seen posted on GitHub. Threat actors are also blasting my honeypot network with "php2shell" exploits that not only don't work, but aren't even within 10,000 miles of anything to do with how the exploit actually works. I've seen the same technique from the attached image in multiple alleged "php2shell exploits", including one on GitHub with over 100 stars. Problem is, it's not php2shell, nor is it even a vulnerability at all. It's a technique known as "session poisoning", which can be leveraged to exploit local file inclusion (LFI) vulnerabilities in PHP apps (not PHP itself). The only thing it has in common with CVE-2026-109618/CVE-2026-109619 is they both use the "PHP_SESSION_UPLOAD_PROGRESS" feature. And mitigation advice for both issues reference setting "session.upload_progress.enabled" to "Off". People are shoving loose details of the vulnerability into LLMs, the LLMs are keying in on the "PHP_SESSION_UPLOAD_PROGRESS" string, then generating session poisoning code that has nothing to do with the actual CVE. And because the people doing this have absolutely no idea what they're doing, they're confident enough to post their "proof of concept exploit" to GitHub and share it on social media. So if you see people talking about "session poisoning + LFI" it's likely their LLM hallucinated an exploit based on a 2018 blog by Orange Tsai talking about a local file inclusion attack vector. What's even worse is that "security researchers" are then using LLMs to triage these exploitation attempts, falling victim to the same hallucinations, then confirming there is ongoing mass-exploitation (there currently isn't). The actual real exploit is very difficult to exploit, and so far I've not seen anyone successfully get it working on more than a handful of PHP version with highly-specific configurations. LLMs are useful tools in the hands of skilled professionals, but for others, they're often just a Dunning-Kruger accelerator.
7
9
4
184
33,778
vuln research in 2026
1
39
1,660
really cool post. essentially taking existing fuzzing harnesses, and "extending" them via formal verification to cover more inputs nothing more nothing less unsurprisingly, there's lots of trivial bugs that these harnesses miss. so it might be a while until we're "vulnzero"...
New on our Frontier Red Team blog: using Claude to formally verify software at large scale. Formal verification can prove that code is free of certain bugs, but historically it has only been feasible for small codebases (or required a lot of expert time). With AI models, however, this is beginning to change. In collaboration with @theoremlabs, we used Claude to prove security properties in over one hundred real-world open-source libraries over the span of a few weeks. Read our research in full here: anthropic.com/research/forma…
1
5
2
78
8,538
Doing our part to keep Signal safe. Thanks @quasar0147! CVE-2026-113380: Video/audio leakage after Signal call hangup
2
2
2
112
5,624
Robert Chen retweeted
This week, @fund_defi, @jump_ ,@paradigm, @SolanaInstitute and @Uniswap submitted a comment letter to @USTreasury on its proposed GENIUS Act Section 3 implementation rulemaking. The GENIUS Act established important statutory protections for DeFi and developers of blockchain technology. We believe that Treasury’s final rule must respect these statutory boundaries.
1
10
2
24
2,323
lots of potential footguns with multisig/mpc setup. great article on in the wild attacks sirn.org/advisories/sirn-202…
SIRN ADVISORY: Multisig deficiencies across the ecosystem Through recent SIRN incidents and investigative efforts, we're seeing multisigs and MPC wallets with security much weaker than their on-chain configuration or operators' understanding suggests.
1
1
26
2,830
Robert Chen retweeted
"we're giving you the @osec_io badge, use it responsibly" MLG Android Root gj @ryaagard
Another fun bug, we turned a Linux kernel timer UAF into a kernel read/write on Android, root + SELinux permissive. Great work @ryaagard! Stay tuned for more 🦦
4
2
40
1,975