I would assume that to a LLM, a binary executable is not much worse than actual source code. And it's much denser, just missing the semantics of human-written identifiers. It's the code's pure logic, condensed into machine language.
And there's tons of it, many vendors supply it "freely" (you don't need license keys to train on a binary) It's often battle-tested code that you wouldn't get hold of otherwise, and compared to ingested source code its unlikely that Codex regurgitates a recognizable part of a Windows 2000 DLL into your C++ source code.
So as an example, there are a bunch of different ways a for or while loop can be implemented in compiled code, but there are also situations where two quite different source constructs can result in the same machine code sequence.
Machine code certainly won't teach an LLM much about how to write good source code.
Executables are often larger than their source code.
A toolchain that creates repeatable binary builds is difficult to create. And a nonrepeatable build is potentially nondeterministic, in the sense that uncontrolled or hidden inputs impact the output.
Also it _is_ possible to gzip a file and get a larger file, there’s an inflection point based on the distribution of symbols in the source where the same compression algorithm produces a larger file than the original
Nowadays you're getting gray area stuff like new AI generated stories based in the Harry Potter universe, which is probably copyright violation but it's not actually pirated video, so Content ID doesn't spot it.
Makes complete sense to study things people actually want to use and consume
Plus, there's so much open source, and game engine SDKs, freely available, that with a few game engineers at Deep Mind, they can write training systems that connect the dots.
It's definitely a gray area because these models are doing what an indie game dev would do, but at a scale and precision that's basically pirating the game, and getting around the rules of copyright to do it legally.
No reason to belive none of the labs have similarly trained on binaries.
If it works and it's verified in nine different ways, throw it in the training pile, and then automate the process.
I imagine that someone will eventually figure out how to query black-box LLMs for copyright violations without triggering their guardrails. This is an existential threat for anyone running a black-box LLM with stolen data.
They're about to learn the hard way that the market wasn't profitable even without 10x the number of new entrants.
And that a third of the paying customer base (which was not that large to begin with) gave up on plug-ins anyway to generate finished music tracks from prompts.
By them being nothing special?
> appearing this year?
Vibe coding in general became viable last year, Opus 4.5 is Nov 24, 2025.
I chalk it up to synth and audio guys being among the more innovative users, personally - its a market of folks who have always wanted to design their own DSP/audio-graphs, and were primed for the opportunity that AI/ML presented to do so.
The same goes for the vibe-coded game communities, and as well all the retro guys.
Folks tend to not realize just how much open source is out there in fields/subjects they’re not really familiar with.
I've made a bunch of unreleased vibe-coded VST plugins to replace the hundreds that I've bought over the years - and many of the barriers to development weren't the model. Just having belief that the model was capable of the work, a bit like the 4-minute mile. Also knowing to persevere and iterate with the model, not giving up because the first UI is inevitably so amateurish.
There's also a flywheel happening. If you make permanent notes on the process, your rules for UI design, a library of re-usable components and algorithms, tools so the model can judge its own work... the whole process for the next VST just gets much faster & much easier. Same goes for any software you make with AI too.
As of this fall, you are being professionally irresponsible and SHOULD NOT be working in the field if AI is not integral to your SDLC. At a minimum it should be checking your code for bugs and vulnerabilities.
And I sort of understand what you’re trying to say in that second line, something along the lines of “the only thing that stops a bad guy with a gun, is a good guy with a gun”, right? Unfortunately it’s poorly phrased.
If AI isn’t hardening my code, then my code is very vulnerable to AI hacking from an adversary, I’ll grant that. But an absence of my AI does not cause the presence of an adversary’s AI in the way that the binary construction claims. (Compare “if you’re not with us, you’re against us”, which is a threat that says the absence of your fealty does cause the presence of my hostility.)
Likewise, I’ll grant that AI hardening my code does mitigate the damage from AI hacking, but again its presence does not cause the absence of an adversary’s AI hacking in the way your phrasing says it does.
You don't need software for that aside from the compiler/linker tools (which are free for C/C++ compilers, rust, etc.). You can then permutate/generate the source code using tools/techniques like fuzzing.
There's also things like Intel's instruction set documentation.
"Hello, we're here to see whether or not your fridge is runni-Hey, no not like that, this is serious!"