[ArkPhaze]

No offense, but this is just like every other "batch script to exe" lame trick. Lots of these just write off to %temp% and execute it, thus this isn't actually a batch script to an exe. I criticize all of these converters for this reason, it's the lamest thing ever.

Even a crappy system() call or something in .NET to execute through cmd.exe would be better, and it would also be a legit, batch to exe if that were the case. I would encrypt the strings though, decrypt them, and run them that way in memory. Anything past that is a waste of time if you really cared to "try" to protect a batch script because batch isn't very powerful to begin with. It's mostly used to automate simple tasks. Although unless they were to actually debug the program and/or decrypt the strings, it would still be more secure than direct system() calls with plaintext strings, or a shovel-off to the %temp% for invoking.

Actually, I would say even going through one of these converters to boot, is nearly a waste of time.

Just my few cents...