Fake Apps: How Copies of Your Brand Are Found and Removed
Skip to content

Fake Apps

A fake app is a mobile application that uses an organization’s name, logo or design without permission, so that customers or staff install it believing it is genuine.

On this page

A repackaged app is a copy of the organization’s real app that someone has unpacked, altered and signed again, usually with code added to collect data. Most fake apps circulate outside the official stores, on APK download sites, in public code repositories and behind links sent by text message or chat, although some reach the official stores before they are removed.

This guide is written for the teams that protect a brand and its customers: security, fraud, digital and legal. It covers how fake apps are built and spread, how to find and confirm them, how to get them removed, and how to start a program.

Kinds of Fake Apps

Fake apps differ in how much of the real product they copy. Some reuse only the name and icon, while others are the genuine app with a few lines of attacker code inside. The kind matters because it changes how the app is detected and which removal route applies.

  • Lookalike app: A new app is built from scratch with the brand’s name, logo and colors, and it usually offers little beyond a sign-in screen or a payment form.
  • Repackaged app: The genuine app is decompiled, modified and rebuilt, so it looks and behaves like the original while it also runs hidden code.
  • Fake companion app: An app claims to be an add-on to the real product, such as a “security update”, a rewards app or a verification tool that the customer is told to install.
  • Impostor developer account: A store account takes a name close to the organization’s own, which makes every app it publishes look official.
  • Fake beta or test build: A pre-release build is shared through a testing channel or a download link, which can bypass the normal store review.
  • Web app posing as an app: A website is saved to the home screen with the brand’s icon and opens without a browser address bar, so it feels like an installed app.

A single campaign often mixes these. A fake website, a lookalike domain and an APK download can all point at the same server, which is why the app is usually only one part of what needs to come down.

Why Brands Get Copied

An app carries more trust than a web page. A customer who installs what looks like their bank’s app will enter a password, approve permissions and accept prompts without the caution they bring to an unexpected email. Attackers copy apps to borrow that trust.

  • Credential theft: The app shows a copy of the real sign-in screen and sends whatever the customer types to the attacker.
  • One-time code interception: The app reads text messages or notifications to capture the codes used for sign-in and payment approval.
  • Payment and investment fraud: The app takes deposits into accounts the attacker controls and shows a balance that never existed.
  • Device takeover: The app requests accessibility or screen-capture rights that let the attacker watch and operate the phone.
  • Advertising and subscription fraud: The app earns money from ads or premium-rate charges on the strength of a familiar name.

In July 2022 the FBI warned financial institutions that criminals were using the names, logos and other identifying information of legitimate US businesses in fraudulent cryptocurrency investment apps. Its Private Industry Notification counted 244 victims and estimated losses of about $42.7 million, and it noted reputational harm to the firms whose names were used.

Banks, payment providers, retailers with loyalty programs, telecommunications carriers, government services and any organization whose app handles money or identity are the usual targets. A brand that has never released an app can still be copied, because customers have no genuine app to compare against.

How Fake Apps Reach Users

A fake app needs a way onto the phone. The official stores review submissions, so attackers favor channels with less checking and use social engineering to move people there.

  • Official stores: Lookalike and repackaged apps are submitted under impostor developer accounts and stay listed until reported or detected.
  • APK download sites: Third-party sites mirror Android installation files, and copies of popular apps appear there with altered code.
  • Public code repositories: Attackers host installation files on release pages and in repositories, where downloads come from a trusted domain.
  • Text messages and chat: A message says an account is locked or a parcel is held and links to a page that offers the “required” app.
  • Search results and ads: Paid ads and pages that rank for the brand name lead to fake download pages.
  • Social media and messaging groups: Posts, fake support accounts and group chats share download links with people who already follow the brand.
  • Beta-testing channels: Victims are walked through installing a pre-release build that skips the standard review.

The FBI described that last route in an August 2023 public service announcement, noting that criminals reach victims through romance and phishing approaches and that the apps may use names, images or descriptions similar to popular apps. Joint guidance from 2025 adds that placing trojanized apps in official stores lends them a sense of legitimacy.

Inside a Repackaged App

Every Android app is signed with a certificate before it can be installed. Android’s documentation explains that when an update arrives, the system compares its certificate with the installed version’s and allows the update only if they match. An app signed with a different certificate needs a different package name and installs as a separate app.

This makes the signing certificate the most reliable marker of a genuine build. Anyone who repackages an app lacks the original private key, so the copy carries the attacker’s certificate. The copy can reuse the real icon, title and screens, and it still cannot pass itself off as an update to the genuine app already on a phone.

What the attacker adds depends on the goal.

  • Overlay screens: The app draws a fake sign-in or card form on top of the real app or another banking app.
  • SMS access: Google Play restricts SMS and Call Log permissions to apps that are the device’s default SMS, Phone or Assistant handler, with limited approved exceptions, so a fake app that wants those codes may ask to become the default messaging app.
  • Accessibility abuse: Accessibility rights let an app read the screen and press buttons, and Android may restrict this setting for a newly installed app until the user chooses to allow it.
  • Notification reading: Access to notifications exposes codes and messages from other apps.
  • Remote command channel: The app connects to a server or messaging bot to send captured data and receive instructions.

These permissions are the clearest technical tell. A brand’s real app rarely needs to be the default SMS app, so a copy that asks for that role deserves immediate attention.

Store Policies on Impersonation

Google Play and the Apple App Store each prohibit apps that pretend to belong to someone else, and each gives rights holders a route to complain.

Google Play’s Impersonation policy covers apps and developer accounts that mislead users by posing as another developer, company, entity or app, or by implying a relationship or authorization that does not exist. Its examples include copying a business’s logo to appear official and using titles or icons close enough to an existing product to confuse users. Its Intellectual Property policy prohibits trademark infringement and directs rights owners to a trademark complaint form, with separate routes for counterfeit goods and copyright.

Apple’s App Store Review Guidelines treat impersonation under Copycats. Guideline 4.1 says submitting apps that impersonate other apps or services violates the Developer Code of Conduct and may lead to removal from the Apple Developer Program, and that another developer’s icon, brand or product name cannot appear in an app’s icon or name without approval. Guideline 5.2.1 bars protected third-party material such as trademarks without permission, and Apple accepts intellectual property claims through a web dispute form.

Store Rule that applies Route for the brand owner
Google Play Impersonation policy; Intellectual Property policy on trademark infringement. Trademark complaint form, counterfeit notice or copyright notice, after contacting the developer where that is safe.
Apple App Store Guideline 4.1 Copycats; Guideline 5.2.1 on protected third-party material. Intellectual property dispute web form, with proof of the mark and the infringing listing.
Apps distributed outside the stores Platform rules apply only where the platform has a role, such as Google Play Protect and Apple notarization. Reports to the hosting provider, the code platform, the domain registrar, browser blocklists and the authorities.

Recent platform changes also affect apps distributed outside the stores. In the European Union, Apple allows iOS apps from alternative marketplaces and authorized developer websites, and its notarization review applies to every app regardless of distribution channel.

Google’s Android developer verification ties apps to a verified developer identity. Google set September 30, 2026 as the start date in Brazil, Indonesia, Singapore and Thailand, beginning with installs from participating app stores, and plans coverage of all apps on certified Android devices and a worldwide rollout in 2027.

Signs a Listing Is Fake

Customers judge an app by its name and icon, which are the easiest parts to copy. The April 2025 joint advisory from the UK’s NCSC, ASD’s ACSC, the FBI, the NSA and other partners makes the point directly: the app title, package name and icon can all imitate the real app, so they should not be relied on alone.

A reviewer checks the details that are harder to fake, in this order.

  1. Signing certificate: The certificate fingerprint of an Android installation file either matches the organization’s own app signing certificate or it does not.
  2. Developer account: The publisher name, contact address and website should match the organization’s registered details exactly.
  3. Package or bundle identifier: A genuine app keeps the same identifier for life, so a near match such as an added word is a strong sign of a copy.
  4. Permissions: Requests for the default SMS role, accessibility, notification access or device administration that the real app never makes point to added code.
  5. Network destinations: The app should talk only to the organization’s own domains and named service providers.
  6. Listing history: A recent publish date, few installs and reviews written in a burst are typical of a fresh copy.
  7. Function: The FBI advises treating apps with limited or broken functionality with skepticism, and a fake often offers only a sign-in screen.

A listing that fails on the certificate or the developer account is almost certainly unauthorized. The remaining checks show what the copy does and how urgently it needs to come down.

Finding Fake Apps

Fake apps surface in many places at once. A monitoring program watches every channel from the earlier section and matches what it sees against what the organization actually publishes.

The starting point is an inventory of the genuine apps: names in each language, package and bundle identifiers, developer account names, icons and the signing certificate fingerprints. Every candidate found is compared with this list.

  • Store searches: Searches cover the brand name, product names, common misspellings and the icon, across the official stores and regional stores.
  • APK site watch: Mirrors are checked for new uploads that carry the brand’s name or package identifier, and each file’s certificate is compared with the genuine one.
  • Code repository search: Release pages and repositories are searched for installation files and source code that name the brand or its servers, the same sources covered in our guide to secrets in public code repositories.
  • Domain and page watch: New domains and pages that offer an app download for the brand often appear before the app spreads.
  • Social, ads and messaging: Posts, ads and channels that share download links are tracked back to the file they serve.
  • Customer and staff reports: A simple reporting address for suspicious apps catches copies that arrive by text message, where outside monitoring cannot see.

The organization’s own app can report copies too. Google’s Play Integrity API returns a verdict of UNRECOGNIZED_VERSION when the certificate or package name does not match Google Play’s records, and Apple’s App Attest lets a server confirm that a request comes from a valid instance of the app. A sudden rise in failed checks, or sign-ins from app versions the organization never shipped, is a lead worth following.

Confirming and Scoring a Finding

Monitoring produces candidates, and some will be harmless: an old version on a mirror, a reseller’s listing or an unrelated app with a similar name. An analyst confirms each one before it is escalated, which keeps takedown requests credible and keeps the brand team from chasing noise.

Confirmation means taking the file apart in an isolated environment. The analyst records the certificate, permissions, embedded addresses and strings, then runs the app on a test device to watch what it asks for and where it sends data. A server or bot address found inside the app often leads to the rest of the campaign, such as other download domains on the same host, which are reported along with the app.

Each confirmed app is then scored so the most harmful ones move first.

Factor Higher priority when
Live status The download link works and the command server responds.
What it collects It captures passwords, one-time codes, card details or full device control.
Who it targets It aims at customers’ accounts or money, or at staff with access to internal systems.
How it spreads It is promoted through text messages, ads or an official store listing.
Age and hosting It is newly published, or hosted where removal requests are slow to act.
Reach Install counts, reviews or link clicks show people are already using it.

A copy that is live, steals one-time codes and is promoted by text message goes to the top. An abandoned upload on a mirror with no working server is recorded and watched.

Removal and Reporting

Removal works best when every part of the campaign is reported together. Taking down one listing while the download page and command server stay up only invites the next upload.

Evidence comes first, because pages and files disappear once attackers notice attention. The order below suits most cases.

  1. Preserve evidence: Save the listing, screenshots, the installation file and its hash, the certificate, the download page and the domain’s registration and hosting records.
  2. Report the listing: Send the store a complaint under its impersonation or intellectual property route, citing the policy and attaching proof of the trademark.
  3. Report the hosting: Ask APK sites, code platforms and web hosts to remove the file and the download page under their abuse terms.
  4. Report the domains: Send registrars and hosting providers the evidence for the download domain and the command server.
  5. Request blocking: Submit the domains and URLs to browser blocklists and block them on the organization’s own mail and web gateways.
  6. Notify authorities: Report fraud to the national cyber agency or police, such as the FBI’s IC3 in the United States or ASD’s ReportCyber in Australia.
  7. Follow up: Track each request until the item is offline, then keep watching for the same certificate, package name and servers in new uploads.

Repeat uploads are common, so the certificate and server addresses from a confirmed copy are kept as matching rules.

Protecting Customers and Staff

Removal stops new installs. People who already installed the app need their own response, and customers need a simple way to tell real from fake next time.

The FBI’s 2022 notice recommends that financial institutions tell customers whether they have a mobile app at all, warn them about fake apps and explain how to report one. The NCSC-led advisory adds that organizations should have a procedure to notify customers who installed a malicious app, with clear removal steps.

  • Publish the official list: One page on the main website names each genuine app, its developer account and direct store links.
  • Link from the website only: Customers are told the organization never sends app download links by text message.
  • Check app integrity in the app: Play Integrity and App Attest checks on sign-in and payment let the backend refuse or step up requests from unrecognized copies.
  • Warn inside the real app: The advisory recommends that developers tell users when they are running an unofficial version.
  • Reset affected accounts: Customers whose sign-ins came from a fake app get a password reset, revoked sessions and a review of recent payments.
  • Cover staff devices: Managed phones restrict installs from outside the stores, so a fake internal or partner app cannot reach corporate data.

Staff are targets too. A fake app posing as the company’s own expense, HR or authenticator app can capture corporate credentials, and the same impersonation tactics appear in brand and executive impersonation campaigns on social media.

A Fake App Case Followed Through

Acme Corp is a lender with a mobile app on each official store, published under the developer name Acme Corp and served from acmecorp.com. Its security team runs monitoring across stores, APK sites, code repositories and new domains.

  1. Detection: Monitoring flags an Android file named “Acme Mobile Secure” on the release page of a public code repository. A new domain, acmecorp-verify[.]com, offers the same file with a message that customers must install a “security update” to keep their accounts open.
  2. Confirmation: An analyst downloads the file into an isolated environment and finds that the package name adds the word “secure” to Acme’s real identifier, the certificate fingerprint differs from Acme’s signing certificate, and the app asks to become the default SMS app. On a test device it shows a copy of the Acme sign-in screen and forwards incoming text messages to a messaging bot.
  3. Scoring: The app is live, captures passwords and one-time codes, targets customers’ money and spreads by text message, so it goes to the top of the queue.
  4. Containment: The security team blocks acmecorp-verify[.]com on Acme’s gateways and passes the bot and server details to the fraud team. Fraud finds a handful of customer sign-ins from new devices immediately after code requests, locks those accounts and calls the customers.
  5. Removal: The team files abuse reports with the code platform, the registrar and the web host, submits the domain to browser blocklists and reports the fraud to the authorities. Each request carries the evidence pack, and the team follows each one until the file and page are offline.
  6. Recovery: Acme posts a notice on its website listing its genuine apps and repeats that it never sends download links by text. Two weeks later a copy with the same certificate appears on an APK mirror, and it is matched and reported the day it is found.

The case shows why the certificate and server details matter more than the app’s name. They tied the second copy to the first straight away, where a name search alone would have treated it as a new problem.

Case File for a Fake App

A good record shortens every report and supports any later legal or regulatory action. Each finding keeps the evidence below in one place.

Evidence item Why a store or host needs it How it is captured
Store listing capture The app name, icon, developer name, description and publish date as customers saw them. Screenshots and the saved listing page from the store.
Installation file and hash The exact file under analysis, so later copies can be matched. The download from the store, mirror, repository or link, hashed on receipt.
Signing certificate fingerprint Whether the app was signed by the organization or by someone else. Certificate details extracted from the Android file, compared with the fingerprints in the organization’s Play Console.
Package or bundle identifier How closely the copy imitates the genuine identifier. The app manifest or store listing URL.
Permissions and behavior log What the app asks for and what it does with the access. Static analysis output and notes from the test device run.
Network destinations The servers, domains and bots that receive stolen data. Strings in the app and traffic captured during the test run.
Download page and domain records Who registered and hosts the page that distributes the app. The saved page, registration lookup, DNS records and hosting provider.
Proof of rights That the organization owns the name and logo being used. Trademark registration certificates and the organization’s own store listings.
Report and response log When each report was sent, to whom, and the outcome. The case record kept by the team running the takedown.
Customer impact Which accounts were affected and what was done for them. Sign-in logs, fraud cases and customer contact records.

Building an App Watch

A fake app program starts small and builds on what the first findings teach. Most of the early work is preparation that makes later reports fast.

  1. Build the inventory: List every genuine app, developer account, package identifier, icon and signing certificate fingerprint, and name an owner for each.
  2. Gather proof of rights: Collect trademark registrations and confirm who may sign complaints to the stores on the organization’s behalf.
  3. Publish the official list: Put the genuine apps on one web page and tell customers how to report a suspicious app.
  4. Start monitoring: Run searches across the official stores, APK sites, code repositories, new domains and social channels, and record every candidate.
  5. Agree the handoffs: Decide who confirms findings, who approves takedown requests, and how the fraud and customer teams are told.
  6. Review the first findings: Work through the first candidates end to end, then adjust searches to cut repeat noise.
  7. Add in-app checks: Plan Play Integrity and App Attest checks with the mobile team so the backend can spot unrecognized copies.

The aim for the first month is a confirmed baseline: every copy currently live is known, scored and either reported or watched. From there the program runs continuously, alongside watching for typosquatting domains that often host the download pages.

Fake App Monitoring With ThreatDefence

Copies of a customer’s app are one of the things the ThreatDefence Brand monitor agent hunts for. It searches the official stores and APK download sites for repackaged builds of the customer’s app and for apps that carry its name or logo without being published by it, and it notes the publisher and download source of each one.

  • Beyond the stores: Installation files sitting in public code repositories, and the posts, ads and Telegram channels that push downloads under the brand, are found by the same agent.
  • Analyst review: A SOC analyst confirms a significant fake app before the customer hears about it.
  • Removal: With the customer’s approval, the Takedown agent files requests with the app store, the code host or the hosting provider and rechecks until the copy is gone.
  • Returns: A copy that comes back on another site or domain is picked up again and handled as a fresh case, with new evidence and a new approval.

While a fake is live, the customer’s team hears which apps are genuine, so support staff can answer customers who ask. MSPs and MSSPs can offer the same watch to their clients under their own brand through brand monitoring.

Frequently Asked Questions

What is a fake app?

A fake app is a mobile app that uses an organization’s name, logo or design without permission so that people believe it is genuine. Some are built from scratch with a copied sign-in screen, and others are the real app altered to carry hidden code. They are used to steal passwords, one-time codes and money, and they spread through stores, APK sites, code repositories and links in messages.

What is a repackaged app?

A repackaged app is a genuine app that someone has decompiled, modified and rebuilt. It looks and works like the original, but it carries added code and is signed with the attacker’s certificate instead of the developer’s. Because Android only accepts updates signed with the original certificate, the copy installs as a separate app, and comparing certificate fingerprints is the most reliable way to identify it.

Can fake apps get into the official app stores?

Yes, fake apps sometimes pass review and appear in official stores until they are reported or detected. Google Play’s Impersonation policy and Apple’s Copycats guideline both prohibit them, and both stores accept complaints from rights holders. Joint government guidance from 2025 notes that a place in an official store lends a trojanized app a sense of legitimacy, so store presence alone proves little.

Is every copy of an app on an APK site fake?

No. Many APK sites mirror genuine apps unchanged, signed with the developer’s own certificate. The way to tell is to compare the file’s signing certificate fingerprint with the organization’s genuine certificate. A matching certificate means the code is the organization’s own, while a different certificate means the file was rebuilt by someone else and should be analyzed before anyone trusts it.

How do I report a fake app to Google Play?

Google Play’s Intellectual Property policy directs trademark owners to a trademark complaint form, with separate notices for counterfeit goods and copyright infringement. The policy encourages contacting the developer first, which may be unsafe with an obvious fraud. A report works best when it cites the Impersonation or Intellectual Property policy and includes proof of the trademark, screenshots of the listing and the analysis of the app.

How do I report a fake app to Apple?

Apple accepts intellectual property claims against App Store apps through its web dispute form, referenced in section 5.2 of the App Store Review Guidelines. The report should show the trademark, the infringing listing and how it breaches guideline 4.1 on copycats or 5.2.1 on protected third-party material. Guideline 4.1 says impersonating other apps or services can lead to removal from the Apple Developer Program.

Can an organization stop its app from being copied?

No. Determined attackers can always copy an app’s look or repackage its file. An organization can make copies easier to spot and less useful. Integrity checks such as Google’s Play Integrity API and Apple’s App Attest let the backend recognize requests from unrecognized builds, and an official list of genuine apps on the website helps customers avoid copies in the first place.

How do fake banking apps steal one-time codes?

Most read incoming text messages or notifications. Because Google Play restricts SMS permissions to default handler apps, with limited exceptions, a fake app installed from outside the store may ask to become the default SMS app or request accessibility or notification access. Once granted, it forwards codes to the attacker, who uses them to sign in or approve payments.

Should an organization tell customers about a fake app?

Yes, a clear notice helps customers avoid the copy and spot the next one. The FBI recommends that financial institutions tell customers whether they offer a mobile app and how to report fakes, and the NCSC-led 2025 advisory recommends notifying customers who installed a malicious app with steps to remove it. The notice should list the genuine apps and say how the organization does and does not contact customers.

Talk to Our Experts

See how ThreatDefence automates security monitoring, compliance and cyber risk management in one platform.

    I'm an MSP, MSSP, or reseller

    By submitting this form, you accept the terms in our privacy policy.