Anubis gains WebAssembly support after a year-long development

The concrete change is that Anubis now contains WebAssembly code after a year of work. Previously the system relied solely on its JavaScript-based proof-of-work challenge. This shift means the codebase now includes a WebAssembly module alongside the existing JavaScript.

Adopting WebAssembly entailed a year of development effort, which represents the primary cost. No other resources such as licensing fees or third-party services are mentioned in the material, so the cost is measured in engineer time spent on the integration.

The integration does not eliminate the system’s dependence on modern JavaScript features; the lead extract notes that Anubis requires such features and that disabling plugins like JShelter will prevent the challenge from loading. Therefore, if a user’s browser blocks those features, the WebAssembly addition does not restore functionality.

Because the WebAssembly work is described as part of a placeholder solution, the system still relies on the proof-of-work challenge while longer-term fingerprinting techniques are developed. Thus, the WebAssembly component does not yet remove the need for the challenge page or guarantee uninterrupted service for legitimate visitors.

Overall, the event signals that the Anubis team considers WebAssembly important enough to allocate a full year to its inclusion, but the practical impact on end-users remains limited by the existing JavaScript dependencies and the placeholder nature of the current anti-bot approach.