To stop AI decompiling your game, make the code look like a bioweapon
A tongue-in-cheek guide: rename functions nanoVirusFactory and let the safety filters do the rest.
A tongue-in-cheek post from @zrkrlc offers advice on stopping Opus 5.5 from decompiling a game demo: rename everything to scary names like nanoVirusFactory and strcpyOverflow, add fake bomb-making comments and hide fake SHA-2 blocks. It drew about 800 likes.
The joke relies on how AI models are trained to refuse harmful requests. If code looks dangerous enough, a cautious model might decline to analyze it, which would accidentally protect it from reverse engineering.
Why it mattersBehind the humor is a real concern for developers. Strong models can now read and decompile compiled software, making it easier to copy or study someone's work. Turning safety filters into copy protection is a joke for now, but it shows people probing how those filters can be gamed.


