You can obfuscate anything. The projects we get to "finish" are always in very bad state. Bad design, unreadable code, terribly inefficient, totaly unreadable ... all in VBScript. I can asure you that I saw things that forced me to scream.
Just a little example. The *&%@#(*$^%*#*&&#^$% was using three variables j, k and l throughout the whole page, then passed them to the next page, and used again j, k and l, but the meanings were exchanged. What used to be k was now l and vice versa. Bleargh. (In the end none of those variables were needed. The design was bad.)
On another page they first wrote the posted data into a file, then made a few useless obfuscations, read the file back in and processed the data. Of course the name of the file was static and there was no locking. But it took a few hours to decipher the code only to find out 90% is worse than useless.
Generaly I think that the quality of the average VBScript code is much worse than the average Perl. Because "just about anyone can write VBScript". So often people not only without education, but also without brains spit out horrible VBScript for living.
But the management is happy ... if the boss looks at the code he doesn't see any strange characters, there are normaly looking english words, it all looks readable ... until you try to read it.