CISONAUT (@cisonaut) header
CISONAUT (@cisonaut) profile picture

Tech Exec * Infosec Explorer * Veteran * Expert AI Gaslighter * Serious - but not THAT serious

Joined February 2025
Photo by CISONAUT (@cisonaut)Photo by CISONAUT (@cisonaut)Photo by CISONAUT (@cisonaut)Photo by CISONAUT (@cisonaut)Photo by CISONAUT (@cisonaut)Photo by CISONAUT (@cisonaut)Photo by CISONAUT (@cisonaut)Photo by CISONAUT (@cisonaut)Photo by CISONAUT (@cisonaut)Photo by CISONAUT (@cisonaut)
FFmpeg's complaints are invalid. They don't care about writing secure code. They don't care that somebody can send you a video file that takes control of your machine. They are like every other "vendor" of software that doesn't care about the security of their code and who looks for reasons to pretend the vuln finders are the bad guys. The person finding a vulnerability in your code isn't the one who created it. I say this as somebody who has analyzed many bugs in FFmpeg. The code is inherently broken and unfixable. For example, one bug I looked at allocated a buffer in one library, using one algorithm to calculate its size, and then filled in the buffer in another library, using a completely different algorithm to calculate its size. Obviously, there was a size mismatch. The fix isn't to change the calculations to come up with the same size, but to carry bounds information with the buffer, so that the code filling in the buffer knows the buffer size, and can check it against an accidental overflow. Since these were different libraries, this requires a change in the API -- something no outside vuln researcher can do, something only a core maintainer can do. FFmpeg cannot be fixed without a major redesign of its API to carry bounds information. FFmpeg code is neither secure nor securable because they don't care ab out security. Google's vuln researchers didn't create this problem. FFmpeg has 1 person generating insecure code faster than 1000 vuln researchers can keep up pointing out problems.
FFMPEG had one of the most valid crash outs in infosec history IMO. There's a huge elephant in the room when it comes to the fact that cybersecurity is extremely unbalanced. You have like 1,000 people pointing at problems for every 1 person fixing them. Vulnerability research is extremely important, but it's become somewhat of a marketing stunt. First with fuzzers, and now with LLMs. It's a lot of "look what my new toy can do" rather than earnest attempts at actually fixing security problem. What Google did to open source developers was especially egregious. They're a $3.6 trillion dollar company, who spent billions upon billions of dollars building a bot that points at problems really really fast, then they just dumped them all on a bunch of unpaid open source project maintainers to fix. Then because of Google's 90 day disclosure policy, the maintainers have 90 days to fix the issues. After 90 days, Google goes public with the issues, making their project look bad if the vulnerability is yet to be fixed, and also potentially harming users if it gets exploited. The 90 day policy was intended to give developers a reasonable amount of time to fix issues, while also applying some pressure with the threat of disclosure. Otherwise, you do get a bunch of goober ass vendors that will just ignore all security issues reported to them, then act completely surprised when their software gets hacked. But when you're a small team, non-profit, or a solo developer, and you have a trillion dollar company's AI just blasting you with infinite problems to fix (each coming with a 90 countdown & a threat), that becomes extremely untenable. They're essentially inadvertently blackmailing developers into becoming unpaid interns. Then on top of that, Google profits unimaginable amounts of money from the use of open source code. They use FFMPEG's code extensively across several highly-profitable products, meanwhile FFMPEG's developers work for free. There's no reason Google couldn't have donated money, engineers, AI tokens, or something towards fixing the problems. They can more than afford it. I don't think Google has any malicious intent at all, it's just that the whole incentive structure behind vulnerability research is completely whack. All the glory goes to people who find issues, not those who fix them, so there's not a whole lot of interest in helping with fixes. Some vulnerability researchers will submit fixes with their reports, but most don't. Honestly, in 2026 cybersecurity basically just feels like the equivalent of 50,000 people following the housecleaner around yelling "you missed a spot". Abysmally little effort has gone into anything outside of pointing out vulnerabilities.
56
46
15
631
123,210
CISONAUT retweeted
just talked to my friend non technical + retarded but just went from 0->1m arr in 2 weeks i’m pretty sure this is illegal but this is what he did he got access to a deepseek 4.1v 1017 cyber loaded up $250 in credits and literally got database level access to over 19 companies with credits to spare fucking insane btw then he gave the companies an ultimatum either pay him $5k or he emails all their users they were hacked his offer has a 100% take rate he did this all while not knowing how to code + spending less than $250 and on top of that he got a few offers from companies to consult them on cyber security wtf is life
5
2
67
5,890
CISONAUT retweeted
i have no time to maintain all my vibe coded tools we need a business model where someone else maintains the code and i just pay a monthly fee
561
184
205
4,450
601,043
SCREAM IT FROM THE ROOFTOPS LORD TORVALDS
21
254
34
2,192
77,199
CISONAUT retweeted
9
9
2
150
3,277
CISONAUT retweeted
I'm so excited to be releasing this engine. This represents the first of hopefully a long line of work with Nvidia We didn't put comparison charts in the main post but rest assured WE SMOKED EM this is the best engine for your dgx station. its not close.
12
25
8
177
38,460
Rare footage of a 90s PC gamer who just realized he’s still 2 kilobytes short of running Wing Commander after fiddling with AUTOEXEC.BAT, CONFIG.SYS, and HIMEM.SYS for half a day… Kids today will never know.
614
532
108
8,283
246,658
CISONAUT retweeted
Still hits the same
376
3,535
657
38,270
12,898,387
CISONAUT retweeted
We have to build AI that murders us, because if we don’t, China will build it first, and I don’t want to get murdered by a computer that speaks Chinese. That would be ridiculous.
592
6,824
427
65,650
1,435,001
We’re launching AlphaGenome Atlas: an AI-powered searchable database mapping the predicted impact of all 9 billion possible single-letter DNA changes. Here’s how it could help researchers better understand our biology 🧵
261
1,042
359
5,062
4,718,875
CISONAUT retweeted
This is why I don’t want sama/dario to tweet
26
104
7
2,138
66,660
Caitlin Clark draws three Sky defenders and drops it off behind the back to Timpson 👀
12
134
19
962
119,420
Caitlin Clark has more 30 PTS | 10 AST games than the rest of WNBA history combined 🤯
537
3,305
348
40,079
1,416,505
CISONAUT retweeted
Carrington Mocks Caitlin Clark… Then Immediately Regrets It 😳🔥 #CaitlinClark #DiJonaiCarrington #IndianaFever #WNBA #FeverRising #Basketball #WNBAPlayoffs #CaitlinClarkFans
167
785
71
10,513
356,027
CISONAUT retweeted
battle scars
41
134
15
1,512
46,734
Dennis Ritchie created C in the early 1970s without Google, Stack Overflow, GitHub, or any AI ( Claude, Cursor, Codex) assistant. - No VC funding. - No viral launch. - No TED talk. - Just two engineers at Bell Labs. A terminal. And a problem to solve. He built a language that fit in kilobytes. 50 years later, it runs everything. Linux kernel. Windows. macOS. Every iPhone. Every Android. NASA’s deep space probes. The International Space Station. > Python borrowed from it. > Java borrowed from it. > JavaScript borrowed from it. If you have ever written a single line of code in any language, you did it in Dennis Ritchie’s shadow. He died in 2011. The same week as Steve Jobs. Jobs got the front pages. Ritchie got silence. This Legend deserves to be celebrated.
258
1,802
83
9,437
172,206
CISONAUT retweeted
Tapping the sign
just heard someone pronounce SQL as "sequel"
16
13
4
1,186
19,181
CISONAUT retweeted
CAIT YOURE NOT REAL 😭
143
673
296
7,793
1,791,496
CISONAUT retweeted
Origin, our code hosting platform, is now live. It's fast, easy to use, and deeply integrated with Cursor. Get started by syncing your repos from GitHub.
1,502
2,355
2,815
25,289
26,332,805
CISONAUT retweeted
He copied a value out of the Windows Event Log. Pasted it into his special browser. And he was signed into Microsoft Entra as the user who had just authenticated. No password. No phishing link. No stolen private key. @MGrafnetter's Black Hat USA 2026 research...
30
373
42
1,973
244,786