
Security Vulnerability Coach, responsible for @x41sec and @persistent_psi Tweets here are my own.
Right here
Joined January 2009
- Tweets8.3K
- Following609
- Followers3.4K
- Likes8.7K
Pinned Tweet
Reality check your defenses! POC collection of the Month-of-Bypasses: github.com/persistent-securi…
"We had our hands on it, and we called it a crash."
In 2024, Mihail Kirov's @Quarkslab team reported a flaw in the exact code behind PHP2Shell. Two years later, three teams turned it into a working attack in six weeks.
His story:
tolmo.com/blog/faster-than-a…
cc: @cryptonitemmk
A liability with a timer on it:
tolmo.com/blog/faster-than-a…
Let’s set the record straight: @lcfr_hax was the first to discover php2shell and develop a working exploit. See his August 5 tweet: xitter.cf/lcfr_hax/status/208503…
His work convinced the PHP Foundation to invest in fixing this entire bug class. He then worked around the clock to review, test, and retest the patches.
We’ve put quite some effort into making a full AEV solution available and affordable for even smaller businesses! Including AI that can work in air gapped environments like OT and explore attack paths in safe and controlled way! 🚀
Some environments thrive in the cloud, others demand on-premise control especially in regulated sectors
Nemesis handles both effortlessly by running #localAI model inside your own system.
Get continuous attack validation w/o compromising on where your data lives.
#ThreatToTest
Markus Vervier retweeted
Some environments thrive in the cloud, others demand on-premise control especially in regulated sectors
Nemesis handles both effortlessly by running #localAI model inside your own system.
Get continuous attack validation w/o compromising on where your data lives.
#ThreatToTest
Markus Vervier retweeted
We’re heading to Techtonics!
Our co-founder Babette De Decker will be there representing Nemesis, ready to catch up w familiar faces, make new connections and talk about where defenses break down.
If you're attending, come say hi 👋
#Techtonics2026 #Networking #cybersecurity
🤖 Made with AI
Markus Vervier retweeted
Loved catching up with old friends and making new ones at @_c0c0n_ 2026!
Getting such a warm welcome from Kerala Police was a highlight, along with @marver's training session.
Big thanks to the organizers, volunteers and speakers for a great event 👋
#c0c0n2026 #cybersecurity
Wow I really managed to look like the evil red team guy in this one! 😈
A month ago I rented an Irish Bar and hosted an AI security panel + speakeasy. Here is the 35min panel youtu.be/ShMq_vH44LU
Lots of fun content here.. I've gotta put more of these on the books.
With Uber and friends we traded conversations with drivers all over the world for lower risk of being scammed and ease of use.
Markus Vervier retweeted
Qwen3-0.6B running happily in a bare metal Go TamaGo microVM and writing a haiku about it.
This is on pure CPU with GOEXPERIMENT=simd on.
Qwen3.8-27B also runs (slower) if you have enough RAM.
I just need a bare metal Go GPU driver now...
Markus Vervier retweeted
🎉
PDF direct link here archives.phrack.org/dl/73/th…
Zip's (team-teso) long lost ssh1-crc32 exploit was found (xt 😘), (PLUS hellkit, 7350statd, 7350qpopper, icmp-tunnel, shellcode, lkm-work, and much more).
🚰 LEAKING phrack 73 article NOW (@phrack ):
github.com/hackerschoice/tea…
🤘🤘🤘
Markus Vervier retweeted
One more Phrack 73 leak for you!
Blueboxing Myths and Feelings: a nostalgic dive into phone phreaking’s golden age.
archives.phrack.org/dl/73/bl…
by @hackerschoice and @GammaTHC
On my way to #c0c0n2026 where I will give a training on building AI tools for security. Thanks for having me @_c0c0n_ !
Markus Vervier retweeted
Signal security, theory vs reality:
you've got PQ-e2ee and forward secrecy and post-compromise security and secure contact discovery and key transparency and PIN protection etc. and you use a fully patched burner phone so you feel so secure and confident when you send that message in the wrong convo and only notice it hours later—not even kidding, much greater a risk than post-compromise etc., should have a local classifier that tells you "are you sure?" when a dissonance is found
Markus Vervier retweeted
The TL;DR of what Anthropic just said:
1.) GLM-5.3 is as good as Mythos for exploit development.
2.) Unlike Claude, GLM-5.3 gives you the results you pay for.
3.) Governments should ban AI models which are as good as theirs but are not made by them.
The funniest part is how Anthropic admitted self-reflectively that the lack of guardrails may actually be benefiting the defenders working to secure their systems. 🤪
Something they never wanted to allow, because of possible misuse.
I don't get it, but I feel Anthropic should at least put a note at the very bottom if they are doing paid advertising to promote GLM-5.3. 😜
Source:
anthropic.com/research/glm-5…
The audacity of OpenAI bike-shedding about a bug bounty, while they’ve had 50.000 of their own agents marauding through other people’s infrastructure.
fwiw, i’m going to stop talking about the openai thing. we made our points pretty clearly, one final note.
to hackers:
1. most serious companies will receive good-faith research like this gracefully and treat you well. they don’t question your intent or threaten you, they look at your profile, your history, and the work itself, and that usually estables bridge quiet quickly.
2. yes, some of the "old and outdated people who are not following the state of vdp," as someone put it, are right about the risky waters.
don’t randomly test every company, stick to top companies. nd yes, they are right about pivoting too, opening pr is one thing, cloning openai’s source code or exfiling ci secrets and starting to hunt for model weights would obviously be a crazy step too far.
3. have your own disclosure policy, i will attach down below ours, 30/90 days, whatever you believe is reasonable. personally, i wouldn’t sell my sole or sell away control of my research for money, being able to show your work publicly goes very far.
you can call that chasing fame. i call it keeping my agency over my own work and proudly showing people what we built.
4. when you choose to publish, understand that publication is opposite of what a ciso wants, occasionally people will become antagonistic.
try to talk sense into them, a vdp does not have to become an embarrassing story, it can become a great one.
case in point, google cloud had nasty bugs disclosed publicly all the time, researchers wrote detailed posts about them, and google celebrates security research every year, highlights top bugs, and has people like @LiveOverflow make videos about them.
Hacking into Google's Network for $133,337:
youtube.com/watch?v=g-JgA1hv…
StubZero: $148,337 RCE in Google Cloud Production
brutecat.com/articles/google…
---
to security leaders:
1. please, you don’t need to be asinine.
2. researchers are doing something useful for society and for your company, even when they also have their own interests
3. treat them well, learn from google or meta, vulnerability research works best as a collaboration, not a threatening relationship
Markus Vervier retweeted
Your weekend reading assignment has arrived early.
A first taste of the upcoming, still-under-wraps Phrack 73: “THE PROXY THAT MADE NO SENSE” by @mikko.
archives.phrack.org/dl/73/th…
























