Oxygen Forensics Introduces New Method Of Decrypting WhatsApp Data

Oxygen Forensics, a worldwide developer and provider of advanced forensic data examination tools for mobile devices, cloud services, and drones, announced today that Oxygen Forensic® Detective 10.2 can now acquire a WhatApp Cloud token from Android devices.Two months ago, Oxygen Forensics announced Oxygen Forensic Detective 10.1 that featured the ability to help decrypt WhatsApp iCloud or Google backups with a token. If a key file that is required for backup decryption cannot be obtained, Oxygen Forensic Detective can create a WhatsApp authentication token and use it to decrypt backups stored within the iCloud and Google Cloud services.

Now, with Oxygen Forensic Detective 10.2, investigators can use a WhatApp Cloud token from an Android device to decrypt WhatsApp backups from Android devices, WhatsApp Google Drive, as well as iCloud backups associated with the same phone number.

“Our product development team is constantly working on new features every single day,” said Lee Reiber, COO, Oxygen Forensics. “The new WhatsApp decryption method leaves no digital trace and is a good alternative to the commonly used method with the key file. With this token, forensics experts can also acquire undelivered messages and unanswered calls directly from the WhatsApp Server which can also help the investigators put the pieces together to solve crimes.”

About Oxygen Forensics, Inc.
Oxygen Forensics was founded in 2000 as a PC-to-Mobile Communication software company. This experience has allowed the team of mobile device experts to become unmatched in understanding mobile device communication protocols. With this knowledge, the company has built innovative techniques into Oxygen Forensic® Detective allowing examiners to access much more critical information than competing forensic analysis tools. Oxygen Forensics delivers the most advanced forensic data examination tools for mobile devices, cloud services, and drones covering the widest range of mobile devices running iOS, Android, Windows Phone, BlackBerry and many others. For more information about Oxygen Forensics, please visit www.oxygen-forensic.com.

Get The Latest DFIR News!

Top DFIR articles in your inbox every month.


Unsubscribe any time. We respect your privacy - read our privacy policy.

Leave a Comment

Latest Videos

Quantifying Data Volatility for IoT Forensics With Examples From Contiki OS

Forensic Focus 22nd June 2022 5:00 am

File timestamps are used by forensics practitioners as a fundamental artifact. For example, the creation of user files can show traces of user activity, while system files, like configuration and log files, typically reveal when a program was run. 

Despite timestamps being ubiquitous, the understanding of their exact meaning is mostly overlooked in favor of fully-automated, correlation-based approaches. Existing work for practitioners aims at understanding Windows and is not directly applicable to Unix-like systems. 

In this paper, we review how each layer of the software stack (kernel, file system, libraries, application) influences MACB timestamps on Unix systems such as Linux, OpenBSD, FreeBSD and macOS.

We examine how POSIX specifies the timestamp behavior and propose a framework for automatically profiling OS kernels, user mode libraries and applications, including compliance checks against POSIX.

Our implementation covers four different operating systems, the GIO and Qt library, as well as several user mode applications and is released as open-source.

Based on 187 compliance tests and automated profiling covering common file operations, we found multiple unexpected and non-compliant behaviors, both on common operations and in edge cases.

Furthermore, we provide tables summarizing timestamp behavior aimed to be used by practitioners as a quick-reference.

Learn more: https://dfrws.org/presentation/a-systematic-approach-to-understanding-macb-timestamps-on-unixlike-systems/

File timestamps are used by forensics practitioners as a fundamental artifact. For example, the creation of user files can show traces of user activity, while system files, like configuration and log files, typically reveal when a program was run.

Despite timestamps being ubiquitous, the understanding of their exact meaning is mostly overlooked in favor of fully-automated, correlation-based approaches. Existing work for practitioners aims at understanding Windows and is not directly applicable to Unix-like systems.

In this paper, we review how each layer of the software stack (kernel, file system, libraries, application) influences MACB timestamps on Unix systems such as Linux, OpenBSD, FreeBSD and macOS.

We examine how POSIX specifies the timestamp behavior and propose a framework for automatically profiling OS kernels, user mode libraries and applications, including compliance checks against POSIX.

Our implementation covers four different operating systems, the GIO and Qt library, as well as several user mode applications and is released as open-source.

Based on 187 compliance tests and automated profiling covering common file operations, we found multiple unexpected and non-compliant behaviors, both on common operations and in edge cases.

Furthermore, we provide tables summarizing timestamp behavior aimed to be used by practitioners as a quick-reference.

Learn more: https://dfrws.org/presentation/a-systematic-approach-to-understanding-macb-timestamps-on-unixlike-systems/

YouTube Video UCQajlJPesqmyWJDN52AZI4Q_i0zd7HtluzY

A Systematic Approach to Understanding MACB Timestamps on Unixlike Systems

Forensic Focus 21st June 2022 5:00 am

This error message is only visible to WordPress admins

Important: No API Key Entered.

Many features are not available without adding an API Key. Please go to the YouTube Feed settings page to add an API key after following these instructions.

Latest Articles

Share to...