/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Researchers detail how Android apps can steal one-time 2FA codes from Google Authenticator by taking screenshots, a flaw that was first disclosed in 2014

Catalin Cimpanu / ZDNet :

ZDNet Catalin Cimpanu

Context & Ripple Effects

This write-up lands two weeks after researchers spotted the Cerberus Android malware strain quietly extracting one-time passwords from Google Authenticator — and it supplies the mechanism behind that capability: any app granted screenshot access can capture the codes, a weakness first disclosed all the way back in 2014. The point of the piece is that nothing about the technique is novel; what changed is that working malware is now using it in the wild.

Read against the wider corpus, the story sits in a long line of Android credential-theft research — from overlay-phishing apps stealing Facebook logins to OCR-based theft of crypto wallet recovery phrases — where the phone's own screen becomes the exfiltration surface rather than a network or server compromise.

First-order effects

  • Android users who treat Authenticator codes as phish-proof are exposed to any installed app with screen-capture ability, since the second factor can be read off the same device that holds the first.
  • Google's Android security team faces renewed pressure to restrict screenshot access around authenticator apps, a fix deferred since the flaw was disclosed in 2014.

Second-order effects

  • Enterprises and banks relying on TOTP apps for account recovery face a forced reassessment of app-based 2FA, pushing demand toward hardware keys and push-based verification that don't render secrets on-screen.
  • Google's Play Store screening comes under scrutiny again — the same review pipeline that let Hacking Team's app bypass vetting and later admitted credential-stealing scanner and wallet apps must now weigh screen-capture permissions as a risk signal.

Third-order effects

  • If the pattern holds, screen-level side channels become a durable attack class on mobile: the later Pixnapping attack shows even partial OS patches leave covert pixel-grabbing viable, meaning 2FA design has to assume the display itself leaks.
  • That points toward industry structure where software OTP apps are treated as a weakening factor category, with trust migrating to isolated secure elements and out-of-band verification.

The trend: Mobile authentication is being pushed away from on-device one-time codes toward factors that assume the screen itself is an attack surface, as screenshot, overlay, and OCR exfiltration techniques keep resurfacing across a decade of Android research.

Discussion

  • @gurgling_mrd AJ Durling on x
    Google Authenticator app lets other apps take screenshots of its code. Issue was first reported to Google in October 2014, but it was never addressed. Google could have fixed 2FA code-stea... via @zdnet #infosec #tech https://www.zdnet.com/...
  • @campuscodi Catalin Cimpanu on x
    Google could have fixed 2FA code-stealing flaw in Authenticator app years ago * App doesn't use FLAG_SECURE flag that prevents UI from being screenshotted/recorded * Issue first reported to Google in 2014 * Microsoft Authenticator also impacted https://www.zdnet.com/... https://t…