Futuremark 3DMark03 Patch and Driver Audit Report

Since 3dmark somehow managed to turn it off (I'd guess by re-ordering the instructions themselves) it hints at being targetted, instead of something that would generically work in all applications.

Though I'm personally suprised that they could do anything to the shaders that could both:
-change they way they look to the drivers (to expose cheating)
-not affect performance (positively or negatively)

Though, I'll take their word for it.

 

You don't necessarily have to reorder the instruction to disable the shader detection. For instance, instead of writing ADD source1, source2, target (no this is not valid PS code) you could change it to ADD source2, source1, target. Another simple change would be to change the use of the temp variables (e.g. whereever you used temp1 you now use temp2 instead).
This would work at least assuming the shader detection just uses a hash value of the shader - I think nobody thus far has said how exactly the shader detection works.