C
Comae Blog
blog.comae.io · Company blog · on HN since 2017
Comae, a security firm, writes technical analyses of malware outbreaks like WannaCry and Petya, and of Ethereum smart contract bugs.
What HN saysHN links it for the Parity multisig bug writeup and WannaCry analysis; commenters cite the bug as a reason to distrust Ethereum.
18HN people shared it
3linked it in comments
17stories submitted
468story points
6 years agolast shared
2017people per year2026
Most-shared posts
- 1The $280M Ethereum bug3 people · 30 points · first shared 2017 · 13 comments on HN
- 2Petya.2017 is a wiper not a ransomware3 people · 16 points · first shared 2017 · 1 comments on HN
- 3Lessons from TV5Monde 2015 Hack3 people · 3 points · first shared 2017 · discussion on HN
- 4WannaCry – The largest ransom-ware infection in history2 people · 140 points · first shared 2017 · 76 comments on HN
- 5WannaCry – Decrypting files with WanaKiwi and Demos2 people · 7 points · first shared 2017 · 2 comments on HN
- 6Smart Contract Languages Development to Follow2 people · 3 points · first shared 2017 · discussion on HN
- 7DEF CON 25: Porosity Decompiling Ethereum Smart-Contracts2 people · 3 points · first shared 2017 · discussion on HN
- 8WannaCry – New Variants Detected1 people · 265 points · first shared 2017 · 159 comments on HN
- 9Going beyond log files, accepting memory as its own format1 people · 1 points · first shared 2018 · discussion on HN
- 10Wannacry links to lazarus group dcea72c99d2d1 people · first shared 2017
What HN people wrote when they linked it
nikcub · 2017-12-21
There is a lot of independent analysis pointing at North Korea[0][1][2][3]
The infosec industry are extremely skeptical of attribution especially coming from government - it took a long time for a higher-certainty attribution to be established in the Sony and Bangladesh reserve bank cases, and there are still open cases of attribution in other incidents
Along with technical evidence, Wannacry also fits the North Korea m.o of financial incentive but also incentive to sow chaos[12], as well as how their attackers operate in Singapore and China and outsource some components.
On the contrary there is little to no evidence pointing anywhere else - meaning the second best probability of attribution for Wannacry is much further down the list.
The key difference there is that during the Iraq invasion there was zero corroborative evidence, the actual weapons inspectors said there was no evidence.
Further - the USA doesn't need a made-up pretext for war with North Korea. They're technically still at war and North Korea are in violation of UN Security Council resolutions and treaties (they routed around the UN for Iraq)
North Korea has sunk a ship[4], downed an airliner[5], attacked South Korean islands[6], tested nuclear weapons, developed a missile program, fired across the DMZ[7] (as recently again as today[8]), assassinated foreigners on foreign soil[9], been caught attempting to sell weapons of mass destruction[10], sold arms to Syria and others in violation of sanctions[11]…
xiphias2 · 2020-11-24
I stopped trusting Ethereum in 2017 at the Parity multisig bug: https://blog.comae.io/the-280m-ethereums-bug-f28e5de43513
Even in the bug fix there wasn't any unit testing involved. I'm using multisig to store all my Bitcoins, so it scared me extremely. With Bitcoin I read through the multisig code (stack machine) before putting money onto the blockchain. With Ethereum the code changes so fast, that with all the hard forks I wouldn't be able to verify the code. ,,Don't trust, verify'' doesn't work there.
jarins · 2018-05-15
They may have changed it in recent versions, but for a long while, functions were public by default (i.e. anyone can call them). Defaulting to open is a huge security flaw and the reason behind the Parity bug https://blog.comae.io/the-280m-ethereums-bug-f28e5de43513