A new Quarks App Protect version is now available, supporting WebAssembly.
What is WebAssembly?
WebAssembly can be, in theory, targetted through many source languages, C/C++, Rust or AssemblyScript being commonly used.
While WebAssembly is designed to be secure as it is executed in a sandbox environment, this design does not protect against reverse engineering. Indeed, when WebAssembly binaries are run client-side, attackers can easily access and extract these, which can then be reverse-engineered.
Obfuscation passes can be applied to WebAssembly binaries to slow down attackers and protect valuable intellectual property.
Organisations that intend to develop applications targeting WebAssembly should look into WebAssembly obfuscation to address this risk of application reverse-engineering.
One of the most compelling use cases of WebAssembly is that it enables organisations to port existing desktop applications to WebAssembly by reusing the existing codebase, as it supports C and C++ as source languages. By leveraging this capability, a software editor can effectively create new revenue streams thanks to the subscription possibilities that a web application entails. These organisations can then use Quarks App Protect to protect WebAssembly applications and consequently, these new revenue streams.
What does Quarks AppShield accomplish?
By supporting WebAssembly as a compilation target with Quarks App Protect, web developers can now obfuscate their application, choosing from our catalogue of more than 25 possibilities.
Moreover, Quarks App Protect can easily be integrated into existing compilation processes as it integrates into standard WebAssembly toolchains (e.g. emscripten).
To learn more about Quarks App Protect and its capabilities, go to the following page:
If you wish to see Quarks App Protect in action, contact our team for a product demonstration by filling out the form at the following address: