
Sec/Madness @privy_io principal security , @_seal_org technical council prev: HoS @uniswap, D&R/IR @RobinhoodApp, IR @BitMEX, Built @Paterva Maltego with RT
New York, USA
Joined February 2008
- Tweets13K
- Following3.1K
- Followers5.5K
- Likes27.8K
Pinned Tweet
Fun react bug, (CVE-2025-55183) if you have a server side component and it explicitly or implicitly exposes a stringified argument you can get the source code for that function. Also found DoS, but reported it to vercel instead of meta and some else reported the next day 🙃
AndrewMohawk⁽ⁿᵘˡˡ⁾ retweeted
Congrats to @killa who solved stealmybitcoin.com hours ago but I screwed up which key went on the server (the flag was a root wallet WIF instead of the branch WIF).
Check out their awesome writeup here: github.com/KillaBoi/StealMyB…
wow, those scores are something
Introducing Kimi K3.1 Pro: our most capable 3T-class open-weight model.
🔹 1M-token context, 2.8T total / 104B active params (MoE), Multimodal.
🔹 Full-project coding: games in Unreal, Unity & Godot.
🔹 Excels at parametric 3D modeling in Blender & CAD.
🔹 More reliable at finance work: Accurate modeling with hallucination down by 65%.
🔹 Matching the strongest proprietary models across coding, agentic and knowledge benchmarks.
Kimi K3.1 Pro and K3.1 Pro Highspeed (2–3× faster) are now live on Kimi.ai, Kimi Work, Kimi Code, and the Kimi API.
Open weights by Nov 4, 2026.
🔗 API: platform.kimi.ai
🔗 Tech blog: kimi.ai/blog/kimi-k3-1-pro
No matter how much fun, with this much still vulnerable from php2shell.censys.com/ , it seems irresponsible to release PoCs for this right now :'(
Its me, I have a working PoC with the infoleaks to bypass ASLR. It took a lot of prompting and re-iterating to find those, tested against PHP 8.5.11 x86_64 with with all defaults and tested over the Internet
also x86_64 PHP-FPM and AArch64 PHP-FPM just for @k_firsov
phoronix.com/news/LKML-New-T…
Does it ever end? Accidentally sent unpatched (incl RCE) bugs to public mailing list
Bind9 RCE anyone?
linuxcompatible.org/story/is…
Has anyone actually seen a fully working PoC in the wild for the PHP vuln? Finding the UAFs is fast, but you still need things like info leak to get it to exec and I dont see anyone posts that include it, just tons of llms that are just reading proc/other ways to manage layout
Its gonna be a long day for defenders :'(
An urgent notice from the Railway team
blog.railway.com/p/security-…
thephp.foundation/blog/2026/…
Really disappointing that companies put marketing ahead of safety.
Fresh Node.js + React/Next.js security fixes:
Node Brotli RCE (CVE-2026-111497): 22.23.4 / 24.22.1 / 26.12.1
Next.js: 2 critical RCEs + Server Actions DoS → 15.5.28 / 16.4.1
Check your deployed versions.
nodejs.org/en/blog/vulnerabi…
nextjs.org/blog/nextjs-secur…
Love that people arent even bothering to rewrite AI slop, just screenshot and go, who needs to validate findings anymore. Security needs to have PoCs that rm -rf / again to bring back some critical reviews.
PHP 8.5.12 released - 90 fixes in 29 components, including security fixes (CVE-2026-109618, CVE-2026-109619).
Changelog + downloads: php-net.pro/news/php-8-5-12-…
- [RCE via OOM corruption · Advisory · php/php-src](github.com/php/php-src/secur…)
- [RCE via stale global state · Advisory · php/php-src](github.com/php/php-src/secur…)
















