splitline 👁️🐈‍⬛

346 posts

splitline 👁️🐈‍⬛ banner
splitline 👁️🐈‍⬛

splitline 👁️🐈‍⬛

@_splitline_

友民党 / CTF with ${cYsTiCk} / @D3VC0R3 / Tâi-gí, zh-TW, en-US, es-PY / 🐈‍⬛

Tsu-lô-Kuān, Formosa Katılım Temmuz 2019
599 Takip Edilen1.8K Takipçiler
splitline 👁️🐈‍⬛ retweetledi
TrendAI Zero Day Initiative
TrendAI Zero Day Initiative@thezdi·
That's a wrap on Pwn2Own Berlin 2026! 🏆 $1,298,250 awarded. 47 unique 0-days. 3 days of absolute chaos. And talk about main character energy - congrats to DEVCORE for claiming Master of Pwn with 50.5 points and $505,000 - they never slowed down. See you next year! #Pwn2Own #P2OBerlin
TrendAI Zero Day Initiative tweet mediaTrendAI Zero Day Initiative tweet mediaTrendAI Zero Day Initiative tweet media
English
20
93
624
43.5K
splitline 👁️🐈‍⬛ retweetledi
HexRabbit
HexRabbit@h3xr4bb1t·
Honestly, with a little LLM help, I found variants, built a working PoC, and sent a polished patch to maintainer on the same day CopyFail dropped. So I’m curious why Xint didn’t find those variants before disclosure, assuming AI tools are used heavily in their workflow👀 Disclaimer: I’m an independent reporter and the patch author of the xfrm-ESP vulnerability, unrelated to the Dirty Frag post.
V4bel@v4bel

💥 Introducing "Dirty Frag" A universal Linux LPE chaining two vulns in xfrm-ESP and RxRPC. A successor class to Dirty Pipe & Copy Fail. No race, no panic on failure, fully deterministic. ~9 years latent. Ubuntu / RHEL / Fedora / openSUSE / CentOS / AlmaLinux, and more. Even if you've applied the "Copy Fail" mitigation, your Linux is still vulnerable to "Dirty Frag". Apply the Dirty Frag mitigation. Details: dirtyfrag.io

English
5
11
111
26K
L4ys
L4ys@_L4ys·
0days doesn't seem cool enough anymore. what should real hackers be doing now?
English
25
7
131
43.1K
splitline 👁️🐈‍⬛
splitline 👁️🐈‍⬛@_splitline_·
is there any cool non-frontend web ctf challenges this year that aren't llm-solvable 👀
English
1
0
3
692
splitline 👁️🐈‍⬛
splitline 👁️🐈‍⬛@_splitline_·
@guttapercha80 @MeeRebus11 @danieleskay However the traditional international name for this island is Formosa, while the ethnic name used by Hokkien-speaking ppl on the island is Taiwan. Yes, even in many Indigenous langs. For example, Amis, which you mentioned we are also called taywan Historical issue is complicated
English
0
0
1
145
GP size 80
GP size 80@guttapercha80·
@MeeRebus11 @danieleskay This is why even I don’t agree that they call Hokkien as ‘Taiwanese language’ It should had always been the aboriginal languages (Paiwan, Rukai, Amis etc)
English
1
2
61
2.6K
splitline 👁️🐈‍⬛ retweetledi
slonser
slonser@slonser_·
And this makes sense given how many CTFs are held per year. However, the ideal CTF challenge, in my opinion, should follow this formula: "The author conducted a mini-research project and instead of publishing it, turned it into a challenge."
English
3
15
127
14.1K
splitline 👁️🐈‍⬛ retweetledi
LiveOverflow 🔴
LiveOverflow 🔴@LiveOverflow·
What I’ve always found amazing about CTFs is that "flag is flag". Whether you found an unintentional solve or pwned the browser with n-day for a XSS challenge, it didn't matter. I totally get the frustration of AI, but there is no solution other than accepting the change.
siunam@siunam321

I started playing CTFs in 2022, and LLMs definitely changed the **competitive** CTF scene a lot, especially since mid-2025. I also started using LLMs in late 2025. Yes, those models did one-shot many challenges, but what's the fun of slopping them? I learned absolutely nothing 🥲

English
18
38
446
69.3K
splitline 👁️🐈‍⬛ retweetledi
dimden
dimden@dimden·
ZXX
73
781
7.3K
269.3K
splitline 👁️🐈‍⬛ retweetledi
NiNi
NiNi@terrynini38514·
The blog post is the full version of my talk at 38c3. It's about some vulnerabilities we found in libarchive and some interesting behaviors of libarchive that you don't want to miss. My favorite part is it only took us 56 seconds to trigger a crash by AFL++.
DEVCORE@d3vc0r3

Our latest deep dive explores libarchive vulnerabilities under recent Windows 11 updates. 🔍🔓 Check out NiNi's (@terrynini38514) technical write-up for key insights and security implications. Read more here: devco.re/blog/2025/02/1… #VulnerabilityResearch #Cybersecurity

English
0
18
80
14.1K
splitline 👁️🐈‍⬛ retweetledi
Renwa
Renwa@RenwaX23·
@dicegangctf @strellic This is just a rumor to make themselves feel better, CTFers doesn't have life and probably all single
English
0
3
43
2.1K
splitline 👁️🐈‍⬛
splitline 👁️🐈‍⬛@_splitline_·
@TalBeerySec @orange_8361 @BlackHatEvents I read that before, it was quite interesting! You’re right. Unicode normalization has always been a security concern, but I wouldn’t call it the core issue here. For me the root cause is still “Best-fit”. Unicode normalization is more of a broad bug category, like “injection”
English
1
0
4
229
Orange Tsai 🍊
Orange Tsai 🍊@orange_8361·
Our talk at #BHEU is done! Hope you all enjoyed it. 😉 A detailed blog is on the way, but in the meantime, check out the pre-alpha website worst.fit for early access and the slides! Huge thanks to @BlackHatEvents and my awesome co-presenter @_splitline_! 🐈‍
English
15
221
781
170.9K

Keşfet

@_L4ys @yuzhinok @guttapercha80 @MeeRebus11 @danieleskay @dicegangctf @strellic @orange_8361