BitPaymer is a ransomware variant first observed in August 2017 targeting hospitals in the U.K. BitPaymer uses a unique encryption key, ransom note, and contact information for each operation. BitPaymer has several indicators suggesting overlap with the Dridex malware and is often delivered via Dridex.[1]
Name | Description |
---|---|
wp_encrypt | |
FriedEx |
Domain | ID | Name | Use | |
---|---|---|---|---|
Enterprise | T1548 | .002 | Abuse Elevation Control Mechanism: Bypass User Account Control |
BitPaymer can suppress UAC prompts by setting the |
Enterprise | T1134 | .001 | Access Token Manipulation: Token Impersonation/Theft |
BitPaymer can use the tokens of users to create processes on infected systems.[1] |
Enterprise | T1087 | .001 | Account Discovery: Local Account |
BitPaymer can enumerate the sessions for each user logged onto the infected host.[1] |
Enterprise | T1547 | .001 | Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder |
BitPaymer has set the run key |
Enterprise | T1543 | .003 | Create or Modify System Process: Windows Service |
BitPaymer has attempted to install itself as a service to maintain persistence.[1] |
Enterprise | T1486 | Data Encrypted for Impact |
BitPaymer can import a hard-coded RSA 1024-bit public key, generate a 128-bit RC4 key for each file, and encrypt the file in place, appending |
|
Enterprise | T1480 | Execution Guardrails |
BitPaymer compares file names and paths to a list of excluded names and directory names during encryption.[1] |
|
Enterprise | T1222 | .001 | File and Directory Permissions Modification: Windows File and Directory Permissions Modification |
BitPaymer can use |
Enterprise | T1564 | .004 | Hide Artifacts: NTFS File Attributes |
BitPaymer has copied itself to the |
Enterprise | T1070 | .006 | Indicator Removal on Host: Timestomp |
BitPaymer can modify the timestamp of an executable so that it can be identified and restored by the decryption tool.[1] |
Enterprise | T1490 | Inhibit System Recovery |
BitPaymer attempts to remove the backup shadow files from the host using |
|
Enterprise | T1112 | Modify Registry |
BitPaymer can set values in the Registry to help in execution.[1] |
|
Enterprise | T1106 | Native API |
BitPaymer has used dynamic API resolution to avoid identifiable strings within the binary, including |
|
Enterprise | T1135 | Network Share Discovery |
BitPaymer can search for network shares on the domain or workgroup using |
|
Enterprise | T1027 | Obfuscated Files or Information |
BitPaymer has used RC4-encrypted strings and string hashes to avoid identifiable strings within the binary.[1] |
|
Enterprise | T1012 | Query Registry |
BitPaymer can use the RegEnumKeyW to iterate through Registry keys.[1] |
|
Enterprise | T1018 | Remote System Discovery | ||
Enterprise | T1007 | System Service Discovery |
BitPaymer can enumerate existing Windows services on the host that are configured to run as LocalSystem.[1] |
ID | Name | References |
---|---|---|
G0119 | Indrik Spider |