Potential clipboard risks and background permission conflicts with Cake Wallet on Android

Hey everyone, I’m hoping to get some advice from anyone familiar with Android app sandboxing and Cake Wallet security. I recently installed a third-party utility tool from here on my phone to run some automated scripts, but since this is the same device where I actively use Cake Wallet for my XMR and BTC transactions, I started feeling uneasy about background interference.

Specifically, the package requested overlay and accessibility permissions, which got me thinking about clipboard hijacking risks where an active background service might alter copied crypto addresses before a transaction is broadcasted. I also wondered if background overlays could theoretically log screen inputs during authentication or if Cake Wallet’s secure enclave and memory space remain completely isolated from other user-space apps.

Has anyone experienced similar security questions with side-loaded utilities on the same operating environment, and would you recommend isolating the wallet inside a dedicated secure profile or keeping it on an entirely separate device?

Not sure if it would be applicable, but just in case you missed it, there’s this available for anyone, at all times. => Security & Vulnerability Disclosure | Cake Wallet