As the key to opening the Web3 world, Web3 wallets are responsible for securely hosting users' cryptocurrency assets. Once the wallet program itself is hacked, users' cryptocurrency assets will be at risk of theft.
Therefore, based on the responsibilities of Web3 wallets themselves, the SlowMist Security Team launched A Web Front-end Security Guide for Web and browser extension wallets and proposed the best security implementation for the management of the key lifecycle for wallets: generate, store, use, backup, and destroy. At the same time, referring to the OWASP MASVS international standard, we developed relevant security guidelines for the Web3 wallet client security audit items. The SlowMist Security Team hopes to ensure as much security as possible on the Web3 wallet client and reduce the risk of cryptocurrency asset theft through years of frontline security attack and defense experience and excellent international standards.
Web3 wallets, as the key to the Web3 world, must interact with a variety of DApps in Web3. During users' interactions, wallets face many security challenges. Hackers are very good at exploiting the design flaws of the interaction process to deceive users' assets, such as: using UI hijacking and tricking users into signing; using blind signatures to trick users into signing; using Permit signatures to steal users' assets; using TransferFrom zero transfer to deceive users for phishing; using the same tail number to execute the scam; phishing for NFT and other general phishing techniques.
In response to the users' interaction process and the common phishing techniques used by hackers, the SlowMist Security Team exclusively proposes a security audit during the users' interaction process, which includes: WYSIWYS (what you see is what you sign strategy); AML strategy; anti-phishing strategy; pre-execution strategy; and other strategies to defend against hacker attacks, reduce the risk of users being phished, and ensure the security of cryptocurrency assets.
Business Communication
Project Evaluation
Pay for Expenses
Security Audit
Issue a Report
Recently, the Model Context Protocol (MCP) has rapidly emerged as a key infrastructure component in the AI ecosystem, thanks to the efforts of organizations like Anthropic and swift adoption by tech giants such as OpenAI, Microsoft, and Google. By standardizing interfaces for seamless integration between AI systems and local tools, databases, and APIs, MCP significantly enhances the execution capabilities of intelligent agents. It has been dubbed the “USB-C of AI” by industry experts. The Web3 space has also begun to explore MCP-related applications. However, the protocol remains in an early, “chaotic” stage, facing multiple security risks and novel attack surfaces. Refer to SlowMist’s recently released MCP attack surface and security checklist for further insights.
In today's internet environment, threats like malware, viruses, phishing attacks, and more are constantly emerging. Installing antivirus software (such as AVG, Bitdefender, Kaspersky, Malwarebytes, and other internationally recognized products) can help users protect against malicious programs and improve system security. However, antivirus software provides basic protection, reducing risks but not guaranteeing absolute security. The fight against threats is a dynamic process, and installing antivirus software is just the first step in enhancing security. At the same time, antivirus software itself may generate false positives, creating additional risks.
As the TON ecosystem continues to grow, so has Web3 phishing groups. Currently, the TON ecosystem utilizes the TonConnect SDK to facilitate cross-platform and cross-application wallet connections and interactions. A common challenge with these solutions is ensuring domain verification during cross-platform or cross-application communications.