Please pardon what may be a naive suggestion. This isn't my area and illness had me "benched" for a long while. Is there an inverted solution? Maybe it's worth

Please pardon what may be a naive suggestion. This isn't my area and illness had me "benched" for a long while. Is there an inverted solution? Maybe it's worth releasing not a simple PoC, but an unnecessarily large ball of executable or testing procedure that incorporates the PoC for testing purposes, but also does many harmless, exploit-like but nonsensical things, performing only one action that matters (the test.) A hairball of mostly trash code or procedure that is not trivial to untangle, in other words. The idea is to create enough of a mess to stop the script kiddies from quickly knowing what to modify for their own purposes, not forever; but for a time. Just maybe it would be possible to create a hairball that takes longer to untangle or trace than just having a pro tear apart the patch and roll their own attack, ignoring the hairball. If so, providing the test/PoC/hairball is not giving the pros in the black hats any extra time. (But in any case, at least you are not amusing all the script kiddies.) If you can make a worthy hairball, you might just want to release the hairball just a little ahead of the patch; enough to whet admins' appetites for the patch - inverting the current order of release. (Or not.) Again, this may not be practical in all cases or any; and my apologies if that's so. PS There may be an argument in here for providing an "unnecessarily" and complex patch, too, to make it harder to reverse engineer - perhaps worth considering.