crypto
3 articles with this tag
Chainalysis Security Incident (October-November 2026): Names, Usernames, Password Hashes and Live Tokens of All Users Exposed, and What Customers Should Do
The blockchain analytics company Chainalysis published a notice about a security incident on October 30, 2026 and has updated it since. In its November 4 update, the company says the names, usernames, password hashes and live tokens of all users were exposed to a malicious actor. It says it has no evidence that investigations data was accessed or that attribution data was tampered with. An earlier update that morning says an on-path attack exposed a subset of customers' passwords, and that affected accounts were locked and had to reset. The company paused KYT, address screening and the login page, and on November 6 began restoring KYT and address screening in phases. No restore date is given for Reactor and Data Solutions. Customers are asked to request allowlisting of trusted IP addresses, reset passwords and rotate API keys. The October 30 notice said there was no evidence of access to authentication credentials or session tokens; later updates describe token exposure, and the page does not explain the difference.
Polymarket Trading Halted After a Third-Party Script Was Compromised: What Users and Site Operators Should Do
On October 29, 2026, Polymarket's status page reported that its international platform (Polymarket.com) went into cancel-only mode at 2:05 p.m. ET, that a third-party provider had been compromised, that the matter was referred to law enforcement and that anyone impacted will be made whole; trading was temporarily halted at 2:37 p.m. ET out of an abundance of caution and expected to resume around 3 p.m. ET. Press reports, citing a security research firm, say the provider was a website performance-monitoring service whose script ran on Polymarket's pages and was used to sell or move logged-in users' holdings, and put the amount traced at roughly $2.2 to $2.7 million depending on the outlet. In a post-mortem on its status page dated October 30, Polymarket said it is returning $3.9 million (about $2.7 million in refunds for drained wallets and positions taken during the attack, and $1.2 million for losses tied to the trading pause), that no claim or ticket is needed because it identified eligible wallets from on-chain and trading data, and that it removed the vendor's script, paused trading and reset all active login sessions. Per press, the vendor's initial finding is that it was compromised through its domain registrar. The post-mortem does not give the number of users affected. This site's take: since Polymarket says no claim is needed, users should treat any message asking them to claim or collect a refund as a possible scam and use only the official site, and site operators should inventory every third-party script on pages where users are logged in.
Coincheck NEM Heist (2018) — How ~$530M Was Stolen, and the Key-Management Defense
The entry point was reported to be spear-phishing / malware aimed at employees, which stole the private key of an internet-connected hot wallet; ~523 million XEM (~$530M at the time) was then moved out in a single transfer. The core failure was keeping a huge, instantly-spendable balance in an online wallet with no multisig, so a single stolen key moved almost everything. Defend by keeping important keys offline or in a dedicated key store (HSM/KMS), minimizing the hot balance, removing single points of failure (multi-approval), and detecting and stopping abnormal bulk operations.