JavaScript (JS) is a versatile language for creating interactive websites, but it’s also easily viewable, which can expose sensitive parts of your code to anyone. Encrypting or obfuscating JavaScript…

SystemWeakness's platform is  dedicated to cybersecurity education and awareness, offering insights into common security vulnerabilities, attack techniques, and risk mitigation strategies. Through articles, tutorials, and security advisories, SystemWeakness offers insights into securing software applications, networks, and systems from cyber threats. Readers can learn about secure coding practices, penetration testing methodologies, and incident response procedures to strengthen their cybersecurity posture and protect against cyber attacks.

System Weakness

Encrypting JavaScript code adds a layer of protection to your website, making it harder for unauthorized individuals to understand or reverse-engineer the code. Techniques such as obfuscation and minification are commonly used, along with encryption libraries for sensitive data. Tools like SafeLine WAF can further enhance security through dynamic encryption, real-time threat detection, and zero-day protection. Combining JavaScript encryption with HTTPS and other security measures offers a comprehensive defense for your web assets.

How to Encrypt JavaScript Code for Web Security

2. Techniques for JavaScript Code Encryption

3. Using SafeLine WAF for JavaScript Encryption and Web Security

How about dont have sensitive code run on your clients machine lmao.
Anything runnable and readable in the browser is not safe.

Well this is not safe at all. And I suppose a lot of people might misunderstand it. Firstly, if the code is going to be run by a browser anyway then it must be decrypted - so it would be available as plain on some level of execution. Secondly, it’s hardly encryption just obfuscation. Thirdly, NEVER but NEVER store sensitive data in code.

Hmm… Isn’t this just obfuscation at 3a? 🤔

The code should not have to be full encrypted on the client side, it is safer on backend for controlling data access, API, auth management, etc

I just read (skimmed) through it. It basically tells you to make it harder for hackers, not impossible. The second paragraph basically says, “… obfuscating …” and suggests some of the things people are saying in the comment section down below
.