OKX Wallet: Not affected by third-party component security incidents, both APP and Web3 can be used safely

On September 9th, in response to the "NPM supply chain attack" incident, OKX Wallet said that OKX always puts system security first, and strictly controls the risk of using third-party components in the whole process of Product Research & Development and launch. After internal verification and evaluation, OKX APP is based on Android and iOS native framework development, and there is no relevant security risk; OKX plug-ins, web applications and mobile end DApp browsers do not use affected versions of third-party components, platform services are running normally, users can continue to use with peace of mind.
It is reported that the attackers stole the NPM account credentials of developer qix through phishing emails (disguised as npmjs support), and then injected malicious code into 18 popular JavaScript packages (including chalk, debug-js, etc., which were downloaded more than 2 billion times a week). This attack is considered to be the largest supply chain attack in history.
It is worth noting that the malicious code does not attempt to plant a Trojan or steal files in the local environment, but specifically targets the Web3 scenario: if it detects the presence of window.ethereum in the browser environment, it hijacks the transaction request. The malicious code redirects funds to an attacker-controlled address (e.g. Ethereum address 0xFc4a4858...) by tampering with the browser's Ethereum and Solana transaction requests, and steals assets by replacing the encrypted address in the JSON response. Although the page shows a normal transaction address, the actual funds are transferred to the attacker's address.