Damru
♥ Donate ★ GitHub
Features

What Damru does

Damru spoofs device identity beneath the browser on a real Android stack — so there is no JavaScript patch surface to detect. Here is what the framework gives you.

What are Damru's stealth features?

Damru's features are the spoofing layers that rewrite a browser's device, GPU, hardware, and network fingerprint at the operating-system and binary level on a real Android stack, plus the tools to run and watch those instances.

Before listing them, it helps to define the approach: a "feature" in Damru is not a JavaScript patch applied to a desktop browser. Each one operates below the page — in the Android OS, in binaries, or over the Chrome DevTools Protocol — so detectors have nothing injected in the DOM to read. The eleven capabilities below split into two groups: stealth layers that change the fingerprint, and operational tools (Damru UI and Damru View) that let you manage and observe your instances.

Zero JavaScript injection

Fingerprint changes happen at the OS, binary, and CDP layers — never in page context. There is no injected script in the DOM for detectors to read.

155 real device profiles

Genuine Samsung, Pixel, Xiaomi, OPPO and Realme hardware fingerprints — real mobile values, not desktop Chromium dressed up as mobile.

GPU binary patching

Physically patches Vulkan / GLES .so files so the GPU fingerprint matches the spoofed device.

Hardware spoofing

CPU cores, RAM (via syscall hooks), and touch points are overridden at the system level.

TLS / JA3 randomization

Around 184 unique network fingerprints from a single binary.

Chrome version rotation

Dynamic WebView alignment keeps the browser version consistent with the profile.

WebRTC & IPv6 leak blocking

Kernel-level prevention of IP leaks that would expose the real network.

Display / density spoofing

Native Android wm size / density overrides for authentic screen metrics.

Multi-container pooling

Orchestrate many Redroid workers in parallel for automation and scraping at scale.

Local control panel (Damru UI)

A local-only web dashboard for setup, worker control, a Work Lab, and logs — manage and inspect instances without writing throwaway scripts.

Live browser viewer (Damru View)

Stream a live scrcpy view of any running worker to watch automation in real time, with a watch-only mode that is safe during a run.

Manage and watch your instances with Damru UI + Damru View →

How do these features map to a fingerprint? (feature → layer → what it spoofs)

Each stealth feature operates at a specific layer — page, binary, OS, kernel, or network — and changes one part of the fingerprint without leaving a detectable injection.

This entity-attribute table shows which layer each feature acts on, what it spoofs, and why none of them leave a script for a detector to read.

FeatureLayerWhat it spoofsDetectable?
Zero JavaScript injectionCDP / pageNothing — the page is untouchedNo injected surface
155 real device profilesProfile dataDevice model, brand, hardware identityNo — real values
GPU binary patchingBinary (.so)Vulkan / GLES renderer stringsNo — matches the device
Hardware spoofingOS / syscallCPU cores, RAM, touch pointsNo — system-level
TLS / JA3 randomizationNetworkTLS handshake / JA3 signatureNo — ~184 fingerprints
WebRTC & IPv6 leak blockingKernelReal IP exposureNo — leaks blocked
Display / density spoofingAndroid wmScreen size, density, DPINo — native override

How do these layers fit together?

The layers stack into one pipeline — Redroid runs real Android, native hooks and binary patches change the fingerprint, and Chrome is driven over CDP — so the spoofing is already complete before a page loads.

Each feature reinforces the others: a real device profile is only convincing if the GPU binary, hardware values, and TLS signature all agree with it. Damru keeps them internally consistent. See how the layers fit together or compare Damru against other tools.

FAQ

Does zero-JavaScript injection mean Damru is undetectable?

No tool is absolute, but zero-JS injection removes the most common detection surface. Because Damru changes the fingerprint at the OS, binary, and network layers before the page loads, there is no injected script in the DOM for a detector to read — unlike JavaScript-hook tools.

Which device fingerprints does Damru spoof?

Damru ships 155 real Android device profiles covering Samsung, Google Pixel, Xiaomi, OPPO and Realme hardware, each with authentic device, GPU, CPU, RAM, screen, and touch values rather than synthetic desktop ones.

Does Damru have a dashboard or live viewer?

Yes — Damru UI is a local-only web dashboard for setup, worker control, a Work Lab, and logs, and Damru View streams a live scrcpy view of any running worker. Both are covered on the instance manager page.