Grinex, a Kyrgyzstan-based cryptocurrency exchange currently under U.S. and U.K. sanctions, has announced a complete shutdown of its operations after suffering a devastating hack. The incident, which occurred around April 15, 2026, resulted in the theft of over 1 billion rubles (approx. $13.74 million) in user funds. The attackers demonstrated sophisticated knowledge of cryptocurrency laundering techniques, immediately swapping stolen Tether (USDT) stablecoins for non-freezable assets like Ether (ETH) and Tron (TRX). Blockchain intelligence firms, including TRM Labs and Chainalysis, have tracked the stolen funds to approximately 70 addresses. In a highly unusual statement, Grinex has accused Western intelligence agencies of orchestrating the attack, a claim that remains unsubstantiated. A related exchange, TokenSpot, was also impacted in a smaller, concurrent incident.
The attack targeted the hot wallets of the Grinex exchange, leading to the unauthorized withdrawal of a significant volume of cryptocurrency. The primary stolen asset was Tether (USDT), a stablecoin pegged to the U.S. dollar. The attackers' immediate priority after the theft was to launder the funds and make them untraceable and unrecoverable. This was achieved by rapidly swapping the USDT for more decentralized cryptocurrencies on various decentralized exchanges (DEXs). Tether Inc., the issuer of USDT, has the ability to freeze tokens associated with illicit activity, so this rapid swap is a critical step for attackers to secure their loot.
TRM Labs has identified around 70 addresses involved in the laundering process. The simultaneous, smaller attack on TokenSpot, with funds being funneled to the same consolidation addresses, suggests that both exchanges were linked and likely shared vulnerable infrastructure or credentials.
While the initial access vector is unknown, the post-exploitation TTPs are clear and align with common crypto-heist tactics.
T1402.001 - Private Keys: The core of the attack was the theft of the private keys controlling the exchange's funds.T1499.003 - Transfer Cryptocurrency).T1499.004 - Obscure Cryptocurrency Transfers). By converting USDT to ETH and TRX, the attackers moved the assets off a centralized platform where they could be frozen and into more censorship-resistant blockchains.Grinex's claim of a state-sponsored attack is a common tactic for compromised entities to deflect blame, although not impossible given the exchange's sanctioned status. However, the TTPs observed are also well within the capabilities of sophisticated cybercriminal groups like the Lazarus Group.
TRM Labs has identified approximately 70 cryptocurrency addresses associated with the hack, but these were not listed in the source articles.
Detection (for Exchanges):
Response:
Protect private keys by storing them in Hardware Security Modules (HSMs) and using multi-signature schemes.
Enforce MFA for all administrative access to exchange infrastructure and key management systems.
Mapped D3FEND Techniques:
Strictly limit and monitor accounts that have privileged access to withdrawal and key management functions.
Mapped D3FEND Techniques:
For any cryptocurrency exchange, the 'crown jewels' are the private keys that control the funds. To prevent a catastrophic theft like the one at Grinex, these keys must be protected by a Hardware Security Module (HSM). An HSM is a physical device designed to securely store cryptographic keys and perform operations with them without ever exposing the keys themselves. This provides a strong defense against remote software-based attacks that aim to steal key files. For an exchange's hot wallets, transactions should be signed within the HSM, meaning the private keys never leave the tamper-resistant hardware. This single control makes it exponentially more difficult for an attacker to steal funds, as they would need physical access to the HSM or would have to find a vulnerability in the HSM's firmware itself, a far more complex task than compromising a standard server.
To prevent a single point of failure, exchanges like Grinex must use multi-signature (multisig) wallets for all significant funds. A multisig wallet requires M-of-N independent parties to approve a transaction before it can be executed. For example, a 3-of-5 multisig scheme would require three out of five designated keyholders to sign off on any withdrawal. These keys should be held by different senior individuals within the company and stored in geographically separate and secure locations. This means that even if an attacker compromises one or even two keyholders, they still cannot move the funds. This D3FEND technique provides powerful protection against both external hacks and insider threats, as it enforces a distributed consensus model for all transactions, preventing a single compromised key or malicious actor from draining the exchange's wallets.
As a real-time detection and response control, exchanges must implement Transaction Volume Analysis. This involves setting up automated systems that monitor the volume and velocity of withdrawals from the exchange's hot wallets. The system should have predefined thresholds, for example, 'no more than $1 million withdrawn in any 1-hour period' or 'no more than 5% of total hot wallet funds moved without manual review.' If a series of transactions exceeds these limits, the system should automatically trigger a 'circuit breaker,' temporarily halting all outbound transfers and sending a high-priority alert to the security and finance teams. This automated control could have limited the damage at Grinex from $13.74 million to a much smaller amount, giving the team time to investigate the initial suspicious activity and move the remaining funds to secure cold storage.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats