TLDR: Hackers trick users with fake podcast invites before requesting screen control through Microsoft Teams. Once granted, attackers get remote desktop access and can run code that drains crypto wallets. Security researcher Nick Bax says millions are already gone, hitting both project leaders and regular holders. Experts call for clearer Microsoft Teams warnings to stop [...] The post Hackers Use Microsoft Teams to Hijack Crypto Wallets: What To Know appeared first on Blockonomi.TLDR: Hackers trick users with fake podcast invites before requesting screen control through Microsoft Teams. Once granted, attackers get remote desktop access and can run code that drains crypto wallets. Security researcher Nick Bax says millions are already gone, hitting both project leaders and regular holders. Experts call for clearer Microsoft Teams warnings to stop [...] The post Hackers Use Microsoft Teams to Hijack Crypto Wallets: What To Know appeared first on Blockonomi.

Hackers Use Microsoft Teams to Hijack Crypto Wallets: What To Know

2025/09/13 16:42

TLDR:

  • Hackers trick users with fake podcast invites before requesting screen control through Microsoft Teams.
  • Once granted, attackers get remote desktop access and can run code that drains crypto wallets.
  • Security researcher Nick Bax says millions are already gone, hitting both project leaders and regular holders.
  • Experts call for clearer Microsoft Teams warnings to stop more crypto users from falling victim.

Hackers have found a new way to clean out crypto wallets, and it’s catching people off guard. The method is simple, built on trust, and ends with stolen funds. 

Security researcher Nick Bax shared details of the attack, warning that millions are already gone. Both project founders and everyday investors have been hit. This is a growing problem for the crypto community, and it relies on social engineering more than tech.

Bax explained that hackers are using Microsoft Teams calls to take full control of victims’ desktops. They first gain access to a real Twitter or Telegram account, or create a convincing fake. Then they contact their target with an offer: usually a podcast interview, partnership call, or investor chat.

The conversation continues until the hacker asks the victim to screen-share their project. After some time, they claim they need to share something too. That’s when a request appears asking for “control” of the screen. Most users think this is harmless and click accept.

Once accepted, the hacker has remote control of the computer. Bax warned that they can now run commands, install malware, and empty wallets. This is not a technical exploit but a social one, and it works.

Crypto Security Risks Widen

According to Bax, this attack is harder to spot on Microsoft Teams because of how the dialog is worded. The message says “Requesting control,” which sounds routine. On other platforms like Zoom, there are extra warning clicks before control is handed over. This difference makes Teams a softer target.

Bax even tested creating a fake Teams account using Cyrillic characters to mimic “Microsoft Teams.” He said the platform allowed it, making it easier for attackers to trick victims. The result is a mix of bad UX design and patient social engineering.

This attack has been active for months and keeps evolving. The initial hook may change, but the result is the same: a complete desktop takeover. Crypto investors and project leaders are urged to treat all screen control requests as high-risk.

Security experts say users should verify who they are speaking to before any screen share. Turning off screen control permissions unless absolutely needed can also prevent attacks. Bax called on Microsoft to add clearer warnings so users understand what they are agreeing to before control is granted.

The post Hackers Use Microsoft Teams to Hijack Crypto Wallets: What To Know appeared first on Blockonomi.

Disclaimer: The articles reposted on this site are sourced from public platforms and are provided for informational purposes only. They do not necessarily reflect the views of MEXC. All rights remain with the original authors. If you believe any content infringes on third-party rights, please contact service@support.mexc.com for removal. MEXC makes no guarantees regarding the accuracy, completeness, or timeliness of the content and is not responsible for any actions taken based on the information provided. The content does not constitute financial, legal, or other professional advice, nor should it be considered a recommendation or endorsement by MEXC.
Share Insights

You May Also Like

Google's AP2 protocol has been released. Does encrypted AI still have a chance?

Google's AP2 protocol has been released. Does encrypted AI still have a chance?

Following the MCP and A2A protocols, the AI Agent market has seen another blockbuster arrival: the Agent Payments Protocol (AP2), developed by Google. This will clearly further enhance AI Agents' autonomous multi-tasking capabilities, but the unfortunate reality is that it has little to do with web3AI. Let's take a closer look: What problem does AP2 solve? Simply put, the MCP protocol is like a universal hook, enabling AI agents to connect to various external tools and data sources; A2A is a team collaboration communication protocol that allows multiple AI agents to cooperate with each other to complete complex tasks; AP2 completes the last piece of the puzzle - payment capability. In other words, MCP opens up connectivity, A2A promotes collaboration efficiency, and AP2 achieves value exchange. The arrival of AP2 truly injects "soul" into the autonomous collaboration and task execution of Multi-Agents. Imagine AI Agents connecting Qunar, Meituan, and Didi to complete the booking of flights, hotels, and car rentals, but then getting stuck at the point of "self-payment." What's the point of all that multitasking? So, remember this: AP2 is an extension of MCP+A2A, solving the last mile problem of AI Agent automated execution. What are the technical highlights of AP2? The core innovation of AP2 is the Mandates mechanism, which is divided into real-time authorization mode and delegated authorization mode. Real-time authorization is easy to understand. The AI Agent finds the product and shows it to you. The operation can only be performed after the user signs. Delegated authorization requires the user to set rules in advance, such as only buying the iPhone 17 when the price drops to 5,000. The AI Agent monitors the trigger conditions and executes automatically. The implementation logic is cryptographically signed using Verifiable Credentials (VCs). Users can set complex commission conditions, including price ranges, time limits, and payment method priorities, forming a tamper-proof digital contract. Once signed, the AI Agent executes according to the conditions, with VCs ensuring auditability and security at every step. Of particular note is the "A2A x402" extension, a technical component developed by Google specifically for crypto payments, developed in collaboration with Coinbase and the Ethereum Foundation. This extension enables AI Agents to seamlessly process stablecoins, ETH, and other blockchain assets, supporting native payment scenarios within the Web3 ecosystem. What kind of imagination space can AP2 bring? After analyzing the technical principles, do you think that's it? Yes, in fact, the AP2 is boring when it is disassembled alone. Its real charm lies in connecting and opening up the "MCP+A2A+AP2" technology stack, completely opening up the complete link of AI Agent's autonomous analysis+execution+payment. From now on, AI Agents can open up many application scenarios. For example, AI Agents for stock investment and financial management can help us monitor the market 24/7 and conduct independent transactions. Enterprise procurement AI Agents can automatically replenish and renew without human intervention. AP2's complementary payment capabilities will further expand the penetration of the Agent-to-Agent economy into more scenarios. Google obviously understands that after the technical framework is established, the ecological implementation must be relied upon, so it has brought in more than 60 partners to develop it, almost covering the entire payment and business ecosystem. Interestingly, it also involves major Crypto players such as Ethereum, Coinbase, MetaMask, and Sui. Combined with the current trend of currency and stock integration, the imagination space has been doubled. Is web3 AI really dead? Not entirely. Google's AP2 looks complete, but it only achieves technical compatibility with Crypto payments. It can only be regarded as an extension of the traditional authorization framework and belongs to the category of automated execution. There is a "paradigm" difference between it and the autonomous asset management pursued by pure Crypto native solutions. The Crypto-native solutions under exploration are taking the "decentralized custody + on-chain verification" route, including AI Agent autonomous asset management, AI Agent autonomous transactions (DeFAI), AI Agent digital identity and on-chain reputation system (ERC-8004...), AI Agent on-chain governance DAO framework, AI Agent NPC and digital avatars, and many other interesting and fun directions. Ultimately, once users get used to AI Agent payments in traditional fields, their acceptance of AI Agents autonomously owning digital assets will also increase. And for those scenarios that AP2 cannot reach, such as anonymous transactions, censorship-resistant payments, and decentralized asset management, there will always be a time for crypto-native solutions to show their strength? The two are more likely to be complementary rather than competitive, but to be honest, the key technological advancements behind AI Agents currently all come from web2AI, and web3AI still needs to keep up the good work!
Share
PANews2025/09/18 07:00