# Android malware posing as ChatGPT apps

- ID: unit42-android-chatgpt-malware-2023
- Reported: 2023-03-21
- Researcher: Unit 42
- Organization: Palo Alto Networks Unit 42
- AI role: ai_tool_as_lure (AI tool as lure)
- Confidence in AI involvement: not assessed
- Research / borderline: false
- Last reviewed: 2026-10-20
- Entry page: https://openattacks.ai/attacks/unit42-android-chatgpt-malware-2023/
- Entry JSON: https://openattacks.ai/api/attacks/unit42-android-chatgpt-malware-2023.json
- Browse title: Android malware posing as ChatGPT apps
- Editorial summary: Fake ChatGPT Android apps delivered Meterpreter and SMS-fraud malware as ChatGPT-themed phishing and trojan sites grew.
- Evidence class (catalog annotation): Reported campaign
- Source-stated target environments: Android
- Stage hunts and conditional defenses: https://openattacks.ai/api/defenses/unit42-android-chatgpt-malware-2023.json

## Technique
Android APKs impersonating ChatGPT delivered Meterpreter and SMS-fraud malware. Broader ChatGPT-themed phishing and trojan sites rose with GenAI popularity.

## Stack relevance (editorial)
Assessment: mapped. Editorial applicability reviewed against the catalog source account; not a scan or independent incident verification.
First action: Review sideloaded APKs and their source, package identity and granted permissions.
- Relationship: lure; tools: chatgpt; OS scope: android; requires existing MCP connections: false.
  Relevance: The report concerns Android APKs impersonating ChatGPT.
  Condition to check: Confirm sideloading of an affected fake APK; legitimate ChatGPT use alone is not the condition.
  Evidence: https://unit42.paloaltonetworks.com/android-malware-poses-as-chatgpt/ ; https://unit42.paloaltonetworks.com/chatgpt-scam-attacks-increasing/
A product mention alone is not a victim-side applicability mapping. Selection does not verify affected versions, permissions or compromise.

## Initial access
Sideloaded fake ChatGPT Android apps / phishing sites

## AI tooling and models
- Fake [ChatGPT](https://chatgpt.com/) Android apps

## Other tooling
- [Meterpreter](https://github.com/rapid7/metasploit-framework)
- SMS fraud malware

## Victims and sectors
Android users seeking ChatGPT apps

## Target geography
- unknown

## Attribution
unknown

## Scale and metrics
unknown

## Attack flow
Catalog reconstruction of the supplied source account. Unknowns and research caveats are preserved.
### step-1: User encounters a fake ChatGPT app [access]
Phishing or trojan sites offer Android APKs.
Evidence: https://unit42.paloaltonetworks.com/android-malware-poses-as-chatgpt/ ; https://unit42.paloaltonetworks.com/chatgpt-scam-attacks-increasing/

### step-2: ChatGPT branding provides the lure [ai]
The application impersonates the AI product.
Evidence: https://unit42.paloaltonetworks.com/android-malware-poses-as-chatgpt/ ; https://unit42.paloaltonetworks.com/chatgpt-scam-attacks-increasing/

### step-3: User sideloads the APK [execution]
The package delivers Meterpreter or SMS-fraud malware.
Evidence: https://unit42.paloaltonetworks.com/android-malware-poses-as-chatgpt/ ; https://unit42.paloaltonetworks.com/chatgpt-scam-attacks-increasing/

### step-4: Remote access or SMS fraud [impact]
The reported payload determines the resulting device abuse.
Evidence: https://unit42.paloaltonetworks.com/android-malware-poses-as-chatgpt/ ; https://unit42.paloaltonetworks.com/chatgpt-scam-attacks-increasing/

Connections:
- step-1 -> step-2
- step-2 -> step-3
- step-3 -> step-4

## Stage defense and hunting recommendations
Editorial recommendations, not validated coverage. Source-controlled query starters are drafts. Custom-schema examples require telemetry collection and field mapping; absence of a mapping means not assessed. MagicSword policy opportunities require managed Windows scope and enforcement.
### step-1: Lure → user action / delivery
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/phishing.sigma.yml
- KQL query download: /api/detections/phishing.kql
- SPL query download: /api/detections/phishing.spl
- Hunt hypothesis: An impersonating message, ad or website leads to a suspicious download, consent request, pasted command or payment instruction.
- Required telemetry: Email / secure-web-gateway records; Browser redirects, downloads and URL reputation; User reports and downstream execution / identity events
- Investigate: Reconstruct redirect and delivery provenance using original report indicators, without visiting payload URLs.
- Investigate: Correlate the click with the actual download, consent or execution; verify the sender through an independent channel.
- Limitation: Polished text, AI branding and a novel domain do not prove maliciousness or AI generation. Follow-on evidence matters.
- No direct MagicSword prevention claim is recorded for this stage.

### step-2: Unapproved Android package / sensitive access
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/android.sigma.yml
- KQL query download: /api/detections/android.kql
- SPL query download: /api/detections/android.spl
- Hunt hypothesis: A sideloaded AI-branded APK obtains sensitive capabilities and performs unexpected SMS, credential or remote-access actions.
- Required telemetry: Android enterprise / mobile threat-defense package inventory; Install source, signer and permission changes; SMS, accessibility and network telemetry where available
- Investigate: Compare package ID and signing certificate with the approved source.
- Investigate: Correlate new permissions and outbound or SMS behavior; apply mobile platform controls rather than Windows policies.
- Limitation: Standard Windows EDR tables do not provide Android app events. Device-management and mobile telemetry are required.
- Qualification: Compare package identity, signer and permissions with approved software; ChatGPT branding alone does not establish a malicious APK.
- No direct MagicSword prevention claim is recorded for this stage.

### step-3: Unapproved Android package / sensitive access
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/android.sigma.yml
- KQL query download: /api/detections/android.kql
- SPL query download: /api/detections/android.spl
- Hunt hypothesis: A sideloaded AI-branded APK obtains sensitive capabilities and performs unexpected SMS, credential or remote-access actions.
- Required telemetry: Android enterprise / mobile threat-defense package inventory; Install source, signer and permission changes; SMS, accessibility and network telemetry where available
- Investigate: Compare package ID and signing certificate with the approved source.
- Investigate: Correlate new permissions and outbound or SMS behavior; apply mobile platform controls rather than Windows policies.
- Limitation: Standard Windows EDR tables do not provide Android app events. Device-management and mobile telemetry are required.
- No direct MagicSword prevention claim is recorded for this stage.

### step-4: Unapproved Android package / sensitive access
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/android.sigma.yml
- KQL query download: /api/detections/android.kql
- SPL query download: /api/detections/android.spl
- Hunt hypothesis: A sideloaded AI-branded APK obtains sensitive capabilities and performs unexpected SMS, credential or remote-access actions.
- Required telemetry: Android enterprise / mobile threat-defense package inventory; Install source, signer and permission changes; SMS, accessibility and network telemetry where available
- Investigate: Compare package ID and signing certificate with the approved source.
- Investigate: Correlate new permissions and outbound or SMS behavior; apply mobile platform controls rather than Windows policies.
- Limitation: Standard Windows EDR tables do not provide Android app events. Device-management and mobile telemetry are required.
- No direct MagicSword prevention claim is recorded for this stage.


## MITRE ATLAS
Mappings are catalog annotations based on described behavior, not assignments or endorsements by MITRE.
No source-backed mapping is currently recorded.

## Defensive notes
Official app stores only; mobile threat defense

## Sources
- https://unit42.paloaltonetworks.com/android-malware-poses-as-chatgpt/
- https://unit42.paloaltonetworks.com/chatgpt-scam-attacks-increasing/
