← Back to index
References / filed

REQUEST_COMPANION_USE_DATA_IN_BACKGROUND

Keeps a paired companion app using network data in the background, so the exfiltration pipe stays open when the victim is not looking.

270 words2 min read
Filed under
#android#permissions#reference

This one extends the companion device model into background network activity, letting a paired companion app continue using mobile data while it is not in the foreground.

The manifest analysis places it in a group it describes as contributing to a manifest with substantial capabilities for maintaining activity outside the normal foreground application lifecycle. Plainly: it keeps the wire open.

That is the part that matters for an implant. Every exfiltration path in the write-up is an HTTP POST, from SmsUploadWorker to data/sms/batch and the call-log and contact workers following the same shape. A background network restriction interrupts those uploads, and a retry worker can only replay what was already collected. Keeping data flowing in the background is what makes the collection chain continuous rather than opportunistic.

It pairs with REQUEST_COMPANION_RUN_IN_BACKGROUND, which covers background execution, and REQUEST_COMPANION_START_FOREGROUND_SERVICES_FROM_BACKGROUND, which covers starting services from the background. Execution, networking, and services, all three of them scoped to the companion relationship.

The honest qualification is that the companion model requires a real pairing, which a sideloaded traffic-challan app has no obvious way to establish. No code-level use is traced for it in the write-up, so it reads as declared capability in the background-permission group alongside the more clearly exploited foreground service types.

Related: REQUEST_COMPANION_RUN_IN_BACKGROUND, REQUEST_COMPANION_START_FOREGROUND_SERVICES_FROM_BACKGROUND, REQUEST_IGNORE_BATTERY_OPTIMIZATIONS

Part of Few Android permissions I have seen used often. All permissions here were seen in the mprivhaan analysis.