Maria Kregul 🌸

This cartoon makes me feel both proud and under tremendous pressure. I will never claim that OKX is absolutely safe or immune to attacks. No company can honestly make that promise. What I can say is that OKX has always treated security and the protection of customer assets as our highest priority. Our 13-year track record reflects more than a decade of continuous investment, engineering, operational discipline, and hard-earned experience. We take security threats seriously and professionally—not as a marketing opportunity. Behind the scenes, we have built extensive layers of proprietary technology, internal security systems, strategies, frameworks, penetration testing, and independent audits. Much of this infrastructure cannot be disclosed publicly for security reasons. But these capabilities are constantly being tested, challenged, and improved. Here’s something I can share: since the recent Binance security incident, the entire OKX team has been working just as hard and staying just as busy as the teams directly responding to the attack. Not because OKX was compromised. But because an attack on one major exchange is a warning to the entire industry. While some may see such moments as opportunities to launch promotional campaigns, generate traffic, or compete for market share, our priority has been different. Our teams have been working around the clock on four critical areas: 1. Tracking stolen funds in real time. Monitoring the movement of funds associated with the incident with second-level latency, identifying suspicious addresses and transactions, and taking available measures to prevent stolen funds from being laundered through OKX Exchange or our Web3 DEX aggregator. 2. Strengthening market risk controls. Assessing the potential market impact of the incident, tightening risk controls where necessary, and preparing for liquidity shocks or cascading liquidations that could threaten users and the broader market. 3. Analyzing emerging attack techniques. Studying the attack patterns, potential vulnerabilities, and methodologies involved, including threats to software development supply chains and the rapidly evolving security risks introduced by AI coding agents and their dependencies. 4. Challenging our own security assumptions. Using the lessons from this incident to conduct a fundamental review of our internal controls, access management, wallet infrastructure, and security architecture. We don’t assume that what protected us yesterday will necessarily protect us tomorrow. Security is never a finished project. It is a continuous responsibility that requires humility, vigilance, investment, and execution. We don’t choose to be the loudest when another company is under attack. We choose to work harder to protect our customers and strengthen the resilience of the entire industry. Competition should drive better products and services. Security should bring the industry together. Protecting customer assets is our first responsibility. And we will never take your trust for granted.