Attacks/Breaches

6/28/2017
12:15 PM
100%
0%

Researchers Find 'Vaccine' for Global Ransomware Attack

A vaccine, not a killswitch, has been discovered to prevent the Petya/NotPetya ransomware from infecting machines.

Researchers have yet to discover a killswitch that would prevent the spread of this week's massive ransomware outbreak, but one has found a "vaccine" that can halt the spread of the attack, reports BleepingComputer.

The rapidly spreading ransomware hit businesses, including those in critical infrastructure, across Russia, Ukraine, France, Netherlands, Spain, India, and Denmark. Some experts found similarities with the Petya malware, including its encryption of the Master Boot Record (MBR) on infected systems. Others say this malware hasn't been previously seen and call it NotPetya.

Amit Serper, a security researcher with Cybereason, discovered the ransomware operates by searching for a local file, and will exit the encryption process if the file already existed on the disk. Victims can block the ransomware from executing by creating this file on their machines.

To implement the vaccination, create a file called "perfc" in the "C:\Windows" folder and set it to read-only. Researchers call this a vaccination, not a killswitch, because it only vaccinates the machine where it's stored. A killswitch could be turned on to prevent all incidents of this ransomware.

Read more details here.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
RyanSepe
100%
0%
RyanSepe,
User Rank: Ninja
6/28/2017 | 12:25:27 PM
Nifty
Wow, this is nifty. Discovering the trigger and inserting it before the malware creates it maliciously is quite smart. What isn't smart however on the end of the creators of the malware is creating a check predicated on only one file.
6 Ways Greed Has a Negative Effect on Cybersecurity
Joshua Goldfarb, Co-founder & Chief Product Officer, IDRRA ,  6/11/2018
Weaponizing IPv6 to Bypass IPv4 Security
John Anderson, Principal Security Consultant, Trustwave Spiderlabs,  6/12/2018
'Shift Left' & the Connected Car
Rohit Sethi, COO of Security Compass,  6/12/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2018-12026
PUBLISHED: 2018-06-17
During the spawning of a malicious Passenger-managed application, SpawningKit in Phusion Passenger 5.3.x before 5.3.2 allows such applications to replace key files or directories in the spawning communication directory with symlinks. This then could result in arbitrary reads and writes, which in tur...
CVE-2018-12027
PUBLISHED: 2018-06-17
An Insecure Permissions vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 causes information disclosure in the following situation: given a Passenger-spawned application process that reports that it listens on a certain Unix domain socket, if any of the parent directories of said ...
CVE-2018-12028
PUBLISHED: 2018-06-17
An Incorrect Access Control vulnerability in SpawningKit in Phusion Passenger 5.3.x before 5.3.2 allows a Passenger-managed malicious application, upon spawning a child process, to report an arbitrary different PID back to Passenger's process manager. If the malicious application then generates an e...
CVE-2018-12029
PUBLISHED: 2018-06-17
A race condition in the nginx module in Phusion Passenger 3.x through 5.x before 5.3.2 allows local escalation of privileges when a non-standard passenger_instance_registry_dir with insufficiently strict permissions is configured. Replacing a file with a symlink after the file was created, but befor...
CVE-2018-12071
PUBLISHED: 2018-06-17
A Session Fixation issue exists in CodeIgniter before 3.1.9 because session.use_strict_mode in the Session Library was mishandled.