Security

Android SDK Vulnerability Exposed Millions of Wallets

3 min read

Summary

Microsoft disclosed a severe intent redirection flaw in the third-party EngageSDK for Android, putting millions of crypto wallet users at potential risk of data exposure and privilege escalation. The issue was fixed in EngageSDK version 5.2.1, and the case highlights the growing security risk of opaque mobile app supply-chain dependencies.

Need help with Security?Talk to an Expert

Introduction

Microsoft has disclosed a severe Android security issue in a widely used third-party library, EngageSDK. While the flaw was not found to be exploited in the wild, it affected apps installed at massive scale and serves as a reminder that third-party SDKs can quietly introduce major supply-chain risk into otherwise trusted mobile apps.

What happened

The vulnerability is an intent redirection flaw in EngageSDK, a library used for messaging and push notifications in Android apps.

Key details include:

  • The issue allowed a malicious app on the same device to abuse the vulnerable app’s trusted context.
  • This could potentially lead to unauthorized access to protected components, sensitive data exposure, and privilege escalation.
  • Microsoft said more than 30 million installations of third-party crypto wallet apps alone were potentially exposed to risk.
  • The flaw was traced to an exported Android activity, MTCommonActivity, added through the SDK during the build process.
  • Because it appears in the merged manifest post-build, developers may miss it during normal review.

Microsoft coordinated disclosure with EngageLab and the Android Security Team. The issue was resolved in EngageSDK version 5.2.1 on November 3, 2025.

Why this matters for security teams

This disclosure is important beyond Android wallets. It shows how:

  • Third-party SDKs can expand the attack surface without clear visibility
  • Exported components can create unintended trust boundaries between apps
  • Mobile app supply-chain weaknesses can affect millions of users at once

Android has also added platform-level mitigations for this specific EngageSDK risk, and apps detected as vulnerable were removed from Google Play. Microsoft noted that users who had already downloaded vulnerable apps now have additional protection.

Impact on administrators and developers

For security administrators, this is a strong example of why mobile application governance must include dependency review, not just app reputation or store approval.

For developers and DevSecOps teams, the biggest lessons are:

  • Review merged Android manifests, not only source manifests
  • Audit exported activities and other exposed components
  • Validate intent handling and cross-app trust assumptions
  • Track third-party SDK versions as part of software supply-chain management
  • Upgrade EngageSDK immediately to version 5.2.1 or later if it is present in any Android apps.
  • Review mobile apps for exported components added by dependencies.
  • Add dependency and manifest analysis to CI/CD security checks.
  • Use Microsoft’s detection guidance and indicators from the original advisory to assess exposure.

This incident reinforces a broader point: mobile security is increasingly shaped by the libraries apps depend on, not just the code developers write directly.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

Android securitymobile app securitythird-party SDKcrypto walletsMicrosoft Defender

Related Posts

Security

Microsoft Sentinel Named a 2026 SIEM Leader

Microsoft has been named a Leader in the 2026 Gartner Magic Quadrant for SIEM, highlighting the continued momentum behind Microsoft Sentinel. The announcement also underscores Microsoft's push toward integrated, AI-powered security operations through deep Sentinel integration with the new Integrated Security Operations Center in Microsoft Defender.

Security

Microsoft Perception GA: Agentic Security at Ignite

Microsoft has made Microsoft Perception generally available, introducing an agentic security platform that coordinates red, blue, and green team agents through automated playbooks. Announced at Ignite 2026, the update also expands Defender and Sentinel capabilities to help security teams detect, investigate, and remediate AI-speed threats while keeping administrators in control.

Security

Device Code Phishing Risks for AI Coding Agents

Microsoft warns that device code phishing can be used against AI coding agents such as GitHub Copilot CLI, not just user mailboxes or cloud apps. In a controlled lab, a single approved device code sign-in could enable remote session steering, memory poisoning, synced session exposure, and private repository access depending on account permissions and enabled features.

Security

Microsoft 365 Outage Phishing Campaign Targets Users

Microsoft Threat Intelligence reported a high-volume phishing campaign that impersonates Microsoft 365 service-health notifications to trick users into clicking malicious links. The campaign matters because it uses outage-themed urgency and recipient-specific tracking to target multiple industries, increasing the risk of credential theft and follow-on account compromise.

Security

SCKit ScreenConnect Attack: MSPs Must Hunt Now

Microsoft Threat Intelligence confirmed a campaign abusing ConnectWise ScreenConnect to deploy unauthorized remote-access clients and the SCKit worm on MSP-managed endpoints. The activity can also target technician sessions, making this a high-priority incident for defenders because removing a rogue client alone does not eliminate persistence or invalidate exposed sessions.

Security

AI Agent Supply Chain Attacks Target Coding Tools

Microsoft Security researchers detailed two post-training supply chain attack paths that can backdoor coding and terminal agents: dataset poisoning and model poisoning. The findings matter because compromised agents can misuse tools, execute commands, and access sensitive environments even when prompts appear benign, reinforcing the need for stronger controls around training data, model provenance, and tool permissions.