IT博客汇
  • 首页
  • 精华
  • 技术
  • 设计
  • 资讯
  • 扯淡
  • 权利声明
  • 登录 注册

    .pzpq扩展名勒索恢复

    惜分飞发表于 2025-01-13 14:32:03
    love 0

    联系:手机/微信(+86 17813235971) QQ(107644445)QQ咨询惜分飞

    标题:.pzpq扩展名勒索恢复

    作者:惜分飞©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]

    有一个10g的库,数据库被勒索病毒加密扩展名为:.email=[biobiorans@gmail.com]id=[f5657ac3dc58dc8c].biobio.[backups@airmail.cc].pzpq
    pzpq


    #Read-for-recovery.txt文件中内容

    Email 1: 
    backups@airmail.cc
    
    Email 2: 
    hero77@cock.li
    
    Send messages to both emails at the same time 
    
    So send messages to our emails, check your spam folder every few hours 
    
    ID: E3DxxxxxxxxxxxxxxxDBB73
    
    If you do not receive a response from us after 24 hours, create a valid email, for example, gmail,outlook 
    Then send us a message with a new email
    

    通过底层对数据库block进行分析,确认损坏的block情况为,头部损坏16个block,中间16个block,尾部16个block
    QQ20250113-214706


    通过Oracle数据文件勒索加密恢复工具,实现快速恢复
    QQ20250113-220625

    然后尝试打开数据库报ORA-600 4193错误

    un Jan 12 22:35:09 2025
    ALTER DATABASE OPEN
    Sun Jan 12 22:35:10 2025
    Thread 1 opened at log sequence 4
      Current log# 3 seq# 4 mem# 0: D:\ORCL\REDO03.LOG
    Successful open of redo thread 1
    Sun Jan 12 22:35:10 2025
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Sun Jan 12 22:35:10 2025
    SMON: enabling cache recovery
    Sun Jan 12 22:35:10 2025
    Errors in file d:\oracle\product\10.2.0.3\admin\orcl\udump\norcl_ora_2796.trc:
    ORA-00600: internal error code, arguments: [4193], [58], [52], [], [], [], [], []
    
    Sun Jan 12 22:35:11 2025
    Doing block recovery for file 1 block 404
    Block recovery from logseq 4, block 73424 to scn 137439548723
    Sun Jan 12 22:35:11 2025
    Recovery of Online Redo Log: Thread 1 Group 3 Seq 4 Reading mem 0
      Mem# 0: D:\ORCL\REDO03.LOG
    Block recovery stopped at EOT rba 4.73426.16
    Block recovery completed at rba 4.73426.16, scn 32.595250
    Doing block recovery for file 1 block 9
    Block recovery from logseq 4, block 73424 to scn 137439548721
    Sun Jan 12 22:35:11 2025
    Recovery of Online Redo Log: Thread 1 Group 3 Seq 4 Reading mem 0
      Mem# 0: D:\ORCL\REDO03.LOG
    Block recovery completed at rba 4.73426.16, scn 32.595250
    Sun Jan 12 22:35:11 2025
    Errors in file d:\oracle\product\10.2.0.3\admin\orcl\udump\norcl_ora_2796.trc:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-00607: Internal error occurred while making a change to a data block
    ORA-00600: internal error code, arguments: [4193], [58], [52], [], [], [], [], []
    
    Error 604 happened during db open, shutting down database
    USER: terminating instance due to error 604
    Sun Jan 12 22:35:11 2025
    Errors in file d:\oracle\product\10.2.0.3\admin\orcl\bdump\norcl_pmon_2168.trc:
    ORA-00604: error occurred at recursive SQL level 
    
    Sun Jan 12 22:35:12 2025
    Errors in file d:\oracle\product\10.2.0.3\admin\orcl\bdump\norcl_reco_2688.trc:
    ORA-00604: error occurred at recursive SQL level 
    
    Sun Jan 12 22:35:12 2025
    Errors in file d:\oracle\product\10.2.0.3\admin\orcl\bdump\norcl_smon_2332.trc:
    ORA-00604: error occurred at recursive SQL level 
    
    Sun Jan 12 22:35:12 2025
    Errors in file d:\oracle\product\10.2.0.3\admin\orcl\bdump\norcl_ckpt_2600.trc:
    ORA-00604: error occurred at recursive SQL level 
    
    Sun Jan 12 22:35:12 2025
    Errors in file d:\oracle\product\10.2.0.3\admin\orcl\bdump\norcl_lgwr_2672.trc:
    ORA-00604: error occurred at recursive SQL level 
    
    Sun Jan 12 22:35:12 2025
    Errors in file d:\oracle\product\10.2.0.3\admin\orcl\bdump\norcl_dbw0_1344.trc:
    ORA-00604: error occurred at recursive SQL level 
    
    Sun Jan 12 22:35:12 2025
    Errors in file d:\oracle\product\10.2.0.3\admin\orcl\bdump\norcl_mman_2828.trc:
    ORA-00604: error occurred at recursive SQL level 
    
    Sun Jan 12 22:35:12 2025
    Errors in file d:\oracle\product\10.2.0.3\admin\orcl\bdump\norcl_psp0_2324.trc:
    ORA-00604: error occurred at recursive SQL level 
    
    Instance terminated by USER, pid = 2796
    ORA-1092 signalled during: ALTER DATABASE OPEN...
    

    通过分析trace,确认是系统回滚段的free block pool异常,使用bbed进行修复

    BBED> clean free_block_pool
    Clean free block pool completed.you can use dump to verify the data, then can us
    e sum apply command to save data.
    BBED> sum apply
    
    Warning: apply the modified data will overwrite original data.
    Would you like to continue? (y/n)
    y
    
    Old checksum value: 0xf2c0
    New checksum value: 0xf315
    Writing block has completed
    
    BBED>
    

    open数据库成功,然后安排导出数据即可
    QQ20250113-222649


    对于类似这种被加密的勒索的数据文件,我们可以实现比较好的恢复效果,如果此类的数据库(oracle,mysql,sql server)等被加密,需要专业恢复技术支持,请联系我们:
    电话/微信:17813235971    Q Q:107644445QQ咨询惜分飞    E-Mail:dba@xifenfei.com
    系统安全防护措施建议:
    1.多台机器,不要使用相同的账号和口令
    2.登录口令要有足够的长度和复杂性,并定期更换登录口令
    3.重要资料的共享文件夹应设置访问权限控制,并进行定期备份
    4.定期检测系统和软件中的安全漏洞,及时打上补丁。
    5.定期到服务器检查是否存在异常。
    6.安装安全防护软件,并确保其正常运行。
    7.从正规渠道下载安装软件。
    8.对不熟悉的软件,如果已经被杀毒软件拦截查杀,不要添加信任继续运行。
    9.保存良好的备份习惯,尽量做到每日备份,异地备份。

    • 记录一次ORA-00600[kdxlin:psno out of range]/ORA-00600[3020]/ORA-00600[4000]/ORA-00600[4193]的数据库恢复
    • undo异常总结和恢复思路
    • ORA-12514: TNS: 监听进程不能解析在连接描述符中给出的SERVICE_NAME
    • win强制修改盘符导致oracle异常恢复
    • 数据库启动ORA-08103故障恢复
    • ORA-00600: internal error code, arguments: [6006], [1], [], [], [], [], [], []
    • 第一例Oracle 21c恢复咨询
    • ORA-600[4194]/[4193]解决
    • 记录一次ORA-00316 ORA-00312 redo异常恢复
    • 某集团ebs数据库redo undo丢失导致悲剧
    • 记录一次ORA-600 3004 恢复过程和处理思路
    • ORA-00470: LGWR process terminated with error


沪ICP备19023445号-2号
友情链接