16 Nov 2026, Mon

Malicious "Safery" Ethereum Wallet Extension Slips into Chrome Web Store Top Rankings Using Sui Blockchain for Data Exfiltration

For several days last November, a malicious Chrome extension managed to secure the fourth position in the Chrome Web Store search results for the high-traffic keyword "Ethereum wallet." Disguised under the name "Safery: Ethereum Wallet," the application was crafted with enough precision and polish to easily pass as a legitimate tool for cryptocurrency users. It featured a clean icon, a generic yet reassuring name adjacent to standard security terminology, a heavy influx of five-star ratings, and boilerplate descriptions immediately familiar to anyone who has ever downloaded a digital asset manager.

However, behind this sophisticated frontend lay a purpose-built attack mechanism. The extension was designed to capture seed phrases and systematically drain user wallets by encoding stolen confidential secrets directly into micro-transactions on the Sui blockchain.

The threat was uncovered and subsequently analyzed by Socket, a prominent security tooling company focused on open-source software supply chains. Security researchers at the firm installed and examined the extension to understand how "Safery" successfully evaded initial automated detection, climbed the official Chrome Store search rankings, and exfiltrated sensitive seed phrases without raising immediate alarms. The resulting forensic report walks through the attacker’s unconventional methodology, serving simultaneously as a postmortem of the breach and a stark warning that browser extensions continue to represent a dangerously overlooked blind spot within the broader cryptocurrency ecosystem.

This particular incident stands out because the malicious actors chose not to spoof an existing, well-known wallet brand. Unlike previous high-profile scams that relied on mimicking MetaMask or recycling defunct phishing domains to trick unsuspecting visitors, this operation forged an entirely original identity. The creators manufactured a brand-new name, acquired or generated botted fake reviews to manipulate search optimization algorithms, and launched the software as a novel wallet option.

Because of this original-identity approach, the store listing presented virtually no immediate red flags to casual observers. There was no broken grammar in the descriptions, no unusual or overly broad permission requests, and no suspicious redirection loops pointing to shady third-party domains. The Chrome Web Store publisher page carried zero prior complaints, and the listed support URL led to an off-platform website that security trackers had not yet flagged at the time of Socket’s analysis.

Given its polished appearance and professional layout, the average user would likely experience no hesitation before clicking the "Add to Chrome" button. The extension requested permission to run on "all websites," which is a standard operational requirement for crypto wallets that need to interact seamlessly with various decentralized applications across the web. Notably, the software avoided prompting users for extra, suspicious permissions or attempting to inject complex content scripts that typically trigger Chrome’s more aggressive automated security warnings. The overall branding remained minimalist, the accompanying website matched the extension’s name precisely, and the initial setup screen guided users through standard procedures like creating a new wallet or importing an existing one—behavior indistinguishable from any legitimate application.

The Seed Heist, Broadcasted Over Sui

The real financial damage began the moment a user entered their recovery seed phrase. Instead of storing the sensitive phrase locally or properly encrypting it for authorized user access, the extension silently partitioned the phrase into small fragments. It then encoded these fragments into what appeared to be completely random, innocuous wallet addresses.

According to Socket’s in-depth research, these fragmented pieces were directly embedded into Sui blockchain transactions. Specifically, the extension initiated minuscule SUI token transfers—amounts so negligible they would never draw the attention of a casual observer—sent directly to addresses controlled by the malicious actors. Hidden inside these standard-looking blockchain transactions, either tucked away inside memo fields or cleverly obfuscated within the transaction addresses themselves, were the vital components of the victim’s seed phrase.

This tactical approach offered significant advantages to the attackers. It completely eliminated the need for the extension to send outbound network requests to external malicious servers. There was no command-and-control beacon communicating over HTTP or WebSockets, which are typical indicators that modern antivirus software or browser security guards look for.

Instead, the payload departed the user’s local device disguised as a completely normal blockchain transaction, routed securely through a widely adopted, low-fee layer-one network. Once safely on-chain, the data remained publicly accessible, allowing the attacker to retrieve the fragments at their leisure, reconstruct the master seed phrase, and systematically sweep the victim’s wallets without ever needing to touch the user’s device a second time.

In effect, the perpetrators utilized the Sui blockchain itself as an alternative communications channel. Because the Sui network features rapid transaction confirmation times and exceptionally low fees, it functioned remarkably well as a low-latency message bus for illicit data exfiltration.

Socket successfully traced multiple instances of these seed-fragment transactions, definitively confirming the direct link between seed entry and the subsequent loss of digital assets. While the actual thefts took place off-chain on Ethereum or other layer-one networks where the victims’ wallets held substantial balances, the operational instructions required to execute the thefts were hidden entirely in plain sight.

Before releasing the final version that managed to infiltrate Chrome’s top search results, the publisher likely tested the methodology in private development environments. Digital forensics reveal that earlier builds experimented with simpler data-leak mechanisms before the Sui encoding process was fully refined and optimized.

By the time the active extension was finally flagged and reported, it had accumulated enough installations to break into Chrome’s "trending" tier, which further amplified its visibility. Industry reports confirmed that the "Safery" wallet maintained its prominent placement among the top results for Ethereum wallet searches even as anxious users began circulating warnings about suspicious behaviors on community platforms like Reddit and Telegram.

How the Chrome Algorithm Let It Happen

The ultimate success of the "Safery" extension hinged heavily on the underlying mechanics of Chrome’s search ranking logic. The Web Store search algorithm evaluates a combination of factors, including keyword matching, total install counts, review velocity, average user ratings, and the recency of updates.

Extensions that experience a sudden burst of activity, particularly within niche categories like cryptocurrency tools, can climb search rankings rapidly if established, better-vetted competitors fail to update their listings frequently. In this instance, "Safery" benefited from a name that scored exceptionally well for common search queries, a coordinated blitz of positive reviews—many of which were templated or duplicated across multiple accounts—and a fresh upload timestamp.

Available evidence indicates that Google did not perform a manual review of the listing prior to publication. Standard Chrome Web Store policies typically subject new extensions to brief automated scans and 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, file systems, or browsing histories. Wallet extensions frequently manage to bypass these tighter triggers by operating safely within isolated iframes or utilizing standard, approved application programming interfaces. The "Safery" extension carefully operated within these established bounds.

Even when vigilant users raised concerns and submitted reports, the elapsed time between the initial flags and the eventual store takedown stretched out long enough for substantial financial damage to occur. Part of this lag is structural; the Chrome ecosystem does not automatically disable flagged extensions instantly unless there is an overwhelming consensus of reports or recognized malware signatures.

In this case, the underlying payload consisted of obfuscated JavaScript code that relied entirely on decentralized blockchain infrastructure rather than external hosting servers. Traditional, signature-based malware detection methods simply failed to catch it.

This incident is far from the first time browser extensions have been weaponized to target cryptocurrency holdings. Previous security threats have ranged from fraudulent Ledger Live applications prompting users to enter private recovery phrases to hijacked legitimate extensions that allowed attackers to compromise a developer’s official publishing key.

What distinguishes the "Safery" incident is the sheer smoothness of the front-end facade combined with the complete absence of traditional backend infrastructure. There was no centralized phishing website for authorities to take down, and no rogue command server to block—just a single browser extension quietly depositing secret fragments onto a public blockchain and walking away.

Impactful recourse for affected users remained narrow. Those who acted with extreme swiftness could limit their overall exposure by immediately rotating their seed phrases and revoking outstanding transaction approvals across various protocols.

Security firms like Socket quickly published triage guidelines for anyone who had mistakenly installed the extension: uninstall the software immediately, revoke all token approvals, sweep remaining digital assets to a newly generated wallet using an entirely clean and unaffected device, and continuously monitor associated blockchain addresses. For unsuspecting users who failed to notice the silent exfiltration or who kept substantial funds parked in vulnerable hot wallets, financial recovery remained highly unlikely.

The Real Trouble Begins Before the Wallet Ever Loads

In the wake of the incident, security researchers, developers, and industry analysts have intensified calls for stronger heuristic defenses built directly into the Chrome browser architecture. Among the primary proposals is the implementation of automated flags for any extension that incorporates user interface elements prompting individuals to input 12- or 24-word recovery phrases.

Another suggested defense involves requiring mandatory publisher attestation for all wallet-related extensions, offering verifiable cryptographic proof that a given publisher genuinely controls the codebase behind an established wallet brand. Industry advocates are also pushing for much tighter regulatory inspection of wallet-related permissions, even in cases where those permissions do not explicitly involve dangerous system access patterns.

For end-users navigating the Web3 landscape, security experts emphasize the importance of rigorous software management checklists. Before installing any cryptocurrency extension, users are advised to thoroughly review the publisher’s history, verify concrete associations with well-known and trusted projects, inspect review patterns for artificial bursts of identical feedback, cross-reference official websites with public code repositories like GitHub, and carefully scrutinize the permissions tab for vague or overly broad system access requests.

A clean interface, a professional name, and inflated ratings are no longer sufficient guarantees of safety. This episode raises profound, systemic questions regarding the browser’s expanding role as a primary gateway for decentralized finance.

Browser-based wallets gained widespread popularity primarily due to their accessibility and user-friendly nature, allowing individuals to interact effortlessly with decentralized applications without switching computing environments or downloading standalone desktop software. However, that accessibility has come at the direct cost of increased exposure. Modern web browsers represent high-risk environments vulnerable to extension manipulation, session hijacking, clipboard scrapers, and, as demonstrated by this incident, covert blockchain-based data exfiltration.

As a result, wallet developers are likely to reevaluate their distribution models in the near future. Some development teams already actively discourage users from relying on Chrome Web Store installations, preferring instead to direct communities toward dedicated mobile applications or standalone desktop binaries. Others may soon introduce active warnings within their ecosystems whenever users attempt to download software from unverified sources.

The underlying challenge persists: software distribution remains fragmented, and the vast majority of everyday users lack the technical expertise required to distinguish a genuinely secure wallet from a polished, malicious clone. The "Safery" extension proved that attackers no longer need to imitate established giants like MetaMask or Phantom to succeed. By engineering an original brand, manufacturing artificial trust signals, and constructing an invisible backdoor utilizing the Sui blockchain as a courier, the creators exposed deep vulnerabilities in modern Web3 user experience models.

This security failure forces a fundamental reassessment of how trust is established within decentralized finance applications, and how close to underlying system layers even casual auxiliary tools like browser extensions truly operate. Cryptocurrency participants inherently assume that the principles of Web3 guarantee absolute digital sovereignty and self-custody. Yet in compromised hands, a standard browser wallet ceases to function as a secure vault, transforming instead into an open port—proving that the browser environment will not always issue a warning before a threat slips through.