HDD Password Toshiba
Hello,
i have a Toshiba Laptop which HDD i can't image with FTK. Only zeros with Software Writeblocker. With Hardware Writeblocker you don't See the drive. If you boot the system there ist the info: Input HDD password. I think it's a firmware password. Any suggestions? Is there a tool that shows If it is so?
π£Civil_Structure_1033
1\. It may be ATA security at work: simplified, hard disks can be assigned a password, and won't allow access unless that password is used to 'login' to the HDD.
Such HDD will, on request, say that security is enabled, so you can use tools such as hdparm (Linux) to identify. (See https://www.admin-magazine.com/Archive/2014/19/Using-the-ATA-security-features-of-modern-hard-disks-and-SSDs for an introduction.)
In this case, as long as you have the password, you can also 'login' to the HDD (pre-boot or post-boot) before you image the drive. The details will obviously depend on the platform you use.
2\. Write blocking may affect the issue. If the blocker prevents all requests that are not simple reads, it will also block login requests. Professional tools usually won't make that mistake, but I can't identify the tool you mention, so I can't say if that is the case here.
The password may be assigned by Toshiba, and be part of the hardware platform: that is, the HDD cannot be removed from the computer and work normally, unless you also extract the password. In these cases, it is easier to let the drive remain mounted, and make a image from a forensic boot environment.
π€athulin12
π@malwr
Hello,
i have a Toshiba Laptop which HDD i can't image with FTK. Only zeros with Software Writeblocker. With Hardware Writeblocker you don't See the drive. If you boot the system there ist the info: Input HDD password. I think it's a firmware password. Any suggestions? Is there a tool that shows If it is so?
π£Civil_Structure_1033
1\. It may be ATA security at work: simplified, hard disks can be assigned a password, and won't allow access unless that password is used to 'login' to the HDD.
Such HDD will, on request, say that security is enabled, so you can use tools such as hdparm (Linux) to identify. (See https://www.admin-magazine.com/Archive/2014/19/Using-the-ATA-security-features-of-modern-hard-disks-and-SSDs for an introduction.)
In this case, as long as you have the password, you can also 'login' to the HDD (pre-boot or post-boot) before you image the drive. The details will obviously depend on the platform you use.
2\. Write blocking may affect the issue. If the blocker prevents all requests that are not simple reads, it will also block login requests. Professional tools usually won't make that mistake, but I can't identify the tool you mention, so I can't say if that is the case here.
The password may be assigned by Toshiba, and be part of the hardware platform: that is, the HDD cannot be removed from the computer and work normally, unless you also extract the password. In these cases, it is easier to let the drive remain mounted, and make a image from a forensic boot environment.
π€athulin12
π@malwr
Reddit
From the computerforensics community on Reddit
Explore this post and more from the computerforensics community
Dissect enables you to go from acquisition of thousands of systems to answering the how, when, and what in a matter of hours β A game changer for incident response teams. Itβs modular and concise API allows for anyone with Python experience to adapt it to their own needs and create output ..
π£digicat
Big fat kudos to Fox IT for releasing Dissect as open source. Wonderful contribution to the community.
On GitHub: https://github.com/fox-it/dissect
π€mrkoot
π@malwr
π£digicat
Big fat kudos to Fox IT for releasing Dissect as open source. Wonderful contribution to the community.
On GitHub: https://github.com/fox-it/dissect
π€mrkoot
π@malwr
GitHub
GitHub - fox-it/dissect: Dissect is a digital forensics & incident response framework and toolset that allows you to quickly accessβ¦
Dissect is a digital forensics & incident response framework and toolset that allows you to quickly access and analyse forensic artefacts from various disk and file formats, developed by Fo...
Bumblebee: increasing its capacity and evolving its TTPs - Check Point Research
π£digicat
π@malwr
π£digicat
π@malwr
Check Point Research
Bumblebee: increasing its capacity and evolving its TTPs - Check Point Research
Research by: Marc Salinas Fernandez Background & Key Findings The spring of 2022 saw a spike in activity of Bumblebee loader, a recent threat that has garnered a lot of attention due to its many links to several well-known malware families. In this pieceβ¦
Remove All The Callbacks β BlackByte Ransomware Disables EDR Via RTCore64.sys Abuse
π£digicat
π@malwr
π£digicat
π@malwr
Sophos News
Remove All The Callbacks β BlackByte Ransomware Disables EDR Via RTCore64.sys Abuse
A fresh exploration of the malware uncovers a new tactic for bypassing security products by abusing a known driver vulnerability
DeftTorero TTPs in 2019β2021 - aka Lebanese Cedar, Volatile Cedar - this post focuses primarily on the TTPs used by the threat actor in intrusions between late 2019 and mid-2021 to compromise victims.
π£digicat
π@malwr
π£digicat
π@malwr
Securelist
DeftTorero TTPs in 2019β2021
In this report we focus on tactics, techniques, and procedures (TTPs) of the DeftTorero (aka Lebanese Cedar or Volatile Cedar) threat actor, which targets Middle East countries.
Security Researchers shares Lockbit 3.0 ransomware technical details, defense tips on case study.
π£Late_Ice_9288
π@malwr
π£Late_Ice_9288
π@malwr
CIP Blog
LockBit 3.0 Ransomware Case Study: A Huge Cybersecurity Risk | CIP Blog
In this article, we will analyze LockBit 3.0 ransomware attack cases to show you how attacks similar to these cases can be prevented.
What is LockBit 3.0 Ransomware?
LockBit 3.0 (also known as LockBit Black) is ransomware created by the cybercrime syndicateβ¦
What is LockBit 3.0 Ransomware?
LockBit 3.0 (also known as LockBit Black) is ransomware created by the cybercrime syndicateβ¦
API Monitor32 - Detecting Windows API hooking and modification for analysis purposes
π£ytk2128
π@malwr
π£ytk2128
π@malwr
GitHub
GitHub - ytk2128/api-monitor32: A simple tool for detecting memory modifications to Windows API.
A simple tool for detecting memory modifications to Windows API. - ytk2128/api-monitor32
π1
Freeze - a payload toolkit for bypassing EDRs using suspended processes, direct syscalls, and alternative execution methods
π£CyberMasterV
π@malwr
π£CyberMasterV
π@malwr
GitHub
GitHub - optiv/Freeze: Freeze is a payload toolkit for bypassing EDRs using suspended processes, direct syscalls, and alternativeβ¦
Freeze is a payload toolkit for bypassing EDRs using suspended processes, direct syscalls, and alternative execution methods - optiv/Freeze