Issue with strings containing \x20 and other hex

[IMN-MichaelL]

I may have missed something in the documentation or other issues but I'm running into an issue where I have some text that is formed and then output containing \x20 and other hex. I'm using the webpack-obfuscator with default settings. I've also tried to use the comments to prevent obfuscation of the function that has these strings but it doesn't seem to work. Unfortunately the string gets output with the hex without being decoded. Any way to prevent this from happening?

[annkiriakidi]

I have the same problem

[IMN-MichaelL]

After much trial and error I think I've solved the issue with the following config:
reservedStrings: [ '\s*' ]

I am not 100% sure if this is the ideal way of solving the problem but it so far appears to work.

[annkiriakidi]

After much trial and error I think I've solved the issue with the following config:
reservedStrings: [ '\s*' ]

I am not 100% sure if this is the ideal way of solving the problem but it so far appears to work.

oh yes, it works for me, thank you so much <3

[SwiTool]

it does not work for me. I still have \x20 in every string with space and \x09 for tabulations, etc.

I use this package with webpack and it breaks :/

[fabienrohrer]

I just get the same issue and the workaround (reservedStrings) is not working for me too.

[schokolama]

Hello, I had the same problem. Figured out that in my case it affected the template strings containing placeholders.
The string was given as an input to the printf method of the winston logger.

So, I had to change:
logger.info(``TO BUY: ${x}kg of Aachener Printen for Christmas.``),
which was logging like "TO BUY:\x205kg etc." after obfuscation

to strings with concatenation operator:
logger.info("TO BUY: " + x + "kg of Aachener Printen for Christmas.")

[SwiTool]

Hello, I had the same problem. Figured out that in my case it affected the template strings containing placeholders.
So, I had to change:
logger.info(TO BUY: ${x}kg of Aachener Printen for Christmas.),
which was logging like "" after obfuscation, to strings with concatenation operator:
logger.info("TO BUY: " + x + "kg of Aachener Printen for Christmas.")

Oh ok, nice catch but in my project there are like 100+ files containing `string with ${variables}`
For several reasons (including eye-candy visual), I personally can't make that change in my project.

[sanex3339]

Hmm. I'll check template strings when I have time.

[schokolama]

Hello, my previous "workaround" was good only in combination with the reservedStrings option mentioned above. But I didn't like it, because the obfuscated code reveals the whole strings, and one can get a hint what happens in specific functions.

I figured out that this issue with \x20 is not coming from the obfuscator alone, at least in my case.
My build sequence looks like this: bundle code with webpack -> obfuscate the bundle.

When I bundled my code from within VS Code integrated terminal, the bundle looked like:
eval("\n // Greeting\n const t = 'test';\n console.log(\"this is a test\\x43\\x44\");\n console.log(\"this\" + \" \" + \"is\" + \" \" + \"a\" + \" \" + t);\n console.log('this' + ' ' + 'is' + ' ' + 'a' + ' ' + t);\n console.log(this is a ${t});\n console.log(\"this\\x20is\\x20a\\x20 test\\x41\\x42\")");

while from the standard bash shell on my system:
r="test";console.log("this is a testCD"),console.log("this is a "+r),console.log("this is a "+r),console.log("this is a test"),console.log("this is a testAB"),.

With the eval input to the obfuscator, the latter was taking \x20 occurances in strings as they are and therefore logged them.

Tip: Try to run your whole build from the system shell or see what you get by running from the integrated shell in case you use VS Code.

[simzard]

Hello All. I got the \x20 in my strings as well. I'm using webpack separately and then applying javascript-obfuscator afterwards on command line separately. But then I realized that i was running webpack in DEVELOPMENT mode. After changing it to production mode, the \x20's in my strings went away. HTH

Here is my webpack config:
const path = require("path");

module.exports = {
mode: 'production',
entry: "./src/index.js",
output: {
path: path.resolve(__dirname, "public"),
filename: "bundle.js" // this will then be fed to the obfuscator
}
};

[spidergleb]

Hello All. I got the \x20 in my strings as well. I'm using webpack separately and then applying javascript-obfuscator afterwards on command line separately. But then I realized that i was running webpack in DEVELOPMENT mode. After changing it to production mode, the \x20's in my strings went away. HTH

Here is my webpack config: const path = require("path");

module.exports = { mode: 'production', entry: "./src/index.js", output: { path: path.resolve(__dirname, "public"), filename: "bundle.js" // this will then be fed to the obfuscator } };

thanks boss

[gostave]

Had the same issue, @IMN-MichaelL solution DID work for me.
Thank you!