Twitxy Saved

Jim Manico from Manicode Security

Verified account This account is verified. Learn more

@manicode

18th-Level AI Magic User 🧙‍♂️
Teaching developers to build secure software with AI
manicode.ai
Kauai, HI and Cobb, CA manicode.ai Joined July 2009
6.4K Following 18K Followers 45K Posts

Latest posts 5

Jim Manico from Manicode Security Verified account @manicode
1) Google has also funded and built tools that produce fixes
2) The FFmpeg dispute was in 2025. Google changed its disclosure policy on November 13, 2026.
3) Google’s Big Sleep report for CVE-2025-59734 documented a use-after-free write in FFmpeg’s SANM decoder. It included a testcase generator, build and execution instructions, and an AddressSanitizer trace. FFmpeg’s team fixed it in 48 hours.
4) Marcus is spot on about the high level point though. Automated discovery can create more remediation work than volunteer maintainers can absorb. That’s a fact. Once an open source project becomes critical infrastructure the big companies using it need to start throwing down money to support the team or suffer the consequences.
Marcus Hutchins Verified account @MalwareTechBlog 23h
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.
View quoted post on X
1 replies 1 reposts 10 likes 1.6K views View on X
Jim Manico from Manicode Security Verified account @manicode
My new x.com favorites.

Everyone follow @_orcaman and listen.

And @dinodaizovi next.

Most of the OG’s are still in shock at the AI wave.

But these folks are charging forward with the hard truths.

1) Use AI as your main assessment tool, now.
2) Zero trust architecture is the new bare minimum.
x.com X. It’s what’s happening From breaking news and entertainment to sports and politics, get the full story with all the live commentary.
Jim Manico from Manicode Security Verified account @manicode
This. The sad truth but this. 1000x this.
Or Hiltch Verified account @_orcaman 1d
For anyone who wants to secure their app and infra, I have some good news and bad news for you.

The bad news is that unfortunately all of your traditional security tooling - PANW, Wiz, Snyk, and the likes - are no longer relevant for app/infra security.

That is because all that matters now is that you have an ** EXPLOITABLE ** vulnerability - and there is only one way to know and fix that: run an agentic hacker against your systems.

If you did not do this, your attacker will do it for you.

The good news: you can send an email to one of the big labs and hope they will let you pay ransom - they will provide you with the model/service you need to stay ahead of the attackers equipped by the same tools. You should also try the open models like GLM, though you will not find the same vulns, so you would need both.

Good luck 🤝
View quoted post on X