Ctrl+C, Ctrl+v, Ctrl+cve: Bypassing Android's Clipboard Read Security Measures
dethmasque
76 points
33 comments
November 13, 2026
Related Discussions
Found 5 related stories in 128.7ms across 12,728 title embeddings via pgvector HNSW
- GrapheneOS Overhauled Default Apps and Secure Clipboard Cider9986 · 246 pts · September 06, 2026 · 48% similar
- Another way to leak traffic on Android has been discovered mhitza · 33 pts · September 11, 2026 · 48% similar
- Google's servers can scan what you copy in Chrome for unsafe content bundie · 23 pts · October 21, 2026 · 46% similar
- Zero click, silent, remote Android DoS MarkBlah · 316 pts · October 29, 2026 · 43% similar
- Backdoor in Claude Code for VS Code extension on the Cursor Marketplace _chall · 857 pts · October 30, 2026 · 43% similar
Discussion Highlights (7 comments)
seszett
I've always been irritated by the lack of control on whether apps can inspect the clipboard or not. The bpost app (Belgian national post) immediately reads the clipboard when it gets opened and I hate this behaviour with a passion. While on the other hand it throws a fit if it ever detects an unlocked bootloader, root access, "suspicious" apps or whatever. I ended up confining it to an outdated phone with a stock OS along with the bank and identity apps that I cannot avoid. I digress, but the original cause of my irritation was indeed lack of control on my clipboard that ia had noticed thanks to that small notification.
chinhodado
A long time ago I wrote a dictionary app for my own use, which would show word definition upon the word being copied into the clipboard (e.g. from an e-book reader app). The dictionary app would run in the background and only show the pop up on clipboard event. Then around Android 10 they tightened security and decided background apps can no longer receive clipboard event. Which makes sense from a security standpoint, but it totally broke my dictionary app. I just wish they're a way as a developer to get around it with my own app.
ryandrake
I feel like the clipboard is something that is on computers today only because it was invented back when dinosaurs roamed the earth, and we can't get rid of it as a concept because it's so ingrained in computing. If we never had the clipboard (on any computer, not just Android) and it was suddenly invented today, it would never pass any major company's privacy or security review. Here we have something that allows the user to share any data instantly with any process that happens to be listening, including sensitive things like credentials, personal information, the works. It's a security nightmare! In today's paranoid times, no OS would say yes to a new feature like this, but we keep it because it's legacy and it can't be gotten rid of at this point.
iloveyoutwo
GrapheneOS recently added secure paste: https://grapheneos.org/features#secure-paste
streetfighter64
I think allowing any program to read the clipboard at all is a huge mistake. The way it should work is that it's entirely safeguarded by the OS, and the only time an app can see the contents is when it receives them in a Ctrl+V event initiated by the user. This is the way most users, even non-technical, expect it to work, I'm pretty sure.
aboardRat4
All programs must be open source and distributed as source. Everything else is cargo cult security.
vintagedave
I don’t use Android so I’m not sure what I’m seeing in the embedded video. Is it that there should be a notification at the top of the screen but there isn’t? I thought the article implied it used two different notifications that hide the system one but I see none at all.