ME News reports that on July 13 (UTC+8), Qubic announced on Twitter that its GitHub organization experienced a security incident today, during which a compromised account was used to access code repositories and extract keys. The team has detected the breach and is currently addressing it. Qubic advises Network Guardians to immediately rotate their mnemonic phrases; users who unlocked their web wallets between 11:00 and 18:00 today should migrate to new identities immediately; developers must not pull or deploy code from Qubic repositories until official confirmation that an audit has been completed. Further details and updates will be posted on the official Discord channel, and a post-incident review report will be published after resolution. (Source: Foresight News)
Qubic GitHub Account Compromised; Users Urged to Migrate Wallets Immediately
KuCoinFlashShare
Summary
Qubic confirmed a security breach on its GitHub account on July 13 (UTC+8), during which an unauthorized user accessed code repositories and extracted keys. The team has taken corrective action and urged all Network Guardian users to immediately rotate their mnemonics. Users who accessed web wallets between 11:00 and 18:00 should migrate to new identities. Developers are advised to pause code pulls or deployments until the network upgrade is complete. Updates will be posted on Discord, with a full incident report to follow.
Source:Show original
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information.
Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.