Julian Derry (@CyberSamuraiDev) header
Julian Derry (@CyberSamuraiDev) profile picture

Digital Forensics Analyst & Examiner Computer & Mobile forensics investigations

SHA-512
Joined April 2015
Photo by Julian Derry (@CyberSamuraiDev)Photo by Julian Derry (@CyberSamuraiDev)Photo by Julian Derry (@CyberSamuraiDev)Photo by Julian Derry (@CyberSamuraiDev)Photo by Julian Derry (@CyberSamuraiDev)Photo by Julian Derry (@CyberSamuraiDev)Photo by Julian Derry (@CyberSamuraiDev)Photo by Julian Derry (@CyberSamuraiDev)Photo by Julian Derry (@CyberSamuraiDev)Photo by Julian Derry (@CyberSamuraiDev)
A Deep Dive into Mobile Forensics I recently completed a full mobile forensic analysis on an iPhone 13 Pro and it was a powerful reminder of how much a device actually remembers. This was an advanced logical extraction with verified image integrity. Even without diving into content, the metadata alone told a story. From location artifacts, I reconstructed where the device had been, the routes it traveled and the exact timestamps tied to those movements. But more importantly, I could see how those locations were generated. Some coordinates were tied to ride activity such as uber and bolt. Others came from navigation searches. Some were linked to shared live locations inside messaging apps. Each source leaves a different footprint. A searched address tells a different story than an active trip. A shared live location suggests intentional disclosure. The coordinates are only part of it, the behavior behind them is the real evidence. The “most visited locations” view made patterns obvious. Certain coordinates appeared repeatedly, building a clear picture of routine and frequency over time. On the communication side, interaction volume alone highlighted the primary contacts. Without even reading conversations, it was immediately clear who the highest frequency messaging relationships were. Volume builds pattern. Pattern builds context. Call analysis went just as deep. Even when call entries were deleted, I could still determine whether interactions were audio or video, which platform they occurred on, how long they lasted, and whether they were answered, missed or rejected. Deleting a visible log doesn’t erase the underlying artifacts. I was also able to recover delivered media, expired content, deleted messages and metadata tying everything to specific timestamps and user actions. Here’s what stands out. Phones don’t just store content. They store behavior. They store routine. They store intent. Files can be deleted. Logs can be cleared. But the artifacts remain. #digitalforensics #DFI #mobileforensics #cybersecurity
63
294
18
1,522
136,804
That’s my Digital Forensics trainee right there doing exploits⚡️. Go for Gold. @mrphilghana is NEXT👌🏽
I passed the CHFI exam. It is a badge. The system asks for badges, so I collect them. The work came first. RAM analysis, hex editor carving, rebuilt timelines, public cases on GitHub.
3
7
37
1,759
I passed the CHFI exam. It is a badge. The system asks for badges, so I collect them. The work came first. RAM analysis, hex editor carving, rebuilt timelines, public cases on GitHub.
17
11
4
62
2,363
Julian Derry retweeted
God, I’m thanking you before it even happens.
20
1,784
39
5,481
79,276
God with the 90+7 assist
404
When you miss a call from a friend, call them back. Especially when it comes out of nowhere and even more so when they’ve tried reaching you more than once. You never know what someone is going through behind closed doors. That unexpected call might be their way of reaching out, looking for someone to talk to or simply needing a little reassurance that they’re not alone. You could be the escape they need, the strength they’re looking for or the comfort that gets them through a difficult moment. People are silently battling pain we know nothing about. Men, especially, check on your male friends. Ask how they’re really doing. And when they call, call them back. Sometimes, being there for someone is all it takes.
1
1
7
557
Julian Derry retweeted
Please congratulate me. I'm falling in love with the Word of God, the presence of God and everything that draws me closer to Jesus. 🥹❤️
219
690
25
13,704
136,847
I taught the new HIVE Consult Digital Forensics cohort how to trace USB activity on Windows. We connected two physical drives live and examined what each one left behind, using the command line, Registry Editor and Registry Explorer. We worked from USBSTOR, MountedDevices and the SetupAPI log. From them, we pulled serial numbers, manufacturer details, drive letters and connection history, including first install, last connection and last removal timestamps. We then ran a corporate scenario. Does the drive recovered from an employee match the device used on a specific workstation? No single registry entry answers that. Correlating independent artifacts does. Trainees asked why a removal timestamp does not update right away when you load a live system hive into Registry Explorer and whether to install tools on a suspect machine. I covered transaction logs, evidence integrity and safer acquisition. The key lesson was "do not alter the system you are examining". USB artifacts show a device was connected. They do not show what was copied. A defensible conclusion comes from correlation.
1
5
17
870
Julian Derry retweeted
WHO'S STILL believing that GOD can flip your entire situation in ONE nightttttttt???
126
974
97
10,511
153,034
A suspicious file appears on Windows. What should you check? Sysmon Event ID 11 → File created Image → Process responsible TargetFilename → File location UtcTime → When it happened File creation doesn't prove execution. Check process activity before concluding.
1
2
12
529
Not only that, I explained to them what "Has Ads" and "Is Ads" fields mean in terms of ALTERNATE DATA STREAMS when the $MFT is parsed.. what a session we had.
I trained a new cohort of digital forensics analysts at HIVE Consult on NTFS $MFT analysis. We extracted the $MFT with KAPE, parsed it with Eric Zimmerman's tools, and read raw records in a hex editor. We covered NTFS attributes and why special system files stay hidden in Windows. Then we created, copied and renamed files and changed their timestamps. We traced every action in the $MFT and USN Journal using NTFS Log Tracker, Timeline Explorer and cross-checked the results in Excel.
418
The part that got the trainees very excited was the part about time stomping and how they could tell by comparing the values in the SI<FN fields as well as the uSecZeros.
I trained a new cohort of digital forensics analysts at HIVE Consult on NTFS $MFT analysis. We extracted the $MFT with KAPE, parsed it with Eric Zimmerman's tools, and read raw records in a hex editor. We covered NTFS attributes and why special system files stay hidden in Windows. Then we created, copied and renamed files and changed their timestamps. We traced every action in the $MFT and USN Journal using NTFS Log Tracker, Timeline Explorer and cross-checked the results in Excel.
2
9
919
Love seeing this, Julian. Practical learning and knowledge sharing at its best. Wishing the new cohort every success!
I trained a new cohort of digital forensics analysts at HIVE Consult on NTFS $MFT analysis. We extracted the $MFT with KAPE, parsed it with Eric Zimmerman's tools, and read raw records in a hex editor. We covered NTFS attributes and why special system files stay hidden in Windows. Then we created, copied and renamed files and changed their timestamps. We traced every action in the $MFT and USN Journal using NTFS Log Tracker, Timeline Explorer and cross-checked the results in Excel.
2
4
11
659
I trained a new cohort of digital forensics analysts at HIVE Consult on NTFS $MFT analysis. We extracted the $MFT with KAPE, parsed it with Eric Zimmerman's tools, and read raw records in a hex editor. We covered NTFS attributes and why special system files stay hidden in Windows. Then we created, copied and renamed files and changed their timestamps. We traced every action in the $MFT and USN Journal using NTFS Log Tracker, Timeline Explorer and cross-checked the results in Excel.
1
6
4
47
6,330
Still working on that. It’s masquerading itself in a folder that mimics 𝙋𝙧𝙤𝙜𝙧𝙖𝙢𝘿𝙖𝙩𝙖\𝙈𝙞𝙘𝙧𝙤𝙨𝙤𝙛𝙩\𝙒𝙞𝙣𝙙𝙤𝙬𝙨\𝘿𝙚𝙛𝙚𝙣𝙙𝙚𝙧 path called 𝙒𝙞𝙣𝙙𝙤𝙬𝙨𝙎𝙚𝙘𝙪𝙧𝙞𝙩𝙮 in ProgramData, which isn’t a default path. I’ll post a full report when I’m through.
Replying to @CyberSamuraiDev
What malware is that?
1
3
639
Hunting a chain malware tonight on Windows 11
1
3
15
1,027
Santa sharing gifts early this year 🔥
1/ EZ Tools 2026.10 is out, all on .NET 10 (LTS) ✅ More accurate: 331K more event log records, hive logs replayed as Windows does, every test hive loads ⚡ Faster: up to 9x; EvtxECmd and Registry 2x 📉 Less memory: up to 82% less Update with Get-ZimmermanTools 🧵 #DFIR
3
502