18 Nov 2026, Wed

Malicious ‘Safery’ Ethereum Wallet Extension Evades Detection on Chrome Web Store Using Sui Blockchain for Data Exfiltration

For a few critical days last November, a malicious software masquerading as a cryptocurrency wallet managed to secure the fourth position in search results for the term "Ethereum wallet" on the official Chrome Web Store. The extension, deceptively titled "Safery: Ethereum Wallet," presented a polished, professional facade designed to easily fool unsuspecting users searching for secure asset management tools. Featuring a clean graphic icon, a generic name subtly aligned with security-oriented terminology, a sudden influx of five-star reviews, and boilerplate descriptions immediately familiar to anyone active in the decentralized finance space, the extension successfully bypassed initial automated security checks.

Beneath this convincing front-end lay a sophisticated, purpose-built attack mechanism engineered to harvest user seed phrases and systematically drain digital asset wallets. Instead of relying on traditional, easily trackable methods of data exfiltration, the malicious software leveraged the Sui blockchain, encoding stolen secrets into tiny micro-transactions to quietly smuggle sensitive information off the victim’s device without raising alarms.

The operation came to light after security tooling specialists at Socket, a firm dedicated to protecting open-source software supply chains, installed and conducted a rigorous technical analysis of the extension following its sudden discovery. The primary objective of their investigation was to understand how "Safery" managed to evade Google’s automated detection filters, rapidly climb the Chrome Store rankings, and exfiltrate sensitive seed phrases without triggering standard browser or antivirus warnings. Furthermore, the resulting security report serves as both a detailed postmortem of the attack and an urgent reminder that browser extensions remain a dangerous, often overlooked blind spot in the broader cryptocurrency ecosystem.

What makes this particular incident especially noteworthy for security analysts is that the perpetrators did not resort to traditional phishing tactics. Unlike many past crypto scams that relied on spoofing well-known wallet brands, masquerading as popular tools like MetaMask, or utilizing recycled phishing domains, Safery forged an entirely new identity. The malicious actors invented a completely novel brand, utilized automated bots or purchased fake reviews to artificiality inflate its search ranking and user metrics, and launched the software as a legitimate new wallet option within the marketplace.

Because the extension did not impersonate an existing trademark, its listing displayed virtually no immediate red flags. There was no broken grammar in the descriptions, no unusual or overly aggressive permission requests, and no suspicious redirections to sketchy external domains. The official Chrome Web Store publisher page associated with the listing had no prior complaints or warning flags, while its designated support URL directed visitors to an external website that had not yet been flagged by cybersecurity tracking databases at the time of Socket’s initial analysis.

Given its highly polished appearance and professional presentation, the average user would have had little reason to hesitate before clicking the "Add to Chrome" button. Like many legitimate Web3 tools, the extension requested standard permissions to run on all websites—a necessary function for browser wallets that must interact seamlessly with various decentralized applications across the web. Notably, it refrained from prompting for extra administrative privileges or attempting to inject complex content scripts that typically trigger aggressive warnings from Google Chrome’s built-in security systems. The branding remained minimalist, the companion website aligned perfectly with the extension’s stated name, and the initial setup interface correctly prompted users to either create a brand-new wallet or import an existing one, mimicking standard industry behavior.

The Seed Heist, Broadcast Over Sui

The true destructive phase of the operation was initiated the moment a user entered their recovery seed phrase into the interface. Rather than storing the sensitive text locally on the device or attempting to encrypt it for user retrieval, the extension silently fragmented the phrase into smaller pieces. These fragments were then ingeniously encoded to resemble random, innocuous wallet addresses.

Socket’s comprehensive research revealed that these data fragments were systematically embedded directly into transactions on the Sui blockchain. Specifically, the extension initiated minuscule SUI token transfers—amounts so negligible that they would draw absolutely zero attention from users or automated network monitors—directed toward wallet addresses under the direct control of the attackers. Embedded deep within these transaction parameters, hidden either inside standard memo fields or through obfuscated address routing, were the discrete pieces of the victim’s seed phrase.

This tactical approach offered significant advantages to the hackers. It completely eliminated the need for the extension to send traditional outbound network requests to malicious command-and-control servers. There was no suspicious beaconing activity, nor was there any data exfiltration conducted via standard HTTP or WebSockets protocols that modern browsers, firewalls, or antivirus software typically monitor and flag.

Instead, the malicious payload left the user’s device disguised as an entirely normal, everyday blockchain transaction, neatly routed through a widely utilized, low-fee decentralized network. Once successfully published on-chain, the fragmented data became publicly accessible, enabling the operators to retrieve the information at their convenience, reconstruct the complete seed phrase, and systematically sweep external wallets clean without ever needing to interact with the victim’s device a second time.

In effect, the scam utilized the Sui blockchain itself as an unconventional, highly efficient communications channel. Because the Sui network boasts exceptionally fast transaction confirmation times and negligible gas fees, it functioned remarkably well as a low-latency message bus for the attackers.

Socket successfully traced multiple instances of these unique seed-fragment transactions, definitively confirming the direct causal link between the entry of a recovery phrase into the extension and the subsequent loss of funds. While the actual asset thefts occurred off-chain—predominantly on Ethereum or other Layer-1 networks where the victims’ wallets held substantial balances—the precise instructions required to carry out the thefts were hidden entirely in plain sight.

Before releasing the final, highly optimized version that eventually climbed to the top of Chrome’s wallet search results, the publisher likely tested the methodology in private environments. Digital forensics and historical data indicate that earlier, unreleased builds experimented with much simpler data leakage techniques before the Sui blockchain encoding method was fully refined.

By the time the active, malicious extension was finally flagged and reported, it had accumulated enough installations to achieve Chrome’s coveted "trending" status, which further amplified its visibility to unsuspecting users. Reports from industry outlets confirmed that the Safery wallet remained prominently featured among the top search results for Ethereum-related queries even as growing warnings and complaints circulated widely across community platforms like Reddit and Telegram.

How the Chrome Algorithm Let It Happen

The ultimate success of the Safery extension hinged primarily on the underlying mechanics of Google Chrome’s search and recommendation algorithm. The Web Store search logic relies on a combination of factors, including precise keyword matching, total installation counts, review velocity, average user ratings, and the recency of the last software update.

Extensions that experience a sudden, concentrated burst of user activity, particularly within specialized or niche categories, can climb search rankings rapidly if established, better-vetted competitors are not updated with equal frequency. In this scenario, Safery combined a strategic title optimized for high-volume search queries with a coordinated blitz of positive reviews—many of which were clearly templated or duplicated—alongside a very recent upload date.

There is currently no evidence to suggest that Google manually reviewed the listing prior to its publication. Standard Chrome Web Store policies typically subject newly submitted extensions to a brief automated scan alongside fundamental static code analysis.

Deeper security scrutiny is usually reserved for extensions that request elevated permissions, such as direct access to browser tabs, local clipboards, the file system, or web browsing history. Because crypto wallet extensions frequently manage to bypass these specific warning triggers by operating safely within isolated iframes or utilizing standard, pre-approved application programming interfaces, Safery was able to remain strictly within acceptable boundaries.

Even after concerned users began noticing and raising alarms about the suspicious activity, the elapsed time between initial reporting and the eventual takedown of the listing stretched out long enough for substantial financial damage to occur. Part of this vulnerability is structural: the Chrome Web Store does not automatically act on flagged extensions instantaneously unless there is an overwhelming consensus from security researchers or a match with known malware signatures.

In this particular instance, the malicious payload consisted entirely of heavily obfuscated JavaScript that relied directly on legitimate blockchain infrastructure rather than communicating with external, identifiable host servers. Consequently, traditional malware detection techniques failed to catch the threat in time.

While this incident is far from the first time browser extensions have been weaponized to target cryptocurrency assets—previous notable scams have included fake desktop companion apps prompting for recovery phrases or hijacked legitimate extensions allowing unauthorized access to developer publishing keys—Safery stood out due to the remarkable smoothness of its facade and the complete absence of traditional backend infrastructure. There was no external phishing website to take down, and no rogue server to block; there was merely a single browser extension quietly depositing secret fragments onto a public ledger and walking away.

Impactful countermeasures were limited for affected users. Those who realized they had been compromised quickly enough could minimize their total exposure by immediately rotating their seed phrases and manually revoking prior transaction approvals across various decentralized applications.

Security firms like Socket quickly published detailed triage steps for anyone who had installed the software: uninstall the extension immediately, revoke all active token approvals, transfer remaining digital assets to a freshly generated wallet using an entirely clean device, and closely monitor all associated addresses for unauthorized activity. For users who failed to notice the silent data exfiltration or who maintained large balances within vulnerable hot wallets, financial recovery remained virtually impossible.

Industry developers and security researchers are now calling for significantly stronger heuristics from Google regarding Chrome Web Store governance. Proposed solutions include implementing automatic warning flags for any extension interface that incorporates user interface elements prompting for a standard 12- or 24-word recovery phrase.

Additional recommendations involve requiring strict publisher attestation for all wallet-related extensions, providing verifiable cryptographic proof that a listed publisher genuinely controls the codebase behind a recognized cryptocurrency project. Calls have also intensified for more rigorous inspections of wallet-related permissions, even when those permissions do not explicitly incorporate traditionally dangerous access patterns.

For the end user, security experts emphasize that a clean name, professional branding, and a high user rating are no longer sufficient guarantees of safety. The incident highlights the inherent risks of relying heavily on browser-based environments for digital asset management, prompting renewed discussions across the cryptocurrency community regarding secure distribution models and user sovereignty.

Leave a Reply

Your email address will not be published. Required fields are marked *