JScrambler is introducing new self defending capabilities for HTML5/JavaScript applications with its release of JScrambler 3.5. Self defending offers an active protection technique which provides apps with the capability to react to source code modifications (tampering) and debugging at
runtime.
Without protecting code, pirates can violate license agreements, steal secret algorithms, steal code and to reuse it, and leak altered versions to the Internet.
JScrambler enables developers to conceal as much as possible including the logic of an application, what information is gathered from the user, how it is processed on the client-side, and how it is sent to the servers-side.
Since JScrambler’s obfuscation introduces a certain level of randomness, allowing developers to explore code morphing techniques, which can be vital in precluding attack automation.
The advanced JavaScript
obfuscation hides the algorithm and frustrates anyone that try to steal it. And developers can lock code to a predefined list of domains. If someone places it anywhere else, it will not execute correctly.
JScrambler 3.5 also introduces another feature which enables developers to drive JScrambler transformations on particular source code blocks. With simple annotations it is now possible to disable or just switch between protection templates on specific source code loops or flows.
Projects can be managed from the a web interface or web
API which can be easily integrated on deploy script.