CoffinLocker勒索软件家族详情
【家族名】Win32/Ransom.CoffinLocker
[平台] / [主类型].[家族名]
平台类型 :Win32 Win64
威胁类型 : Ransom
【是否支持解密】
360解密大师：暂不支持
在线解密：暂不支持
【被加密文件】
被加密文件后缀格式：.coffin
修改文件后缀为
【勒索提示信息】：
文件名：how_to_recover.coffin.txt
文件内容
---------------------------------------------------------------------------------------------------------------------------
================================================================================
#### ########## ###### ##### # # #### ##### # ######
# # # # # # # ## # # # # # # # ##
# # # ########### # ## # # # # #### #####
# # # # # # # ## # # # # # # ## #
#### ##### # # # ## ###### #### ##### #######
================================================================================
YOUR FILES ARE IN THE COFFIN
================================================================================
Discovered on : 2026-10-20 15:41:01
Deadline : 2026-10-27 15:41:01(7 days)
Ransom : 0.075 BTC(~\$4,900 USD)
--------------------------------------------------------------------------------
WHAT HAPPENED
--------------------------------------------------------------------------------
Every document, database, spreadsheet, source file, archive, and image
on this machine and on every mapped network share has been encrypted.
Each file has been sealed inside its own coffin with a unique key.
Decrypting one file tells you NOTHING about the others.
Original file sectors were then overwritten with random data. Undelete
tools will only find garbage. Volume Shadow Copies, the Windows Backup
Catalog, System Restore points, and your Recycle Bin were all destroyed.
So "just restore from a previous version" will NOT save you.
--------------------------------------------------------------------------------
THE CIPHER STACK (why you cannot break it)
--------------------------------------------------------------------------------
Content layer : AES-256-GCM (hardware accelerated, per-file key)
Header layer : ChaCha20-Poly1305 (per-file key)
Session keys : X25519 Curve25519 ECC (fresh per file)
Key wrapping : RSA-4096-OAEP (master keypair)
Nonces : counter-XORed per 1 MB chunk
Header spoof : files start with PK\x03\x04 (look like ZIPs)
--------------------------------------------------------------------------------
WHAT YOU WILL SEE
--------------------------------------------------------------------------------
* Every encrypted file now ends in:.coffin
* A copy of this note sits in every directory.
* Your desktop wallpaper has been replaced.
* The file "coffin_keys\master_rsa_private.pem" is the ONLY key
that can unwrap your files. Back it up before you touch anything.
* A scheduled task "CoffinLocker" and a Run key keep this alive.
--------------------------------------------------------------------------------
HOW TO RECOVER YOUR FILES
--------------------------------------------------------------------------------
You have TWO options. Read both before you pay.
OPTION A — PAY THE RANSOM (recommended)
---------------------------------------
1. Send exactly 0.075 BTC to this Bitcoin address:
bc1qcoffin7x9k2m4p8v3n6w1z5r0t9y2u4i8o6a3d
2. Email your BTC transaction ID (txid) AND the machine name to:
coffin.locker@onionmail.org
Subject line: COFFIN <your-machine-name>
You can reach this address from any normal email provider.
OnionMail also works over Tor if you prefer.
3. Within 24-48 hours you will receive the decryption key file
(coffin_keys_paid.zip). Drop it next to CoffinLocker.exe and run:
CoffinLocker.exe unlock
Every .coffin file is restored to its original name and content.
OPTION B — DIY DECRYPT (if you have the master private key already)
------------------------------------------------------------------
Copy master_rsa_private.pem into a coffin_keys\ folder next to
CoffinLocker.exe, then run:
CoffinLocker.exe unlock --root "C:\Users\You\Documents"
This works WITHOUT paying IF you kept the private key from the
original run. Most victims do not, which is why you pay.
--------------------------------------------------------------------------------
PAYMENT DETAILS
--------------------------------------------------------------------------------
Amount : 0.075 BTC
USD approx: ~\$4,900 USD
Address : bc1qcoffin7x9k2m4p8v3n6w1z5r0t9y2u4i8o6a3d
Network : Bitcoin mainnet (native segwit bc1q...)
Deadline: 2026-10-27 15:41:01
Contact : coffin.locker@onionmail.org
AFTER THE DEADLINE the price doubles. No exceptions.
Partial payments are accepted but slow you down.
--------------------------------------------------------------------------------
FAQ
--------------------------------------------------------------------------------
Q: Can I just rename .coffin files back?
A: No. The bytes are transformed. Renaming does nothing.
Q: What if I reboot?
A: Fine. Nothing is lost. The task re-runs and finishes any stragglers.
Q: What about my network drives?
A: Already sealed. Same recovery process.
Q: What if I pay late?
A: Price doubles. Key still works.
Q: How do I know you will actually send the key?
A: You do not. That is the game. But the math is real.
--------------------------------------------------------------------------------
TECHNICAL APPENDIX (for the curious)
--------------------------------------------------------------------------------
Coffin format v1.1:
magicPK\x03\x04
header nonce
header salt
content nonce
content salt
session public key (X25519, cleartext)
header ciphertext length
header ciphertext (ChaCha20-Poly1305)
chunk length-> chunk ciphertext (AES-256-GCM)
...repeated ...
0x00000000 terminator
Header key= HKDF-SHA256(session_pub, header_salt, "coffin-header-v1")
Content key = HKDF-SHA256(X25519(shared), content_salt, "coffin-content-v1")
Session key = RSA-4096-OAEP-wrapped inside the header ciphertext.
Nothing here is proprietary. It is just done correctly.
================================================================================
STAY CALM.READ THIS.PAY.RECOVER.
================================================================================
---------------------------------------------------------------------------------------------------------------------------
【修改桌面显示】：
【防护建议】
1.多台机器，不要使用相同的账号和口令
2.登录口令要有足够的长度和复杂性，并定期更换登录口令
3.重要资料的共享文件夹应设置访问权限控制，并进行定期备份
4.定期检测系统和软件中的安全漏洞，及时打上补丁。
5.定期到服务器检查是否存在异常。查看范围包括：
a)是否有新增账户
b) Guest是否被启用
c) Windows系统日志是否存在异常
d)杀毒软件是否存在异常拦截情况
6.安装安全防护软件，并确保其正常运行。
7.从正规渠道下载安装软件。
8.对不熟悉的软件，如果已经被杀毒软件拦截查杀，不要添加信任继续运行。
页:
[1]