
Thank you @msftsecresponse for the unexpected Most Valuable Researcher 2024 gift. The pink hoodie will probably end up in my wife's closet. 😉

Private account! Red teamer @codewhitesec. @frycos@infosec.exchange @frycos.bsky.social

Thank you @msftsecresponse for the unexpected Most Valuable Researcher 2024 gift. The pink hoodie will probably end up in my wife's closet. 😉

Starting our journey to Amsterdam shortly. We’re looking forward to interesting talks, and more important: interesting people. ✌️
Vulnerabilities that get under your skin: join the talk of our researchers @frycos & Fabian Weber at @hardwear_io for a demonstrated attack chain targeting connected medical infusion pumps. hardwear.io/talks/vulnerabil…

Vulnerabilities that get under your skin: join the talk of our researchers @frycos & Fabian Weber at @hardwear_io for a demonstrated attack chain targeting connected medical infusion pumps. hardwear.io/talks/vulnerabil…


Infusion pumps deliver medication, but can they be hacked? At #HardwearNL2026, @frycos & Fabian Weber of CODE WHITE reveal how firmware reversing and unknown vulnerabilities led to an infusion pump compromise. Register now: hardwear.io/nl-2026/talks-sp… #FirmwareSecurity

Happy announcement: My colleague and me will present a talk at hardwear.io NL 2026, "Vulnerabilities That Get Under Your Skin: Targeting the World’s Best-Selling Infusion Pumps". 100% human-brain VR 😛

100% this —> AI agents are inherently dangerous. We shouldn’t have them. We should nationalize the AI labs, decommercialize it, and use AI exclusively for scientific research.
🚨 OBAMA ON AI: "If we are thinking about AI just in terms of how do we cure cancer or get better energy, you can do that without having agentic AI and having it just roaming free in the internet. The reason you are doing that is because you have to market a product that people will pay money for. That’s a misalignment between what our society needs and the commercial imperatives that these companies are facing, not because necessarily they’re trying to do bad things, but because they’ve got to justify these valuations. So, that’s one more reason why it is really important for us to have a competent government and a serious bipartisan conversation around this issue, and we have to do it fast. And I would encourage voters to pay attention to this. If somebody does not have a serious plan for how to deal with this, then they’re not meeting the moment, and you should probably look for somebody else."


i talked to a lot of people who played the defcon ctf finals to understand how llms affected them, both professionally and mentally. i went in hoping to learn that human intuition still mattered. instead, ctfs in their current form as everyone saying is dead, players are forced to operate slot machines because anyone who refuses to token-max loses to those who do. almost everything i learned, including how to learn, came from grinding ctfs. but the pipeline for developing that kind of skill and expertise now seems broken, juniors are rewarded for token-maxxing rather than going through the process of actually understanding things which is quiet sad and ctfs might not produce high quality security researchers any more. this also has serious implications for people who can’t afford tokens. five years ago, i wouldn’t have been able to afford access to something like gpt-5.6, and I would have been locked out of the very competitions that helped me build my career. anyway these are questions i asked if interesting for anyone: did they have fun? almost everyone was unhappy. it has largely become slot-machine operating, if they refuse to use llms, they lose to teams that do. it is not there is no fun at all, playing with friends and competing was all fun just process of solving which is main part and it isn't fun.(please let me know if you had fun) did having a skilled human in the loop still matter? i got mixed answers, but the leaderboard tells a fairly clear story, the top teams aggressively token-maxxed, by pooling gpt accounts and stuff. the #1 team allegedly spent around $50k on tokens xd. how much of the outcome came from human skill versus token-maxxing? its probably 95% token-maxxing and 5% human skill. some challenges, especially visual ones, remain difficult for llms, and human intuition to prompt mattered. but overall, the dominant strategy appears to be throwing more tokens at problems, one interesting observation, people who were better before llms were also better after the llms and they are the ones solving lot of challenges so it seems still 5% operating skill will put u in top and can't be dumb operator. will a new generation of players simply adapt to this new kind of competition? i thought maybe current players are just behaving like boomers who hate every new technology. but unlike previous technology stuff, there doesn’t seem to be much for the human to master here. token-maxxing is literally just token-maxxing. it doesn’t reward human ingenuity, it discourages it, and may eventually atrophies and makes us dumb let me know if i missed something or if you have different opinions

Hacking random companies is totally okay if I claim my GPU did it?!



We’ve now seen at least four nginx RCEs that require non-default configs: nginx rift, nginx poolslip, and two of our own (including the one in the last tweet). The configs involved are unusual, which raises the obvious question: do these attacks actually work in real-world deployments? We asked Claude to download and analyze more than 4,000 nginx config files from GitHub. The result was embarrassing: none of them were vulnerable to nginx rift or our own attacks. We can’t say anything about nginx poolslip yet, since it hasn’t been published. So don't worry about your nginx yet. Moral of the story: AI can generate FUD, but also help fight FUD. Embrace it!

NGINX Rift is the new 18-year-old nginx RCE. Every version since 2008 in scope. We scanned 1,465 configs from 528 popular GitHub repos to see how bad it really is. What we found, and where the real attack surface actually lives 👇

See ya @offensive_con 👋

Would love to see ZDI showing stats of submissions, so we can know what is truly on fires (everyone sitting on 0day exploit) instead of all the hypes around these noisy LPE and unexploitable CVE, or in OS that nobody use...
but anw we guess they filter based on their implicit own rules ( like uniqueness , highly impact... ) not really overwhelming and reject blindly.