Website operators have begun deploying Anubis, a Proof‑of‑Work shield designed to curb aggressive AI scrapers. The system forces visitors to solve a lightweight hash challenge before the server delivers content, raising the cost of bulk crawling while leaving casual users unaffected. Administrators report occasional downtime as legitimate traffic stalls behind the challenge page.

The approach mirrors Hashcash, an early anti‑spam technique that taxed email senders with computational work. At single‑user scale the extra CPU cycles are negligible, but when thousands of bots request pages simultaneously the aggregate load becomes prohibitive. Developers hope the scheme will buy time to implement more precise fingerprinting, such as detecting headless browsers through font‑rendering anomalies.

A practical hurdle is that Anubis relies on modern JavaScript features that privacy extensions like JShelter block. Users must disable such plugins to pass the challenge, which can frustrate security‑conscious visitors. Nonetheless, the trade‑off highlights a growing arms race: site owners sacrifice a slice of usability to protect bandwidth and data from automated extraction.

While Anubis does not eliminate scraping, it forces attackers to allocate compute resources, raising the economic barrier. Sites that can tolerate occasional access delays may find the system a viable stopgap until more sophisticated bot‑detection methods mature.