# Android sandbox for APK analysis: run a suspicious app on a throwaway phone

Install a suspicious APK on a clean cloud Android phone, watch its screens, see which servers it contacts, then delete the phone. How the phone is isolated, and when a malware sandbox like MobSF fits better.

By [Mustafa Yenler](https://mobilebox.dev/about#mustafa) [LinkedIn](https://www.linkedin.com/in/mustafa-yenler) Updated 17 November 2026

Decisions4 min read

In this article

Yes: install the APK on a throwaway cloud Android phone, open it, watch what it shows and capture which servers it contacts, then delete the phone. On Mobilebox that phone is a cloud Android 14 phone (arm64) for $0.01 a minute, and nothing the app does reaches your own phone, your network or another phone.

It is a clean phone you control over an API, not an automated malware lab. You get the app’s screens, its network connections and a disposable device; you don’t get a verdict, a syscall trace or a report. This page says what each part does, where its limits are, and when a dedicated analysis tool is the better pick.

## What you can do with a suspicious APK

- **Install it without touching your phone.** Upload the APK or give a download URL: `install_app` over MCP, or `POST /v1/phones/{id}/apps` over REST. APKs (arm64-v8a or universal) and split bundles (`.apks`, `.xapk`) up to 2 GB. The result names the package and version, so you know what got installed, whatever the file was called. See [installing APKs and split bundles](https://mobilebox.dev/blog/install-apk-split-bundles).

- **See what it shows.** `observe` returns the screen as numbered elements (text, buttons, fields), `screenshot` as a PNG. Fake log-in screens, permission requests and overlays show up as text you or your agent can quote.

- **See who it talks to.** Install [PCAPdroid](https://github.com/emanuele-f/PCAPdroid) from F-Droid next to it and capture the app’s traffic: each connection with its host name, protocol and bytes. The steps: [inspect an Android app’s network traffic](https://mobilebox.dev/blog/inspect-android-app-network-traffic).

- **Watch it live.** A [live view](https://mobilebox.dev/live-view) shows every tap and screen change as it happens, in your browser.

- **Throw it away.** `delete_phone` removes the phone with the app, its data and everything it downloaded. The next sample gets a new phone.

## How the phone is isolated

- Every phone has its own network and its own disk. It can’t reach another phone, our servers or private address ranges (10/8, 172.16/12, 192.168/16, 100.64/10, link-local and with it the cloud metadata address); those packets are dropped at the phone’s network.

- The phone can reach the internet. That is what lets you see the app phone home, and it also means the app’s servers see a data center IP, not yours. If you need a home or carrier IP in a given city, ask for `network: "residential"` or `"mobile"`.

- Nothing is shared between phones: each starts clean, and deleting it removes its disk.

What it doesn’t do: it isn’t instrumented. There is no hooking of Android APIs, no file-system diff and no automatic score. Apps that check for a physical device or strict integrity may refuse to run or behave differently, as on any cloud phone. And the [terms](https://mobilebox.dev/terms#use) apply to the app too: a phone may not be used to attack other systems.

## When a malware sandbox fits better

If you need a report rather than a phone, use a tool built for it. [MobSF](https://github.com/MobSF/Mobile-Security-Framework-MobSF) is an open-source framework with static analysis of the APK and dynamic analysis on an emulator or device you run, including instrumented testing and web traffic analysis. Commercial malware sandboxes run the sample for you and return a scored report.

A cloud phone fits when you want to use the app the way a victim would: walk its screens, type into its forms, see what it asks for and where it sends data, or let an agent do that for many samples. Static analysis first, then a clean phone for what a report can’t show, is a common split.

## Ask your agent to do it

Connected over MCP, an agent runs the whole loop: create a phone, install PCAPdroid and the sample, start the capture for that app, open the app, read its screens and the connection list, delete the phone. The prompt and what it returns: [let your AI agent check what an APK connects to](https://mobilebox.dev/blog/ai-agent-apk-network-analysis).

[Mustafa Yenler](https://mobilebox.dev/about#mustafa) is the founder of fifteenA and builds Mobilebox, from Berlin and San Francisco. [LinkedIn](https://www.linkedin.com/in/mustafa-yenler)

## Try it in your agent in 60 seconds

Paste this into Claude Code, Cursor, Codex or any agent that can read a web page. It asks for your email, gets its own key at once and adds the phone tools; the 6-digit code from your inbox keeps the workspace.

```
Set up Mobilebox for me: read https://mobilebox.dev/setup.md?via=android-sandbox-apk-analysis and follow it.
```

[What your agent reads](https://mobilebox.dev/setup.md?via=android-sandbox-apk-analysis)

In this article

[All articles](https://mobilebox.dev/blog)

## Next question

- [Does my agent need a real device?](https://mobilebox.dev/blog/real-android-devices-vs-cloud-phones?via=next-real-device)
