{"id":12980,"date":"2018-11-27T00:00:00","date_gmt":"2018-11-26T16:00:00","guid":{"rendered":"https:\/\/www2019.dash.org\/2018\/11\/27\/dash-is-not-affected-by-the-bitpay-copay-attack\/"},"modified":"2021-09-18T11:36:27","modified_gmt":"2021-09-18T11:36:27","slug":"dash-not-affected-copay-attack","status":"publish","type":"post","link":"https:\/\/www.dash.org\/news\/dash-not-affected-copay-attack\/","title":{"rendered":"Dash is not affected by the BitPay Copay attack"},"content":{"rendered":"

Good day everyone !<\/p>\n

You might have seen the news on GitHub, Twitter, ZDNet, and various other places on the net.
\nThe whole JavaScript ecosystem discovered an attack targeting BitPay\u2019s Copay product.In order to be sure the compromised package was included in Copay during the building phase, the attacker had to spread an ingenious, obfuscated and malicious code across the whole ecosystem.This malicious code was looking for a description of a package (bunch of code that works as libraries to enhance programmer\u2019s productivity) that had the specific message, \u201cA Secure Bitcoin Wallet\u201d, and used that as a decryption key to unveil and execute the dormant code.<\/p>\n

This matched two projects: Copay, and our first fork of copay created 2 years ago while Dash was studying the idea of using Copay as a foundation for DashPay. We did not pursue this idea further, and that project was never used.<\/p>\n

The Dash Copay Beta that we worked on and released was not targeted and therefore won\u2019t manage to steal your funds.<\/p>\n

\u200b<\/p>\n

Here is the exact naming thing that got everyone (including ZDNet at one point) confused:<\/p>\n