dfIndexeddb
dfindexeddb is an experimental Python tool for performing digital forensic analysis of IndexedDB and LevelDB files.
It parses LevelDB, IndexedDB and JavaScript structures from these files without requiring native libraries. (Note: only a subset of IndexedDB key types and JavaScript types for Firefox, Safari and Chromium-based browsers are currently supported).
The content of IndexedDB files is dependent on what a web application stores locally/offline using the web browser's IndexedDB API. Examples of content might include:
- text from a text/source-code editor application,
- emails and contact information from an e-mail application,
- images and metadata from a photo gallery application
Installation
- [Linux] Install the snappy compression development package
$ sudo apt install libsnappy-dev
- Create a virtual environment and install the package
$ python3 -m venv .venv
$ source .venv/bin/activate
$ pip install dfindexeddb
To also install the dependencies for leveldb/indexeddb plugins, run
$ pip install 'dfindexeddb[plugins]'
Installation from source
- [Linux] Install the snappy compression development package
$ sudo apt install libsnappy-dev
-
Clone or download/unzip the repository to your local machine.
-
Create a virtual environment and install the package
$ python3 -m venv .venv
$ source .venv/bin/activate
$ pip install .
To also install the dependencies for leveldb/indexeddb plugins, run
$ pip install '.[plugins]'
Usage
Two CLI tools for parsing IndexedDB/LevelDB files are available after installation:
IndexedDB
$ dfindexeddb -h
usage: dfindexeddb [-h] {db,ldb,log} ...
A cli tool for parsing indexeddb files
positional arguments:
{db,ldb,log}
db Parse a directory as indexeddb.
ldb Parse a ldb file as indexeddb.
log Parse a log file as indexeddb.
options:
-h, --help show this help message and exit
Examples:
To parse IndexedDB records from an sqlite file for Firefox and output the results as JSON, use the following command:
dfindexeddb db -s SOURCE --format firefox -o json
To parse IndexedDB records from an sqlite file for Safari and output the results as JSON-L, use the following command:
dfindexeddb db -s SOURCE --format safari -o jsonl
To parse IndexedDB records from a LevelDB folder for Chrome/Chromium, using the manifest file to determine recovered records and output as JSON, use the following command:
dfindexeddb db -s SOURCE --format chrome --use_manifest
To parse IndexedDB records from a LevelDB ldb (.ldb) file and output the results as JSON-L, use the following command:
dfindexeddb ldb -s SOURCE -o jsonl
To parse IndexedDB records from a LevelDB log (.log) file and output the results as the Python printable representation, use the following command:
dfindexeddb log -s SOURCE -o repr
To parse a file as a Chrome/Chromium IndexedDB blink value and output the results as JSON:
dfindexeddb blink -s SOURCE
LevelDB
$ dfleveldb -h
usage: dfleveldb [-h] {db,log,ldb,descriptor} ...
A cli tool for parsing leveldb files
positional arguments:
{db,log,ldb,descriptor}
db Parse a directory as leveldb.
log Parse a leveldb log file.
ldb Parse a leveldb table (.ldb) file.
descriptor Parse a leveldb descriptor (MANIFEST) file.
options:
-h, --help show this help message and exit
Examples
To parse records from a LevelDB folder, use the following command:
dfleveldb db -s SOURCE
To parse records from a LevelDB folder, and use the sequence number to determine recovered records and output as JSON, use the following command:
dfleveldb db -s SOURCE --use_sequence_number
To parse blocks / physical records/ write batches / internal key records from a
LevelDB log (.log) file, use the following command, specifying the type (block,
physical_records, etc) via the -t option. By default, internal key records are parsed:
$ dfleveldb log -s SOURCE [-t {blocks,physical_records,write_batches,parsed_internal_key}]
To parse blocks / records from a LevelDB table (.ldb) file, use the following
command, specifying the type (blocks, records) via the -t option. By
default, records are parsed:
$ dfleveldb ldb -s SOURCE [-t {blocks,records}]
To parse version edit records from a Descriptor (MANIFEST) file, use the following command:
$ dfleveldb descriptor -s SOURCE [-o {json,jsonl,repr}] [-t {blocks,physical_records,versionedit} | -v]
Plugins
To apply a plugin parser for a leveldb file/folder, add the
--plugin [Plugin Name] argument. Currently, there is support for the
following artifacts:
| Plugin Name | Artifact Name |
|---|---|
ChromeNotificationRecord |
Chrome/Chromium Notifications |
Metadata
Release files for dfindexeddb 20241031
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| dfindexeddb-20241031.tar.gz | 64.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dfindexeddb-20241031-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 148.9 kB
Release files / dfindexeddb-20241031.tar.gz
| Download URL | dfindexeddb-20241031.tar.gz |
|---|---|
| Size | 64.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
378f9804a336df4c594cede8fd0aa0a06d09832b69bcba1b5efdb83b7496d265
|
|
BLAKE2b-256 checksum How to use checksums |
519e242868cfea525859517c5219b59266ef930c6b7d9e9d51c53818b61b357c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 31, 2024.
Transparency logRelease files / dfindexeddb-20241031-py3-none-any.whl
| Download URL | dfindexeddb-20241031-py3-none-any.whl |
|---|---|
| Size | 84.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2ecc82149a673a1027b2a0721294bca10a798979a7feb32e3b586c1a3a337390
|
|
BLAKE2b-256 checksum How to use checksums |
bf3672579d95cb3b2325306aad20e45d8bc5c14106b6460fd63d4ba3da348994
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/5.1.1 CPython/3.12.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 31, 2024.
Transparency log