What it is
A tampered app is a copy of your app that someone changed: they removed a check, unlocked paid features, added ads or malicious code, or bundled an instrumentation tool. Distribution may use channels not authorized by the application owner.
A cloned app takes another route: it imitates yours, with its name, its icon and its screens, so your users believe it is the original. Sometimes it is a modified copy of your own package; other times it is a different app that merely looks like it.
Why it matters
Modified copies and clones affect almost any app with something of value in it:
- Fraud. Versions that skip limits, payments or identity checks.
- Piracy. Premium content or paid features available for free.
- Credential theft. Clones that ask for usernames and passwords in your brand’s name.
- Traffic that isn’t yours. Your APIs receive requests from an app you do not control, which can behave in any way.
To your backend, a request from a modified copy looks the same as one from your real app. That is why the question “is this really my app?” has to be answered on the device and proven to the server.
What Pulse does
Pulse detects signals related to application integrity and origin, depending on platform and configuration. An off-store installation is not necessarily a malicious copy: enterprise and testing channels must be included in the assessment.
Attestation can complement backend operation controls with additional integration. Pulse is not a service for discovering applications that imitate your brand.
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
- Independent imitations. An unrelated application that imitates your brand without integrating Pulse is outside the product’s local detection scope.
- Application takedowns. Reporting and removing clones from stores or websites requires external processes.
- Legitimate distribution. Assess beta releases and enterprise channels before restricting installation sources.
- Secure development. Pulse does not replace protection of publishing credentials, obfuscation or backend authorization.