Co-Founder @neploxaudit. CTF team @C4TBuTS4D Security Researcher.

London
Joined December 2023
In 2024, I interacted a lot with Extensions. I decided to create a resource that will help with a basic understanding of extensions and key attacks. P.S. I tried to make everything as clear as possible and hope it won’t feel too overwhelming anywhere. extensions.neplox.security/
21
107
1
419
40,694
We've been working with x402 for a while. Now that it’s taking off, we wrote down everything we’ve learned in an article Also, we've refreshed our website design. Check it out, along with our previous articles if you missed them 👇
We found multiple ways to bypass the 402 paywalls 💸 neplox.security/research/bre… :~$ "402 Payment Required" sat unused for 30-ish years - Now, the protocols reviving it let us skip the paying part; Here's how paywalls in TypeScript / Go / Java served paid content for free: [1] - x402 verify() checked the amount, the asset and the network; but not the recipient. What if we rewrite payTo in the console and payTo ourselves? 👀 [2] - MPP credential proved an invoice was paid, not what for. What if we pay 1 sat for /cheap, but spend it on the 100 sat /expensive? 👀 [3] - The middleware priced one path, the server served another; & here is just 1 example out of many: → GET neplox.security/premium HTTP/1.1 Host: app.example ← HTTP/1.1 200 OK { "served":"PREMIUM CONTENT" } <!-- READ MORE: "Breaking HTTP (pay)walls" --> 👉 neplox.security/research/bre…
1
2
27
1,401
slonser retweeted
> Highlights – the bugs you might find interesting: 0️⃣ PrivEsc TO Admin: through Privy Google account linking 1️⃣ Data Leak: when users can link the same address → they collide 2️⃣ Another sign-in flow + Privy / Google Auth bypasses = Account Spoofing 👉 link.neplox.security/nabu-au…
1
2
5
723
Funny leak at Chrome No AI, Just @J0R1AN and a brilliant idea And yeah, this is only a small part of something bigger -writeup coming soon😵
4
11
182
10,330
"We used to be magician on the board ... and now it's just like press a button and there's no mystery anymore" - @MagnusCarlsen on how chess changed once engines came along I'm getting pretty much the same vibes from the AI in CTF... (and IT/InfoSec in general)
3
5
1
84
10,360
Maybe CTFs won't die (just like chess didn't), but it seems we have to admit that capturing that "something magical" feeling is harder now. AI is turning a lot of things into routine work // Just my thoughts after defcon ctf quals
7
1,287
Sometimes I feel like yapping about security issues; but not in a shitposting way - 🥀 So I recorded a series of videos – “Security Ensh!*$ttification”: each episode covers a certain hot topic + introduces you to research articles! 👁️ Ep.00 – Backdoors: youtu.be/Uc8J81VZ6W0
1
2
7
1,872
Btw, if anyone has interesting job opportunities in London/UK, I'm open to them.
7
15
4
94
28,389
I didn't really want to get involved in the discussion about the "death of CTF" because of AI. But the conversations on Twitter keep going, so I'll express my thoughts in this thread. For those too lazy to read — CTF will live on. For the rest, I suggest reading the thread below.
4
40
2
231
30,010
CTF is a really awesome activity. But I don't want it to turn into an AI model race. The AI-assisted approach to solving is here to stay, but we can make sure challenges don't turn into "Hey Claude Code — solve this chall."
1
22
3,480
I believe CTF organizers will adapt — they just need time, and top CTF competitions will simply become insanely difficult. We need to change something, otherwise the CTF community will be the first to die — and that community is actually greatest value that CTFs have given me.
1
2
45
3,751