helmet VS javascript-obfuscator

Helmet is an npm package that includes middleware to handle and filter out malicious request headers (exploiting XSS vulnerabilities or clickjacking, for example). You can utilize Helmet's default configuration or customize it based on your needs following the instructions provided here.

helmet

By default, NuxtSecurity will set security response headers to match the values recommended by OWASP and a popular Express.js middleware called helmet.

Utilize security headers and middleware to add another layer of security to your Node.js application. Tools like Helmet.js can help you set secure HTTP headers, while middleware can assist in filtering and sanitizing user inputs.

Documentation Link: helmet

Helmet helps “sanitise” the input, which might not have come from the UI directly. Mongoose is what is known as an Object Document Modelling (ODM), which defines a structure (schema) for the stored data, making it easier to manage in Express. These additions have been omitted from our example stack purely to simplify the tutorial and focus on the fundamental tiers and interfaces.

If you can repro the issue with a minimal tsconfig, with nothing but an import statement then it's probably something the maintainers of helmet would like to see. There's also this (recent) issue I saw looking at their queue -- maybe related? https://github.com/helmetjs/helmet/issues/424 ...

// Security // https://helmetjs.github.io/ app.use(helmet())

You can learn more about each header and how to configure them in the Helmet documentation.

These days I only use middleware if it's global and has no outputs. Helmet comes to mind.

I don't need/use IDA, Nemlei just used https://obfuscator.io/, which just obfuscates the crap out of the code using various known methods (which I won't go into detail, it's public knowledge) and an un-obfuscation was cooked up by others. The one fucked-up thing the website does is randomizing function names, it just changes every variable/function name. We can't "un-obfuscate" those, so it's up to our brains to figure out what the code does, and change the names back.

I was considering using a obfuscation library (https://github.com/javascript-obfuscator/javascript-obfuscator) and noticed in the usage example that backticks are used and the javascript is enclosed within. The issue is that my javascript already has backticks from using template literals so my code then errors out.

Obfuscation: JavaScript Obfuscator

What I ended up doing is having two build steps, one for renderer and other for the main process, in the main process build I use https://github.com/javascript-obfuscator/javascript-obfuscator. Works pretty fine.

It's to purposefully makes your code harder to read so it prevents people from stealing your work. Here's a tool that does it: https://obfuscator.io/

I just tested it on a little snippet of my code obfuscated with https://obfuscator.io/ and it worked seemingly perfectly.

My original code:

  function resizeImage(img) {

https://obfuscator.io/ produces a similar result, perhaps that's all they used.