WhiteRose Ransomware
This content has been archived
This article no longer conforms to NHS Digital's standards for cyber alerts, and may contain outdated or inaccurate information. Use of this information contained in this page is at your own risk
Summary
Affected platforms
The following platforms are known to be affected:
Threat details
At the time of publication it is unclear how WhiteRose is being distributed, with unconfirmed reports indicating it is being manually installed using Remote Desktop services.
When installed WhiteRose will check for the presence of file in the C drive, Perfect.sys, and will cease operations if it is detected. If it is not, WhiteRose will create the file before scanning all connected drives on the targeted device and encrypting them. Files contained within the Windows, Program Files, $Recycle.Bin and Microsoft folders are ignored.
It also appears that decryption tools are available that are able to recover files encrypted by WhiteRose, although these have not been verified by CareCERT and are used at an organisation's risk.
Remediation steps
| Type | Step |
|---|---|
|
If a device on your network becomes infected with ransomware it will begin encrypting local machine files and files on any network the logged-in user has permission to access. For system administration accounts this may include backup storage locations. To avoid becoming infected with ransomware, ensure that:
Identifying the source of infection:
To limit the damage of ransomware and enable recovery:
The only guaranteed way to recover from a ransomware infection is to restore all affected files from their most recent backup. Additionally, if RDP is not used then ensure port 3389 (TCP/UDP) is blocked at your internet firewall. If RDP is used:
|
Last edited: 17 February 2020 12:57 pm