Julian Derry retweeted
That’s my Digital Forensics trainee right there doing exploits⚡️.
Go for Gold.
@mrphilghana is NEXT👌🏽
Julian Derry retweeted
WHO'S STILL believing that GOD can flip your entire situation in ONE nightttttttt???
Julian Derry retweeted
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.
Julian Derry retweeted
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.
Check this out uibeawuchi.com
Julian Derry retweeted
Using Windows Task Manager, I acquired the Chromium-based browser's process memory and performed hexadecimal and string analysis with WinHex, identifying credential artifacts within the captured memory space.
The experiment demonstrates how sensitive authentication data may persist in volatile memory, depending on browser memory allocation, application behavior, and acquisition timing. Memory indeed sits above disk.
Key takeaway: TLS encrypts credentials in transit, but it does not eliminate potential plaintext exposure within endpoint memory.
I captured 32 GB of RAM from my Windows system with Belkasoft RAM Capturer. Then I ran WinHex’s File Recovery by Type on the image. The output was multiple file types, each sorted into its own folder.
The JPEG folder ran past 004000 files. Three of those faces belong to people I follow on X. @Josephnartey_
@ireteeh @samgeorgegh. I have never interacted with them. WinHex also returned a search hit for X at offset 1ED6721F. A trace of the platform sat in memory next to the images.
This is the order of volatility in practice. 𝗥𝗙𝗖 𝟯𝟮𝟮𝟳 tells investigators to collect the most volatile evidence first. Memory sits above disk. RAM holds image data, file fragments, running processes and network connections.
A shutdown erases all of it. My rule on every live system, acquire memory, then image the disk, then power down. Skip step one and you cannot get it back.
Julian Derry retweeted
Not to sound delusional, but please pray for grace. Life isn't really about hard work. It's more about alignment, meeting the right people, grace, mercy, and favour.
Julian Derry retweeted
Imagine someone accessing your account without knowing your password.
That's possible with a stolen session cookie.
Cookies aren't malicious. They help websites remember you and keep you logged in.
But in the wrong hands, a valid session cookie can become an access key.
Julian Derry retweeted
The game engine is using actual geographical map data. So when you see Accra, you’re looking at the real Accra, not a fictional city. You can walk around, explore the city, and even fly over it. The character is a bit off 😂 ive been working on this engine for only 18 hours. Give me time
Julian Derry retweeted
Sometimes the best solution to a problem is to close your laptop and go to sleep.
You can struggle with something for hours, wake up the next morning, and solve it in five minutes.
Your brain really needed that break.
Replying to @CyberSamuraiDev
"Came up empty" is a result too, and it belongs in the report: what was searched, with which tool and version, over what data. And "not found" isn't the same as "never existed", so the report should say that too.
Julian Derry retweeted
1/8 This is a legitimate question. And I don't think that we do our faith any favours, when we dismiss questions like these with religious clichés. As a Christian, I've come to accept that the human mind cannot fully comprehend the operations of God. But let's go further.
I’m confused small
“If our God we serve sees and knows everything! I’m sure he sees when we go through very tough times right? He has us at heart too right? So why must we fast and pray to Him that sees and knows everything before our problems can be solved?”
I mean he sees it all, and knows deep in our hearts what we need right? Why doesn’t he just do it but demand we pray to him first before he gives us a solution?
Julian Derry retweeted
Replying to @RevErskineGH
I think your argument starts with a wrong assumption. You’re assuming that because God knows about a problem and has the power to solve it, He must solve it immediately. Knowing something, having the ability to change it and choosing when or whether to intervene are 3 different things. You’re also assuming prayer is a requirement God imposes before helping us. Who says God never helps people who don’t pray? If God is all-knowing, then logically, prayer cannot be about giving Him information He doesn’t already have.
Julian Derry retweeted
If it never reaches the person who has to act, it does not matter.
A briefing is not the win. A platform nobody can field is just a better brief.
Julian Derry retweeted
Networking opened doors. It didn’t close the deal. That took reps, follow-through, and getting comfortable being evaluated.
#veteran #militarytransition #networking
Julian Derry retweeted
Today in HIVE Consult’s Pentest and DFIR Lab, Instructor @elormkdaniel demonstrated how our forensic box can be used during a mobile device investigation. The BlockBox helps isolate a phone or laptop from cellular, Wi‑Fi and Bluetooth signals while investigators handle it. This reduces the risk of incoming messages, remote commands or a remote wipe changing potential evidence. Elorm’s demonstration shows why protecting a device’s state is an essential first step in a mobile investigation.
Follow our LinkedIn page: linkedin.com/company/hivesec…
Thank you💚
Julian Derry retweeted
Replying to @CyberSamuraiDev
I've watched people treat extension mismatch like the finish line. It's usually just the first flag. The burnout piece is real though. A thousand files and every one wants another look.




















