CrocBoot retweeted
Basically, through a series of unexplainable events, maybe genetic, maybe environmental, I developed an unusually strong trait for "Adversarial Thinking", combined with epistemic curiosity and intrinsic motivations.
In human psychology you have this thingy called Adversarial Thinking, and it's like, a persons ability to think of oppositional moves, motivations, capabilities, resources, and defenses. It can usually be defined as a persons approach to solving problems from the perspective as trying to defeat, exploit, or circumvent something, but also encompasses defenses.
Adversarial Thinking, besides cybersecurity, is an absolute requirement in military strategy, criminal investigations, defense attorneys, fraud investigators, safety engineers, and (unsurprisingly) criminals.
Anyway, when I was 13 I was flabbergasted that someone could make "bad" programs. I knew about programming, but there was something so fascinating that we could write computer code which could be bad. I know it seems like a "NO SHIT DUMBASS" observation, but to me it was beautiful and when I really thought about it, it melted my mind.
My little brain wanted to understand how this was possible and I wanted more. I wasn't motivated by money or power, or blah blah blah. I had an insatiable desire for more information (epistemic curiosity) and I didn't care about anything else (intrinsic motivations).
I wanted to write malware because I wanted to find ways to abuse Windows. I wanted to know how it worked so I could abuse it and evade anti-malware services. I like reverse engineering malware because I can see what the malware authors did, or are doing, and it's almost like ... "yeah, I see what you're trying to do bro".
Sometimes I see malware and I'm like, "nah, bad idea, should have done this", or I think, "oh shit, that's a really good idea, that's badass".
I'm not the best malware reverse engineer. There are many way more intelligent, skilled, educated, or experienced than me. I'm also not the best malware developer, there are some truly brilliant people who understand and implement ideas better than me.
The only defining factor is I am abnormally persistent and abnormally obsessive about malware. I've passed many brilliant malware people in my career not from raw talent, or intellectual ability, but by pure brute force and inability to stop foaming out the mouth by how much I like it.
I'm mid-30s. Since I was 13 I've been in love with malware. Every single day I think of malware, look at malware, bonk malware, think of malware ideas, read malware reports. I've dedicated 7.5 years of my life to vx-underground, and I have no intention on stopping.
Yeah, so pretty much I've decided I'm going to dedicate my entire existence to malware and my brain thinks this is a good idea and makes me feel happy.
Claude Duet is honestly insane.
We went from babysitting prompts to dropping a messy half thought and having an agent just get it matching your exact intent, holding context across workflows, and executing in the background.
The alignment feels like a genuine leap for Anthropic.
26
CrocBoot retweeted
mfw I'm a Network Admin and I see a Threat Actor got access to the domain controller from ms-paint
Remote code execution in MS Paint.
cve.org/CVERecord?id=CVE-202…
yup....
CrocBoot retweeted
🚨 PSA for anyone running a Linux server, node, or relay
CVE-2026-98432 is a critical Linux kernel bug (CVSS 9.8). Someone on the internet can send crafted TCP packets and take over your machine. No login needed.
Ubuntu and Red Hat haven't shipped a fixed kernel yet. Debian, SUSE, Oracle and Amazon have.
What to do today:
1. Check your kernel: uname -r
Fixed versions: 6.1.190+, 6.6.159+, 6.12.113+, 6.18.56+, 7.2.10+ or 7.3+. Below that, you're exposed.
2. If your distro has a fix, update and reboot.
3. If not, block the attack. It needs TCP packets with "IP options," which normal traffic never uses. One nftables rule drops them. Log what gets dropped so you can see if someone's probing you.
4. Turn off MPTCP unless you need it:
sysctl -w net.mptcp.enabled=0
Programs built with Go 1.24+ use MPTCP automatically, and that's how the known exploit gets in.
5. Make it survive a reboot, and check it still works after one.
If you run a Bitcoin node, a Lightning node or a Nostr relay, your machine is on the internet by design. Do this today.
Self-hosting is freedom. Patching is part of the job. 🛡️
CrocBoot retweeted
You can never make everyone happy
Give it away for free - they hate you because you have something to hide
Don't give it away for free - they hate you because you don't have a free tier
If only @Tailscale explained why and how they have a free plan.... tailscale.com/blog/free-plan
Replying to @NathanMcNulty @Tailscale
"Folks" is insidious, I think.
I *really* haven't seen a solid honest explanation of "why is this 'great' tool free? Why does it make sense to rely on it strongly without paying for it" and "no free lunch" feels like it should be explored better.
CrocBoot retweeted
You have unlimited chances here.
- One post could go viral.
- One post could resonate with someone who needs it.
- One post could open a door you didn’t know existed.
Stop overthinking. Get posting.














