r/computerforensics • u/[deleted] • Oct 27 '25
Love this book
Almost half way through and it’s so good! Been learning a lot.
r/computerforensics • u/[deleted] • Oct 27 '25
Almost half way through and it’s so good! Been learning a lot.
r/computerforensics • u/[deleted] • Aug 05 '25
r/computerforensics • u/MrPoBot • Feb 21 '21
r/computerforensics • u/secnigma • May 08 '22
Prettier version of this post is available here.
The first problem anyone’s with a damaged disc going to encounter, is that they cannot copy files from it using a regular copying mechanism (eg:. file explorer, terminal commands).
This is due to the fact that, normal file copying mechanisms will not attempt to read from a bad sector or unreadable data. Instead, they will freeze, or throw an error upon encountering such data.
To recover data from a damaged medium, we need specialized tools that are aware of this problem and will continue with the reading process, even after encountering errors.
Three of such tools are ddrescue , dvdisaster and testdisk.
These applications can be used to create an exact image file (or something that resembles it), from a damaged medium.
Ok. I have some good news and some bad news. Let’s get the bad news out of our way first.
Note: Reading from a damaged disc using ddrescue or dvdisaster is going to take a long time. For comparison, from my CD, which has the capacity of 700 MB, there was 400MB of data. And it took around 12 Hours for it to finish reading it!
But the good news is that, the process can be cancelled and resumed at any time!
You can select either dvdisaster, ddrescue or TestDisk to begin the read process.
Once we get an image file, we will carve out the readable data using the photorec utility.
Let’s start the reading process.
I’m going to talk about creating a disk image using the three applications I’ve mentioned. Although the end goal is same, knowing multiple applications to do the same thing can come in handy.
Dvdisaster is a GUI application, so that would be easier to use. It has a nice interface and a cool animation to display progress.
On Debian based distros, we can install it using
sudo apt install dvdisaster -yUsing DVDisaster is easy. Just select the CD / DVD reader, Specify location to save the output file and Click on start Reading. Once the reading is finished, the file will be stored in the specified location.
Sometimes, we would need to manually specify some settings when reading a damaged disc; like the block size, reading direction etc.
If you want such granular control while reading the disc, then you should go with ddrescue. Also the chances of getting succesful data recovery are higher with ddrescue, since we can use it to run multiple times on the same disc with different read options.
On Debian based distros, we can install it using
sudo apt install gddrescue -yWe are going to run ddrescue three times on the disc. First, we are going to to make ddrescue skip the parts with error and we will read the good data.
Then on the second run, we are going to make ddrescue read the entire disc, including the blocks with errors and try to get more data from the disc.
And on the final run, we are going to make ddrescue read the entire disc, but backwards.
This three step recovery process ensures that we are going to get every last bit of readable information from the damaged disc. Read this answer for a detailed explanation.
Note: You can use the info ddrescuecommand anytime to get a great guide on how to use ddrescue.
Read #1 Reading just the Good Data
ddrescue -b 2048 -n -v /dev/cdrom dvd.iso rescue.logThis command specifies the following things
b : Block Size as 2048 (default blocksize of DVD)
n : No scrape ( Skip the bad sectors)
v : Verbose
/dev/cdrom : The path to mounted CD (This will vary on distros)
dvd.iso : Output image to write
rescue.log : Log file
Note: Now this reading process is going to take a looooong time. Either keep your computer running untill it finishes or just cancel and restart the process with the same command later, to resume the reading process.
Read #2 Reading the Bad Data
Once it has been finished, we can run it again with scraping (Reading the bad blocks), with the following command. Please note that we are using the same image file (dvd.iso), we’ve created in the first run and not a different file.
ddrescue -b 2048 -d -r 3 -v /dev/cdrom dvd.iso rescue.logHere, we have two new flags.
d : Read the device directly (Instead of going through kernel)
r : Retry count on error
Now this is going to attempt to read and recover data from bad sectors. Once new data is found, it will be appended to the dvd.iso image we’ve created in the first step.
Let’s continue the waiting game..
Read #3 Reading the Bad Data, But in Reverse
Once that command has finished it’s execution, let’s scrape again, but this time in a reverse order.
ddrescue -b 2048 -d -R -r 3 -v /dev/cdrom dvd.iso rescue.log
* R : Reverse read
After this command finishes execution, we will have an image file with the data recovered by ddrescue.
Edit: Reverse read is not required, as ddrescue automatically does this.
Thanks LinAGKar
Now if we check the file type of the extracted image, we can see that it’s not a proper ISO file. Instead, it’s recognized as a data file.
This means that we have to perform additional carving in the recovered image, to get usable files from it.
Now as the final method for creating a disc image file, I’m going to use Testdisk.
TestDisk is a free and open source tool, that helps users recover lost partitions or repair corrupted filesystems. Testdisk is actually faster in creating disc images, in comaprison to other disc imaging methods.
PhotoRec is a free and open-source tool for data recovery using data carving techniques, designed to recover lost files.
We will first use TestDisk to create a disc image from the CD. Then, we could use PhotoRec on the disc image to carve files from it.
To install TestDisk and Photorec on debian based distros, use
sudo apt install testdisk -yPhotorec is a part of testdisk suite. So, It will be automatically installed along with testdisk.
To use testdisk, simply pass the full path to my CD, as an argument to it. In my case, it is /dev/cdrom.
testdisk /dev/cdromSelect Proceed and press enter when TestDisk prompts to select Media.
Now, choose Continue, when prompted to continue.
Select None when TestDisk asks for partition table type.
Now press Right Arrow to highlight the Image Creation at the bottom and Press Enter.
Select the directory to save the output disk image. If you want to save it to the current working directory, just press “C” to confirm.
Once TestDisk finishes creating the image file, we can choose to perform additional operations on it, or just exit.
Here, I am quitting TestDisk.
Now, we will have an image file named image.dd.
Now, let’s start the carving process.
To start the file carving process, we are going to use the tool photorec. If you’ve installed testdisk, photorec will be automatically installed along with it.
We can now run photorec on any of the disc images we’ve generated earlier to start the carving process.
photorec image.ddPhotorec’s interface is similar to TestDisk's.
Select Proceed and press Enter.
You can now select Search to start the File recovery.
OR you could choose specific file formats to recover from the File Opt menu.
After selecting Search, photorec will prompt you to choose the file system type. Choose Other and press enter.
Now, PhotoRec will ask us to select a location to save the recovered files. Select the location and press “C” to confirm.
Once the process has been finished, we can find the files inside a directory called recup_dir.*
Around 30-40% of the files are recovered fully, others were recovered partially and some files have been split into multiple files.
Though it might not seem like a great number, considering the stage the disc was in, it is indeed a great achievement achieved through pure software trickery!
I’m sure that I could’ve gotten more data, if I’ve spent some time on physically polishing the CD’s surface to reduce the scratches. But, since this was just a hobby project, I’m more than satisfied with the outcome.
r/computerforensics • u/PabloSkywalk • Oct 31 '18
So I came upon this channel : https://www.youtube.com/user/davisrichardg/videos
and his videos are so good and I hate it when I see people who put effort in their videos get small amount of views, it would be a shame if he stopped making videos so make sure you guys check it out.
r/computerforensics • u/Cypher_Blue • May 15 '26
r/computerforensics • u/jamesabels • Jan 21 '20
r/computerforensics • u/hahasorelevant • Mar 24 '20
r/computerforensics • u/SalandaBlanda • Mar 31 '26
Some background: I'm a DFE in the Army. I've done the job roughly 5 years. I've worked in a broad variety of areas and with other technical specializations, so I wanted to build a one-stop shop for myself and others I work with. The site has artifact locations, step actions for tools like X Ways (which desperately needs step actions), and a variety of other things. I have no current plans to monetize as the domain cost me $1. I hope it's helpful for somebody.
r/computerforensics • u/digicat • Jun 16 '19
r/computerforensics • u/4n6expert • Mar 07 '17
Wikileaks have just released a huge collection of data said to have been leaked from the CIA, apparently around the end of 2015.
included in the data dump is documentation for a system called 'Hive' that manages communications between infected systems and the CIA via proxy servers (the 'Blot' proxy software was developed by Xetron, now part of Northrop Grumman - the drone people).
If Hive fails to communicate with 'home base' for a certain period it will automatically delete itself. (That deletion does not appear to be a full anti-forensic deletion, which could be of interest).
But, on *NIX systems, even if the implant deletes itself two files are left behind in /var. They are ".config" and ".log". Date stamps on the log file reveals when the implant was deleted.
If you would like to know if the CIA have been looking around your *NIX systems then these files are good things to look for.
Source: https://wikileaks.org/ciav7p1/cms/files/DevelopersGuide.pdf
r/computerforensics • u/cracka0 • Dec 23 '25
Recent releases of heavily redacted documents (including the Epstein files) raised a technical question for me:under what conditions, if any, could forensic techniques recover information from such shaded areas?. Thinking about it, I remember Interpol fighting to find a pedophile nicknamed Mr. Swirl, who published photos and videos proving his crimes. His face was under the influence of Swirl, which alters the pixel order in images. There are two types of effects: the first changes the pixels themselves, which is difficult to reverse, and the second changes the pixel order in images, which is relatively easy to do using appropriate algorithms. So, my question is: can we modify or discover an algorithm that would allow us to remove the shading in Epstein's files? Thank you.
r/computerforensics • u/cnuttyforehead • Jun 27 '20
r/computerforensics • u/brian_carrier • May 14 '20
Based on overwhelming interest, we're extending the offer 15 more days. 80k+ people have started the course! This is your chance to learn more about Autopsy for free.
https://www.autopsy.com/support/training/covid-19-free-autopsy-training/
r/computerforensics • u/zero-skill-samus • Oct 03 '25
I get cases in from time to time regarding suspicions of a hacked iPhone. Every single time, theres nothing on the device. Instead, its an iCloud issue where someone else has access to their data through another authenticated device.
I wanted to know, is it even feasible for a civilian to establish remote/secret access on a modern iOS device? Has anyone ever seen an iOS device that was actually compromised? Apple already locks down most access and remote functions. GoToAssist can't even allow remote control. I suppose running full file system extractions and giving the client peace of mind is worth it for some.
r/computerforensics • u/MDCDF • Mar 11 '25
r/computerforensics • u/nelsondelmonte • Apr 21 '21
r/computerforensics • u/meirwah • Nov 15 '16
r/computerforensics • u/Majestic_Report_2908 • Mar 18 '26
Hi everyone!
As a beginner student in Cyber IR and Forensics, I’m trying to put in a lot of work at home to learn and gain experience beyond the generic stuff we learn in class. Honestly, we haven't even covered anything related to forensic investigation in my degree yet!
Still, I’ve built this 'Forensics Lab' today to eventually use for DFIR investigations in companies. What do you think?
to keep minimal touch on infected machines, I created a script called Start_Investigation_Script. By running it through CMD as Administrator, I can activate this whole lab...
I’d love to get your feedback, how does it look?
r/computerforensics • u/Desperate-Ad-8456 • Apr 10 '26
Hey everyone,
I don't know about you, but I was getting seriously frustrated with how fragmented our tools are. Trying to piece together an investigation across Windows, Linux, and Mac artifacts usually means jumping between half a dozen different apps, and the centralized "all-in-one" solutions cost some money
So, about 9 months ago, I decided to just try and build the tool I actually wanted to use. It's called Heimdall DFIR. GitHub: https://raiseix.github.io/Heimdall-DFIR
Instead of a bunch of marketing buzzwords, here is what it actually does right now:
One giant timeline: It takes your artifacts (EVTX, MFT, Prefetch and other Windows artifacts Linux/Mac logs, etc.) and merges them into a single chronological grid. I spent a lot of time trying to make the output actually human-readable instead of just dumping raw JSON on the screen
RAM Analysis: I hooked it up to VolWeb (Volatility 3). You can upload massive memory dumps directly in the UI and it actually handles the stream without crashing the backend
Collaborative mode: Investigating alone sucks, so I added a side-chat and an evidence-pinning system so a team can look at the exact same case simultaneously
To be completely transparent with you all: This is very much a Beta. It’s a massive undertaking and it’s still missing a lot of features I want to add before calling it a complete platform
That’s honestly why I’m sharing it today. I’m hoping to get some brutally honest feedback from people who do this daily. What parsers are you constantly missing in open-source tools? What would make you actually want to use this?
If anyone wants to spin it up (Docker compose is ready to go), break it, submit bug reports, or even contribute code to help build this out, I would be incredibly grateful.
Let me know what you think. If you like the vision, a GitHub ⭐ helps a lot!
r/computerforensics • u/Ian_Henry_McDuckins • Jul 31 '21
r/computerforensics • u/[deleted] • Oct 22 '25
Is it possible to make a raspberry pi zero w, into a personal write blocker for when I want to write an image?
r/computerforensics • u/Fake4d • Feb 25 '18