GOPAX stopped trading, digital-asset deposits and standard withdrawals on Friday after receiving an email threatening a hack. The South Korean exchange kept a support-based route for withdrawal requests while it moved most assets from connected hot wallets into offline cold storage.
GOPAX moves most hot-wallet balances
The exchange described the transfer as a precaution and said it had not lost any assets. Customers seeking withdrawals must contact support; staff process requests one by one after internal checks and approval. GOPAX cautioned that this manual arrangement could take longer than normal, and reports dated 6 November 2026 gave no date for services to resume.
Support keeps a manual route
The change comes after GOPAX disclosed on 16 October that information relating to seven customers and two current or former employees had been exposed. The exchange said unusual access to accounts started in early September and was identified in early October. The available account does not link that earlier exposure to the hacking-threat email that preceded the suspension.
Earlier data exposure came first
Across 37 companies, the Financial Services Commission (FSC) logged 40 incidents between September 30 and November 3. The cases involved approximately 473,000 personal-information records.
About KRW1 billion, approximately US$745,000, was reported stolen, chiefly from company management accounts; the regulator had not identified losses by individual users. Bithumb was also affected: an intrusion in its employee-support system led to an FSC emergency meeting on 28 October, followed by reports of customer-data exposure.
South Korean oversight expands checks
The FSC has ordered inspections at about 580 financial companies and told firms to halt affected operations when vulnerabilities are found. As Finance Magnates reported, the incidents sit within a wider pattern of attacks on financial institutions; the report also cites a $6.3 billion cryptocurrency theft from Binance attributed to North Korean hackers.
Where this lands in the stack
For exchange operators, the immediate operational pressure falls on wallet controls and withdrawal processing. Teams should establish which balances have moved offline, how support verifies each request and what approvals are needed before standard withdrawals can restart. GOPAX has not published a resumption timetable.
The account does not specify whether the threat involved signing infrastructure or prompted a precautionary response without access to wallet keys. Operators should seek clarity on that point, and on what reconciliation records will be available for manually approved withdrawals while normal processing is suspended.
Operations teams should also check what conditions would allow affected services to resume and how those decisions align with the regulator's instruction to suspend operations where vulnerabilities are identified. The story does not detail GOPAX's criteria, so those controls and communications remain points to clarify.
Platforms · Software · Providers · Markets