Skip to content

How to detect device farm fraud and prevent automated attacks

Learn what device farms are, which detection signals work, and how to deploy tiered enforcement to stop automated abuse while reducing false positives.

5 min readDeepak RajGuidesUpdated 18 March 2026

In this article

Device farm fraud operates as an advanced threat which results in marketing budget losses and destroys data precision for online businesses. The attackers use thousands of actual devices to create humanlike activity patterns which conventional security systems cannot detect, resulting in potential financial and analytical risks for your business.

What is Device Farm Fraud?

A device farm is a large collection of devices (usually mobile phones or tablets) that are physically located in one area, and are connected to the internet, allowing them to be used for both manual and automated tasks across hundreds or thousands of devices simultaneously.

The purpose of a device farm is to deceive apps and websites into believing they are communicating with legitimate, unique users. A good example of how this is done is when criminals use device farms to create thousands of fake social media accounts; download apps in order to inflate their rankings; or click on digital advertisements in order to take advantage of advertising revenue.

Real-world example: An app developer pays for a "user acquisition" campaign. Instead of real people downloading the app, a device farm in another country automates 10,000 installs. The developer pays for the "users," but these "users" will never spend money or engage with the app.

Why Device Farms Are Hard to Detect

Most basic security systems look at IP addresses or basic cookies. Fraudsters know this. In a device farm, they use sophisticated setups to hide their tracks:

Unique Hardware: These are real devices, not emulators. This makes them look "human" to basic checks.

IP Rotation: They use residential proxies or VPNs to make every device appear to be in a different city or home.

Resetting Identifiers: Fraudsters constantly clear caches and reset Advertising IDs (like IDFA or GAID) to appear as brand-new users every few minutes.

Because the traffic looks like it is coming from legitimate hardware and diverse locations, traditional fraud detection often lets them through.

Signs of Device Farm Fraud

While they are hard to spot, device farms leave behind "digital breadcrumbs." If you see these patterns, you are likely facing a coordinated attack:

Strange Battery Patterns: Most real users have varying battery levels (e.g., 42%, 88%). Device farms are often plugged into constant power, showing 100% battery or a "charging" state 24/7.

Identical Hardware Models: You might notice a sudden surge of 500 users all using the exact same older model of a budget Android phone.

Impossible Movement: If a "user" is supposedly in New York but their device sensors show zero physical movement or an impossible tilt angle, it’s likely a stationary device on a rack.

High Action Velocity: A single "person" performing 50 clicks in 10 seconds across different apps is a major red flag for automation.

How to Detect Device Farm Fraud Effectively

To stop these attacks, you need a multi-layered approach that goes beyond the surface level.

1. Advanced Device Fingerprinting

Device fingerprinting collects thousands of tiny details about a device, such as its screen resolution, OS version, and hardware components. Even if a fraudster resets their ID, the physical "fingerprint" of the hardware remains the same. This allows you to see that 1,000 "different" users are actually the same 10 devices being reused.

2. Behavioral Signals

Real humans don't interact with apps perfectly. They make mistakes, they pause, and they move their phones. By analyzing how a user types, swipes, or holds their phone, you can distinguish a real person from a script or a worker in a farm.

3. Network Intelligence

Fraudsters use proxies to hide their location. Advanced detection checks if an IP belongs to a data center or a known proxy network rather than a real home internet service provider (ISP).

How DeepID Helps You Stay Safe

DeepID provides the advanced technology needed to spot device farms before they damage your business. Instead of just blocking IPs, DeepID uses deep device intelligence to verify the integrity of every user.

Identify Reused Hardware: Our SDK creates a persistent device ID that survives factory resets and OS updates. If a device has been seen in a fraud farm before, we flag it instantly.

Detect Automation Tools: DeepID scans for the presence of "app cloners," emulators, and automation scripts that device farms rely on.

Reduce False Positives: Because we use high-fidelity signals, we can accurately block the bad actors without bothering your real customers.

By focusing on outcomes like higher ad ROI and cleaner user data, DeepID helps fraud teams and product managers sleep better at night.

Best Practices for Fraud Prevention

Prevention is a continuous process. Here are three steps you can take today:

Monitor Your Data: Look for "clumps" of traffic. If 20% of your new users come from the same ISP or use the same phone model, investigate immediately.

Verify New Installs: Use a real-time SDK to check device integrity at the moment of the first open. This is when most device farm fraud occurs.

Update Your Rules: Fraudsters change their tactics weekly. Ensure your detection logic is updated frequently to catch new types of spoofing.

Conclusion

Device farm fraud is an organized activity; however, it is not an invisible one. Moving away from basic checks and towards more sophisticated device fingerprinting and behavioral analysis is the way to protect your revenue. Being one step ahead of the fraudsters is the way to guarantee that your growth is coming from genuine and high-value users.

More from the blog.

Dated articles on the rules, the attacks and how DeepID is built.

  • One decision id, three places

    Every DeepID decision carries one id: the same in the app that acts on it, in the event your FRM receives and in the decision log an auditor reads. Here is why, and how it is wired.

    2 min read

  • SMS OTP is not banned. Three things that are changing

    No regulator in DeepID’s markets has banned the SMS one-time password. What is changing is where it is enough: at login, for high-risk transactions, and as the floor under every payment.

    2 min read

  • Why a coached payment passes every check

    In a coached payment the real customer signs in on their own phone and approves the payment themselves. Each check does its job, and the money still leaves. What changes the outcome is reading the session as a whole.

    2 min read

See DeepID on a real phone.

We show your fraud, security and engineering leads how DeepID would run your sign-up, login or payment journey, then plan a pilot on your own traffic.