Russian Nuclear Plant Internal Network Infected with Stuxnet - BestCyberNews: Online News Presenter in the present world

BestCyberNews: Online News Presenter in the present world

Start knowing

test banner

Breaking

Russian Nuclear Plant Internal Network Infected with Stuxnet

Stuxnet had infected the internal network of a Russian nuclear plant after the sophisticated malware caused chaos in Iran's nuclear facilities in Natanz.

Kasperky security CEO Eugene Kaspersky had reveled the Russian Nuclear Plant Internal Network Infected with Stuxnet, he got the information for a staffer at the unnamed nuclear plant informed him of the infection. Kaspersky said

“So unfortunately these people who were responsible for offensive technologies, they recognize cyber weapons as an opportunity”.

Stuxnet virus is the powerful malware that for the first time has shown to governments the capabilities and efficiency of a cyber weapon.


After its disclosure it’s risen the debate on the use of software and malicious application in Information warfare, every government is investing to improve its cyber capabilities working on both Defense and Offense sides.

The malware Stuxnet is widely considered to have been developed by the US Government in a joint work with Israel cyber units as a means to disrupt Iran’s nuclear enrichment plans.

In a presentation given at the Canberra Press Club designed to give mainstream journalists a broad overview of the state of information security, the chief executive offered his view of the state of online crime and state-sponsored espionage.

”All the data is stolen,” Kaspersky said. “At least twice.”

Kaspersky also focused on Gauss, Flame and Red October and also Kaspersky stated that more than 50% of malware were written in Chinese,  nearly 33% were written in Spanish or Portuguese, followed by Russian-coded malware, this last group is considerably very dangerous because the malicious code it products is the most sophisticated in the world.

If the claim of the Russian nuclear plant infection is true, then it’s easy to imagine how this “collateral damage” could have turned into a very serious incident indeed, with obvious diplomatic repercussions.

No comments:

Post a Comment