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

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.

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.

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.

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.

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

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.

After Louis Litt from Suits, Kate Wyler from The Diplomat might be the most annoying character I’ve ever watched.

In Windows forensics(NTFS), you delete one file or folder and end up finding two corresponding artifacts in the Recycle Bin. One containing metadata and the other representing the original content. It’s details like these that make computer forensics difficult to master and push some people to explore other areas of cybersecurity.

"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.

In computer forensics, every startup entry is a potential suspect worth investigating during malware analysis. Not every entry is malicious but any one of them could reveal a persistence mechanism.

You are RIGHT. DFIR starts as an exciting journey. You investigate, uncover what happened and feel like a detective in a true-crime series. Then reality sets in. You repeat investigations. Come up empty. Find artifacts that don’t support your hypothesis and fail to find the ones you hoped would. And through it all, you must remain unbiased. You spend hours troubleshooting, researching and learning new tools and techniques just to keep up. One case can consume so much time that you start questioning whether you chose the right field. And continuous learning? You never stop. New challenges emerge and existing solutions don’t always work. Digital forensics is exciting but it will test your patience, discipline and curiosity in ways you never expected

This game is about humiliating Donnarumma.. it’s not about ManCity

This is brilliant😂

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 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.

There’s a reason tools like Graykey and Cellebrite Premium exist. They cost enormous sums and are typically used by law enforcement. Bypassing a modern iPhone depends on its hardware, iOS version, patch level and security configuration. Even specialized tools have limitations. Yes, it’s possible, but with the latest hardware, updated iOS and security features enabled, it’s nowhere near as easy as he’s making it sound. An unpatched vulnerability can provide an entry point. Zero-click exploits are another route, but developing them is exceptionally difficult. They exploit flaws without requiring the target to click anything, sometimes even flaws the vendor doesn’t know exist. For context, top tier zero-click exploit chains have attracted multimillion dollar bounties, sometimes reaching $2M–$7M. This isn’t casual work.

Before I shout Eii…Let’s ask which iPhone hardware and iOS versions he’s referring to. Maybe his experience is with an iPhone 6s running iOS 14. Modern iPhones use hardware-backed security alongside software encryption, making access significantly more challenging. It’s not impossible, but it’s certainly not the walk in the park he’s making it sound like.

Sack Carrick now!!! Sack him.

We need Rashford on that left flank