For a few critical days last November, a malicious browser extension masquerading as a crypto wallet managed to secure the fourth spot in the search results for "Ethereum wallet" on the official Chrome Web Store. The deceptive application, titled "Safery: Ethereum Wallet," successfully bypassed automated checks and user skepticism alike through a combination of polished design, algorithmic optimization, and an innovative data exfiltration technique that utilized the Sui blockchain as a silent communication channel.
The incident has since been thoroughly documented and analyzed by Socket, a security tooling firm specializing in open-source software supply chains. After discovering the fraudulent extension, researchers at Socket installed and dissected the software to understand how it evaded detection, climbed the store’s trending rankings, and exfiltrated sensitive user data without raising immediate alarms. Their findings serve as a stark postmortem and a timely warning that browser extensions remain a dangerously overlooked blind spot within the broader cryptocurrency ecosystem.
What sets the Safery incident apart from typical crypto scams is that the attackers did not rely on traditional phishing tactics. They did not spoof an existing, trusted wallet brand, nor did they utilize a MetaMask lookalike interface or a recycled phishing domain. Instead, the malicious actors manufactured an entirely new identity. They purchased or generated bot-driven fake reviews to artificially inflate their search ranking and launched the software as a novel, independent wallet option.
Because the extension did not impersonate a known brand, its store listing displayed virtually none of the standard red flags that experienced users have learned to spot. There was no broken grammar in the description, no demand for suspicious or unauthorized permissions, and no automated redirection to shady, unverified external domains. Furthermore, the Chrome Web Store publisher page carried no prior user complaints or warning flags, while its designated support URL directed traffic to an off-platform website that security trackers had not yet flagged at the time of Socket’s investigation.
Given the professional and clean presentation of the listing, the average user would have felt little hesitation before clicking the "Add to Chrome" button. The extension requested permission to run on all websites—a standard, mandatory requirement for legitimate crypto wallets that must interact seamlessly with a wide variety of decentralized applications. Notably, the software refrained from prompting for extra privileges or attempting to inject complex content scripts that might have tripped Chrome’s more aggressive security warnings. The overall branding was minimalist, the companion website matched the exact name of the extension, and the initial setup screen simply prompted users to create a new wallet or import an existing one, mimicking entirely standard operational behavior.
The Seed Heist, Broadcast Over Sui
The true mechanics of the scam were unleashed the moment a user entered their seed phrase. Rather than storing the recovery phrase locally or employing encryption for user management, the extension executed a silent, malicious routine. It fragmented the seed phrase into smaller pieces and encoded those fragments into what appeared to be entirely random, innocuous wallet addresses.
According to Socket’s technical analysis, these fragmented pieces were embedded directly into Sui blockchain transactions. The extension initiated minuscule SUI token transfers—amounts so small they would naturally draw zero attention—directed toward addresses controlled directly by the hackers. Embedded quietly inside those transactions, either hidden within memo fields or obfuscated directly within the structure of the 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 malicious command-and-control servers. There was no external beaconing, and no data exfiltration occurred over standard HTTP or WebSockets protocols that modern browsers or antivirus programs are typically programmed to flag.
Instead, the stolen payload left the victim’s device disguised as an ordinary, everyday blockchain transaction routed through a widely used, low-fee layer-1 network. Once the data successfully reached the blockchain, it became publicly accessible in the ledger, allowing the perpetrators to retrieve the fragments at their leisure, reconstruct the complete seed phrases, and sweep associated assets clean without ever needing to interact with the victim’s device a second time.
In effect, the operation weaponized the Sui blockchain itself, turning it into a low-latency message bus. Because the Sui network boasts exceptionally fast transaction confirmation times and virtually negligible gas fees, it functioned as an ideal courier for stolen secrets. Socket successfully traced multiple instances of these seed-fragment transactions, definitively confirming the direct link between entering a seed phrase into the extension and the subsequent loss of funds. While the actual thefts occurred off-chain—typically on Ethereum or other layer-1 networks where the victims’ wallets held significant capital—the precise operational instructions required to steal those funds were hidden entirely in plain sight.
Evidence uncovered by security researchers indicates that before launching the version that eventually claimed a top spot in Chrome’s search results, the publisher likely tested the methodology in private experimental builds. Earlier iterations appeared to test simpler data leaks before the Sui encoding mechanism was thoroughly refined. By the time the active, malicious extension was finally flagged and removed, it had accumulated enough installations to secure a prominent spot in Chrome’s trending tier, amplifying its visibility just as reports of suspicious behavior began circulating across community platforms like Reddit and Telegram.
How the Chrome Algorithm Let It Happen
The rapid rise and success of the Safery extension were largely enabled by the inherent mechanics of Chrome’s search and discovery algorithm. The Web Store search engine weighs multiple factors, including keyword matches, total install counts, review velocity, average star ratings, and the recency of software updates.
When an extension experiences a sudden, artificial burst of activity—particularly within specialized niches like cryptocurrency tools—it can climb the rankings rapidly, especially if established, well-vetted competitors fail to update their listings frequently. In this particular instance, Safery benefited from a title optimized for common search queries, a coordinated blitz of positive yet templated reviews, and a very recent upload date.
Available evidence indicates that Google did not subject the listing to manual human review prior to publication. Chrome Web Store policies typically subject new software submissions to automated scans and basic static analysis. Extensions generally face deeper, more rigorous scrutiny only when they request heavily elevated permissions, such as direct access to browser tabs, the system clipboard, local file systems, or browsing history. Because legitimate wallet extensions frequently manage to bypass these specific warning flags by operating within isolated iframes or utilizing approved APIs, Safery was able to remain safely within those accepted technical bounds.
Even after vigilant users began raising concerns, the operational lag between the initial public reports and the eventual takedown of the extension stretched on long enough for substantial financial damage to occur. Part of this delay is structural; the Chrome ecosystem rarely acts on flagged extensions instantaneously unless there is an overwhelming consensus of abuse or recognizable malware signatures present in the code. Because Safery relied on obfuscated JavaScript combined with legitimate blockchain infrastructure rather than external malicious hosting sites, traditional automated detection tools failed to catch it in time.
While browser-based cryptocurrency scams are unfortunately not entirely new—ranging from fake Ledger Live desktop applications to hijacked legitimate extensions that expose developer publishing keys—the Safery incident underscored a troubling evolution. The lack of traditional backend infrastructure meant there was no malicious phishing website to shut down and no centralized server IP address to block. There was merely an unassuming browser extension quietly translating confidential secrets into on-chain data packets and walking away.
For impacted individuals, remediation options were extremely narrow. Security analysts from Socket and other firms outlined urgent triage steps for anyone who had installed the extension: uninstalling the software immediately, revoking existing token approvals, sweeping remaining assets to an entirely new wallet generated on a clean, uncompromised device, and continuously monitoring associated blockchain addresses. For users who failed to notice the silent exfiltration in time, or who maintained large balances within vulnerable hot wallets, asset recovery remained virtually impossible.
Industry experts, developers, and security researchers are now intensifying calls for more robust heuristic defenses within the Chrome Web Store. Proposed solutions include automatically flagging and quarantining any extension that incorporates user interface elements explicitly designed to prompt for standard recovery phrases. Additional recommendations include mandatory publisher attestation for wallet-related software, providing verifiable cryptographic proof that a given developer actually controls the codebase of an established brand, and enforcing stricter permission inspections for financial tools regardless of whether they utilize traditional dangerous access patterns.
Ultimately, the Safery incident has reignited broader industry conversations regarding the inherent vulnerabilities of relying on web browsers for asset management. While browser-based wallets gained widespread popularity due to their accessibility and convenience, allowing users to interact smoothly with decentralized applications without switching platforms, that high degree of accessibility has come with severe security trade-offs. As long as the browser remains a high-risk environment susceptible to extension manipulation and covert blockchain exfiltration, users navigating the Web3 landscape will continue to face sophisticated threats that standard digital storefronts struggle to intercept.

