What it is
An emulator is a program that imitates an entire phone inside a computer: its processor, its operating system and its sensors. The iOS simulator works differently, because it runs apps built for the computer, but the result is similar: the app runs outside a physical iOS device.
There is a third variant: virtualization on the phone itself. These are apps that create an isolated environment to run copies of other apps, for example to have several accounts of the same app on a single device. We come back to it at the end, because it is a case Pulse does not cover specifically.
Development and testing teams use emulators every day, as part of their work. The problem appears when your production app, the one your customers use, runs on one.
Why it matters
An emulator gives an attacker two advantages that are hard to get on a real phone.
Full control. They can inspect memory, save and restore the device state, change any system property and attach analysis tools without restrictions. It is the most comfortable environment for studying your app.
Scale. They can run dozens of virtual devices at once, each with a “new” identity, and automate them. That is the engine behind much of the fraud against consumer apps:
- creating accounts in bulk to abuse promotions, coupons or welcome bonuses;
- piling up loyalty points or rewards automatically;
- testing stolen credentials against your service;
- in games, running bots or account farms.
If your business model gives something away to every new account or device, knowing that a session comes from an emulator is first-rate information.
What Pulse does
Pulse identifies signs of execution in Android emulators and the iOS simulator. This information supports session assessment and environment-specific responses. It does not by itself establish automation or fraud.
Decisions about promotions, payments or rewards belong to your application and backend business controls. Pulse signals can provide context but do not implement those decisions automatically.
How it responds
The policy can record the signal, notify the application or trigger termination, where the response is applicable. Actions such as requesting additional verification, restricting an operation or protecting content require implementation in your application.
Local detection and response can work offline. Pending reports are sent when connectivity returns; the console shows the data it receives. History should not be interpreted as a guaranteed record of all device activity.
Before applying restrictions in production, assess detections on the devices and versions used by your organization. Observation mode supports investigating signals and potential false positives without enabling their restrictive response. Define separate policies for development, testing and production.
Scope and limitations
- Virtualization within other applications. Specific coverage is not offered for every environment that runs applications inside a physical phone.
- Adapted environments. A modified environment may evade detection. Coverage must be validated for the use case.
- Automated physical devices. These are not emulators; additional backend behavior and abuse controls are required.
- Authorized testing. Maintain policies that allow development work without carrying those settings into production.