Projects
Burn Racist Giga
Digital Hacktivism & Network Architecture
Burn Racist Giga is a digital hacktivism campaign designed to combat the rising tide of xenophobia and extreme right-wing hostility on Italian social media. Commissioned by Rolling Stone Italy and Serviceplan Group Italia, the initiative targeted the primary weapon used by extremists to spread hate: their mobile data connection. By tricking racists into visiting a disguised mini-site, the campaign aimed to exhaust their monthly data limits, effectively removing them from the internet and silencing their ability to distribute toxic propaganda.
The initial campaign strategy relied on a digital honeypot: a landing page (riprendiamocisubito.com) advertised to far-right groups, filled with fake extremist videos. The concept assumed that by forcing these users to watch uncompressed, massive video files without Wi-Fi, the site would rapidly burn through their mobile data plans. However, while the strategic intent was powerful, the initial technological approach was fundamentally flawed.
The Technical Roadblock
The core problem with relying on large video files to drain data is human patience. Standard HTTP requests respect browser throttling, meaning high-resolution videos require significant bandwidth to load. If the video buffered or loaded too slowly, the targeted users would simply close the browser window before any meaningful data volume was consumed. A passive video player could not effectively sabotage a data plan; the project required an invisible, aggressive architectural exploit that bypassed standard browser limitations entirely.
The Solution
To execute true hacktivism, STD.DEV discarded the video-bloating concept and engineered a weaponized background process. Daniel Kuhnlein developed a custom Node.js server that established a persistent, bi-directional WebSocket connection with the target’s smartphone. Instead of loading media, the server continuously blasted 512KB binary buffers of randomized float data directly to the client. Because the data was pure mathematical noise, network compression algorithms failed, resulting in a relentless, unthrottled data-draining loop that operated entirely in the background.
Impact
This aggressive architectural pivot transformed a conceptual idea into a highly effective digital weapon. By exploiting Android lifecycle management, STD.DEV ensured the data leeching continued unabated even when the target’s phone screen was turned off. The silent execution burned through over 5,000 gigabytes of mobile data in just 10 days, successfully taking more than 800 targeted extremists offline. Following the reveal, the campaign generated 28 million media contacts and drove a 1,500% traffic surge to RollingStone.it. The unprecedented exploit earned global recognition, securing Gold at the Epica Awards, Golden Drum, and ADCI, alongside accolades at Cannes Lions and The One Show.
Burn Racist Giga demonstrates that effective digital protest requires uncompromising technical execution. By replacing passive content delivery with an active, programmatic network exploit, STD.DEV ensured the campaign’s success. This uncompromising approach to data manipulation was delivered across two core components:
1. Bi-Directional Flooding Architecture
Architecting a highly aggressive client-server loop designed specifically to bypass network optimization. A custom Node.js backend continuously generated massive Float64Array buffers filled with pure cryptographic noise (Math.random()), ensuring internet service providers could not compress the payload. Simultaneously, an invisible client-side script maintained a persistent WebSocket handshake. The moment the target device received a data buffer, the client immediately dispatched a response to the server, instantly triggering the next payload drop to create an infinite, unthrottled data-draining loop.
2. OS-Level Background Exploit
Bypassing standard mobile browser pausing mechanics by exploiting Android background execution vulnerabilities. STD.DEV engineered the connection to remain active and prioritized even when the smartphone’s screen was turned off, ensuring the data leeching process continued silently and relentlessly as long as the browser application remained unkilled in the device’s memory.
The technical reality of Burn Racist Giga proves that code can be a profound tool for direct action. By understanding the deep-level mechanics of network transmission and browser lifecycles, STD.DEV transformed standard web protocols into an instrument of defense—proving that true digital intervention requires moving beyond the surface level to command the infrastructure itself.
Credits
Client
Rolling Stone Italy
Creative Direction & Social Media Campaign
Serviceplan Group Italia
Exploit Engineering & Full-Stack Development
STD.DEV (Daniel Kuhnlein)
Cloud Infrastructure & AWS Deployment
Develon
How did the Burn Racist Giga campaign initially attempt to exhaust users' mobile data?
The initial campaign strategy relied on a digital honeypot, a landing page advertised to far-right groups filled with fake extremist videos, assuming that forcing users to watch uncompressed, massive video files without Wi-Fi would rapidly drain their mobile data plans.
What was the fundamental flaw in the initial technological approach of the Burn Racist Giga campaign?
What technology was engineered to replace the video-bloating concept in the Burn Racist Giga campaign?
How did the revised technical solution ensure data draining continued even when the phone screen was off?
What was the impact of the Burn Racist Giga campaign in terms of data usage and user impact?
What were the key components of the Burn Racist Giga's technical execution?
How did the custom Node.js server ensure the data payload could not be compressed?
What was the strategic goal of the Burn Racist Giga campaign?
What business outcomes did the Burn Racist Giga campaign achieve beyond its primary objective?
Who was responsible for the exploit engineering and full-stack development of the Burn Racist Giga campaign?
Why is uncompromising technical execution emphasized as crucial for effective digital protest, according to the Burn Racist Giga case study?
What was the purpose of the invisible client-side script in the Bi-Directional Flooding Architecture?
