xss-payload-list

en something you could sketch out. Even if you think you have something, like, say, https://github.com/payloadbox/xss-payload-list , you're looking at a human list. All I'd have to do to completely scramble that entire list is to have a parallel evolution of ASCII where the letters and symbols are in completely different places than they are now. Nothing in that list would work if all the control characters in ParallelASCII were in 223-255, and the alphabet was 0-52, and all the symbols were from 128 on. And that's still a very human standard that is, for instance, based on bytes instead of, say, collections of 9 trits as the base level of the system. There's an effective infinity of other ways of encoding things and deciding what characters have what characters doing what things... assuming "characters" is even the way to look at the representation in the first place. As others mention, you could hypothetically send a program that does something that can't be analyzed, through sheer size if nothing else, but it would still be an uphill battle to just guess how to exploit something. You'd be looking more at an AI that is good enough to talk itself out of the box, rather than something that is actually "hacking" anything reliably.