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

Tsu-lô-Kuān, Formosa / Taiwan
Joined July 2019
splitline 👁️🐈‍⬛ retweeted
DEVCORE CONFERENCE 2027 | CFP is open #Redteam, #VulnerabilityDiscovery, #Physicalsecurity, firmware and hardware RE, #AI attack surfaces. Bring the research that starts from a hacker's view. Deadline: Oct 11, 2026, 23:59 GMT+8 sessionize.com/devcoreconfer…
8
1
27
5,420
splitline 👁️🐈‍⬛ retweeted
In case you were wondering
101
122
31
6,580
273,997
splitline 👁️🐈‍⬛ retweeted
你是否也習慣將「官方網站下載」、「Microsoft Store 上架」或「官方套件管理庫」當作萬無一失的信任背書? 但「官方」真的就代表安全嗎? 從建置、簽章到發布,每一層都有可能成為攻擊者的切入點。 ​今年 HITCON,三場硬核議程將從三個完全不同的信任層級拆解軟體供應鏈,顛覆其安全想像: 💥 原初之穢:先莫管供應鍊夆毒,阮直接共官方發布源頭駭掉矣 | 講者:splitline 如果負責宣告「這是官方版本」的發布系統被駭了呢? 本場演講將揭露 Python、Ubuntu、Go、Alpine 與 Windows 套件生態系上游發布端的脆弱盲區。即便最終執行檔帶有合法數位簽章,只要上游建置環境遭滲透,簽章也可能無法保證你拿到的東西安全。 現場將公開多個實戰案例,展示攻擊者如何用非預期的邏輯漏洞直接拿下控制權。 ☠️ Not Just Spies Anymore: DPRK's Espionage Actors Are Coming for Your Crypto | 講者:Seongsu Park 當原本專注於國家間諜行動的 APT 組織轉向加密貨幣撈金,攻擊者開始重新利用各種「可信」背書。 從架設高擬真交易平台、申請公司簽章,到成功把木馬化應用程式上架到 Microsoft Store,再結合 AI 輔助開發、macOS TCC 權限操作與精準白名單投遞,這場議程將展示官方通路沒有被攻破,也可以被攻擊者拿來建立信任,造成極致濫用。 🚨 黑吃黑: 瞄準駭客的供應鏈攻擊 | 講者:Jason3e7、Samuel 當獵人自己成為獵物? 攻擊者密切盯著高熱度 CVE 的公開資訊,在社群瘋傳、復現 PoC 的黃金時間,將高度混淆與多階段載入的後門深埋在 PyPI 工具的深層依賴鏈中。 當研究員為了復現漏洞,在終端機按下執行的瞬間,測試環境就已淪為被控端點。 三場議程,三個不同的信任位置。 從官方建置環境、官方的發布通路,到你以為只是研究工具的第三方依賴——當「看起來可信」不再等於「真的安全」,我們還能相信什麼? 📅 HITCON 2026:8 月 21 日-8 月 22 日 🔎 完整議程:hitcon.org/2026/zh-TW/agenda… 🎫 購票連結:hitcon.kktix.cc/events/hitco… #HITCON2026 #HITCON #供應鏈安全 #漏洞復現
1
2
7
1,157
splitline 👁️🐈‍⬛ retweeted
My #BHUSA 2026 slides are online! It was an honor to share our AFD research and how a different perspective led to 30+ Windows kernel vulnerabilities. Blog post coming soon — check out the slides here: i.blackhat.com/BH-USA-26/Pre…
4
148
6
513
71,138
splitline 👁️🐈‍⬛ retweeted
Two of our researchers hit the #BHUSA stage for the first time. Angelboy(@scwuaptx ) shares how a different angle on AFD led to 30+ new #Windows kernel vulnerabilities. Splitline(@_splitline_ ) exposes backdoor risks in Go, Python & Flutter pipelines. #VulnerabilityResearch
1
10
87
3,929
splitline 👁️🐈‍⬛ retweeted
Seems that wp2shell PoCs are now floating around the internet, so we've published our blog post including our research methodology for finding the bug as well as a deep dive into the chain itself - slcyber.io/research-center/e…
16
201
24
715
79,603
splitline 👁️🐈‍⬛ retweeted
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
22
92
16
671
88,064
splitline 👁️🐈‍⬛ retweeted
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.
💥 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
5
9
1
111
27,473
splitline 👁️🐈‍⬛ retweeted
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."
3
15
1
129
14,825
splitline 👁️🐈‍⬛ retweeted
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@siunam321Mar 2
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 🥲
18
38
5
439
70,291
splitline 👁️🐈‍⬛ retweeted
68
712
91
7,044
271,152
splitline 👁️🐈‍⬛ retweeted
A POC for CVE-2025-55182 gist.github.com/maple3142/48…
32
422
60
1,953
553,117
splitline 👁️🐈‍⬛ retweeted
A bit late, but I just published my blog post on bypassing Ubuntu’s sandbox! Hope you enjoy it! u1f383.github.io/linux/2025/…
5
110
3
386
41,121
splitline 👁️🐈‍⬛ retweeted
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++.
17
78
14,538
splitline 👁️🐈‍⬛ retweeted
This is just a rumor to make themselves feel better, CTFers doesn't have life and probably all single
3
1
44
2,293
splitline 👁️🐈‍⬛ retweeted
I created a Linux Kernel challenge “Halloween” for the HITCON CTF Qual 2024 :). Below are the official writeup for “Halloween” and the unofficial writeups for "v8sbx" and "reEscape". Enjoy it! Halloween & v8sbx: u1f383.github.io/ctf/2024/07… reEscape: u1f383.github.io/ctf/2024/07…
39
145
14,068
splitline 👁️🐈‍⬛ retweeted
Orange Tsai 🍊
@orange_83617 Jun 2024
PHP just fixed one of my RCE vulnerabilities, which affects XAMPP by default. Check to see if you are affected and update now! 🔥 blog.orange.tw/2024/06/cve-2…
12
338
26
1,203
135,959