In 2017 – For the first time in more than a decade – computer worm has erupted over the Internet, threatening to disrupt businesses, industries, governments and national infrastructure across multiple continents.
WannaCry ransomware has become the biggest threat to the Internet since the Mydoom worm in 2004. On May 12, 2017, the worm infected millions of computers, encrypted their files and held them hostage for the payment of Petequin.
Train stations, government departments and Fortune 500 companies were suddenly attacked. The National Health Service (NHS) in the UK was one of the largest organizations to have been conducted, forcing doctors to remove patients Emergency rooms to close.
Earlier this week we reported Deep Diving Story In the 2017 cyber attack that has not been reported before.
British security researchers – Marcus Hutchins and Jimmy Hankins – recorded a domain name in the WannaCry code to track the infection. It took them three hours to realize that they had inadvertently stopped the attack on its tracks. This area became the infamous "killing key" that immediately stopped the ransom.
As long as the switch remains on the Internet, its computer files will not be encrypted using WannaCry.
But the attack is not over yet.
In the following days, the researchers were attacked by one of the angry robots who hit the field with unwanted traffic in an attempt to hit them offline and the police in France took over two of their servers believing they were contributing to Spread ransom.
Worse yet, their exhaustion and lack of sleep threatened to disrupt the process. The kill key was later transferred to Cloudflare, which has technical support and infrastructure support for its survival.
Hankins described him as "the most stressful thing" he has ever experienced. "The last thing you need is the whole NHS idea on fire," he told TechCrunch.
Although the key to killing is in good hands, the Internet is just a failure in one area away from WannaCry's outbreak. Just last month Two Cloudflare failed Threatened to fetch killing field switch currently. Luckily, I stayed without a hitch.
CISOs and CSOs take note: Here's what you need to know.