MOSCOW FORENSICS DAY '26MFD '26

Slides / 3 of 9

Talk slides

Using SQLite database journals in the investigation of digital incidents

Alexey Moskvichev · MKO Systems
Day 1 — Thursday, 3 September 2026 · Scheduled 11:20–11:55 · In the recording 00:42:33–01:09:41

An English deck and the text under the slides

These slides are an English translation of the Russian deck shown in the recording; the Russian original is on the RU version of this page. Under each slide its text is set out — for word search and for machine reading. It is recognised automatically from the same image shown above: small text inside screenshots is not always recognised, so check anything doubtful against the slide itself.

  1. Slide 1 — Using SQLite database journals in the investigation of digital incidents
    Page 100:43:28

    Slide text

    MKO

    SYSTEM

    USING SQLITE DATABASE LOGS IN DIGITAL INCIDENT INVESTIGATIONS

  2. Slide 2 — Using SQLite database journals in the investigation of digital incidents
    Page 200:43:40

    Slide text

    THE SQLITE LOG: THE DATABASE'S "BLACK BOX"

    1

    What databases store

    2 creato no

    database · gone without a trace

    case studies

  3. Slide 3 — Using SQLite database journals in the investigation of digital incidents
    Page 300:44:07

    Slide text

    WHY SQLITE?

    A WIDELY USED EMBEDDED DBMS FOR ANDROID, iOS, macOS,

    WINDOWS AND LINUX

    WHAT DOES IT STORE?

    No separate server required

    Messages

    Location data

    Almost no configuration needed

    Stores data in ordinary files

    Browser history

    Banking app data

    High performance with a small footprint

    18

    Contacts

    & Call logs

    Settings and service data

  4. Slide 4 — Using SQLite database journals in the investigation of digital incidents
    Page 400:45:09

    Slide text

    SQLITE LOGS OFTEN PRESERVE TRACES OF CHANGES EVEN AFTER DATA IS DELETED FROM THE MAIN DATABASE

    1 MESSAGE

    sent

    EDIT

    2

    18:00 → 18:10

    DELETION

    3

    record disappears

    DATABASE.DB

    Final state only

    SQLITE LOGS May retain traces of changes

  5. Slide 5 — Using SQLite database journals in the investigation of digital incidents
    Page 500:45:52

    Slide text

    HOW WAL WORKS: THE LOG FIRST, THE DATABASE SECOND

    APP

    Creates, modifies or

    deletes a record

    DATABASE-WAL Changes are written

    here first

    CHECKPOINT Transfers changes

    DATABASE.DB

    Current state

    DATABASE.DB

    Current data

    DATABASE-WAL

    Change log

    DATABASE-SHM

    Service information

  6. Slide 6 — Using SQLite database journals in the investigation of digital incidents
    Page 600:47:12

    Slide text

    WHAT A WAL FILE MAY CONTAIN

    New records

    Not yet transferred to database.db

    Deleted records

    Traces of objects no longer in the main database

    Previous versions

    Earlier states of modified data

    Temporary states

    Intermediate database states

    Incomplete transactions

    Events that have not reached a checkpoint

  7. Slide 7 — Using SQLite database journals in the investigation of digital incidents
    Page 700:48:07

    Slide text

    A SIMPLE EXAMPLE: ONE MESSAGE,

    THREE STATES IN WAL

    18:00

    1

    Let's meet at 18:00

    2 19:00

    Let's meet at 19:00

    3 DELETE

    Message deleted

  8. Slide 8 — Using SQLite database journals in the investigation of digital incidents
    Page 800:48:28

    Slide text

    THREE INCIDENTS INVOLVING FRAUDULENT LOANS

    Victim

    No.

    Date

    Amount

    Device

    Acquisition method

    Ivanov I.l.

    12.11.2025

    11 000

    Tecno Spark 8C (Teno KG5n)

    Unisoc / Spreadtrum Android

    Petrov P.P.

    13.01.2025

    34 000

    Samsung Galaxy M12 (SM-M127F)

    Full file system

    Sidorov S.S.

    25.01.2026

    23 000

    Realme Note 50 (RMX3834)

    Unisoc / Spreadtrum Android

  9. Slide 9 — Using SQLite database journals in the investigation of digital incidents
    Page 900:50:14

    Slide text

    INCIDENT A:

    "SEARCH BY FULL NAME BP"

  10. Slide 10 — Using SQLite database journals in the investigation of digital incidents
    Page 1000:50:20

    Slide text

    TRACES OF MALWARE

    INCIDENT A

    The SberBank Online

    threats.db-wal log contained a record for

    base.apk, detected by the built-in antivirus as HEUR:Trojan- Dropper. AndroidOS.Hqwar.bk. The file was already absent, but its identifier survived: okkOiikd.q2gdtth.izn110

    Q FOlte Carving Tool

    Analyse

    SOleMactel

    hres inte

    threat type'

    detect. type

    DêuNen/ HEUR Trajay-Dropper AndroidOSHpwr./k",otjectName:/dota/app/+-YR/TPoD18-ci7g67104j460-s/64806kd.#2ydthim110-HigoWWC/

    MONITOR

    er AnsoisOS./ignor./lc: aljectNome/data/Spp/--YR/1P&78-OLZ067/MERG0+/ol/01k @2yie0110-N5@0WCAIWAR

    Cell contents: threat_info.txt - Notepad

    He

    Edel

    Format

    View

    Hep

    app/~-YB31PaDT8-

    o17g67Wjk6Q==/okk@11kd.q2gdtth.izn118-HsgjoÍkVcC5yeL1m8GRTQg+=

    *fileFul1Path":"/data/app/-~YB31PaDT8-

    012g67Wjk6Q::/okk@1ikd.q2gdtth.izn110-

    HsgJoiWcC5yeL1naGRTQg==/base.apk*,"fileHash": nu11, "packageName":

    okke11kd.02gdtth.Jzn118), "severityLeve1": "HIGH", "application"

    :true, "adminThreat": false, "cloudCheckFalled": false)

  11. Slide 11 — Using SQLite database journals in the investigation of digital incidents
    Page 1100:51:04

    Slide text

    CONFIRMING APP INSTALLATION

    INCIDENT A

    No record of

    okkOiikd.q2gdtth.izn110 was found in packages.xml.

    However, the palm-a service log retained its registration event on 12.11.2025 at 04:39:15.

    palm-a - Notepad

    File Edit Format View Help ("currentTime"

    1762922355829 "packageName": "okk@iikd.q2gdtth.izn110"),

    Ln 1, Col 19012

    100%

    Code v5.5

    File

    Tools

    Theme

    Heip

    Time Decoding

    Time Encoding

    Timestamp

    © Unix Millseconds (Java Time) (UTC)

    2025-11-12 04:39:15.8290000 Z

    • Unix Millseconds (Java Time)

    2025-11-1204:39:15.8290000+00:00

    Value Input

    Numeric

    1762922355829

  12. Slide 12 — Using SQLite database journals in the investigation of digital incidents
    Page 1200:51:48

    Slide text

    RECOVERING A DIGITAL FINGERPRINT

    INCIDENT A

    The gass.db system database retained the

    SHA-256 checksum of the

    installation file for the app with identifier

    okkOiikd.q2gdtth.izn110.

    SQLiteStudio (3.1.1) - [app_info (gass)]

    Database

    Structure

    View

    Tools

    Help

    DEKOHH

    Databases

    Contraints

    Data

    Indexes

    Triggers

    DDL

    Structure

    Filter by name

    Grid view

    Form

    gass (SQLite 3)

    O Filter...

    Tables (3)

    ad_attestation

    version_code

    digest_sha256

    _id

    package_name

    pb

    android metadata

    okkOiikd.q2gdtth.izn110

    1202

    tok..

    app_info

  13. Slide 13 — Using SQLite database journals in the investigation of digital incidents
    Page 1300:52:22

    Slide text

    APP CAPABILITIES

    INCIDENT A

    AndroidManifest.xml contained the permissions requested from Android by the app okkOiikd.q2gdtth.izn110:

    Internet access and

    receiving and sending SMS messages.

    File Edit Search Index View Options Help

    Name

    Row

    ~~YB/1PaDT8-olZg67MMjk6Q==-0

    okkOiikd.q2gdtth.izn110 /data/app/- -YBJ1PaDT8-olZg67MMjk6Q==/okk0iikd.q2gdtth.izn110-HsgjoiWVcC5yeLim8GRTQg==/base.apk android.hardware.camera android.hardware camera.autofocus

    android permission.INTERNET android.permission.RECEIVE_SMS android.permission.READ_SMS android.permission. SEND_SMS android.permission WRITE SMS android.permission. RECEIVE_WAP_PUSH android.permission.READ_CELL_BROADCASTS android.permission. RECEIVE _BOOT COMPLETED

  14. Slide 14 — Using SQLite database journals in the investigation of digital incidents
    Page 1400:53:02

    Slide text

    APP DISPLAY NAME

    INCIDENT A

    PhoneHelper.Db established that the app okkOiikd.q2gdtth.izn110 was displayed on the device as "Search by full name BP"

    FQLite Carving Tool

    Analyze

    File

    Export

    Info

    Databases

    All Columns (Filter) ->

    okkOiikd.q2gdtth.izn110

    PhoneHelperDb

    PhGrantTable

    No.

    "pkgName*

    "appName"

    okkOükd.q2gdtth.izn110

    Search by full name BP

  15. Slide 15 — Using SQLite database journals in the investigation of digital incidents
    Page 1500:53:29

    Slide text

    HOW THE APP REACHED THE DEVICE

    INCIDENT A

    Telegram's file_to_path.db database contained a record

    showing that "Search by full name BP.apk" had been received in a chat.

    Design SQL builder SQL Scripting

    file_to_path

    Database Extensions Schema

    Data

    DDL

    paths

    Refresh

    paths by dialog id

    message id

    dialog id

    message_type

    rowid

    path

    (empty)

    Search by full name BPapk

    (empty)

    (empty)

    (empty)

    216652

    2

    1423

    /storage/emulated/0/Android/data/org.telegram.messenger/tiles/ielegram/lelegram Files/Search by full name BPapk

  16. Slide 16 — Using SQLite database journals in the investigation of digital incidents
    Page 1600:54:02

    Slide text

    WHAT THE TELEGRAM CHAT REVEALED

    INCIDENT A

    The Telegram messages_v2 table contained no messages. However, the chats table retained the chat name: "Missing in the special military operation"

    SQLiteStudio (3.1.1) - [chats (cache4)]

    Database

    Tools Help

    Structure View

    Databases

    Filter by name

    chat_settings_v2

    chats

    contacts

    dialog_filter dialog_filter_ep dialog_filter_pin_v2

    Structure

    Data

    Constraints

    Indexes

    Grid view

    Form

    uid

    name

    2

    Missing in the special military operation

  17. Slide 17 — Using SQLite database journals in the investigation of digital incidents
    Page 1700:55:11

    Slide text

    INCIDENT B:

    "PHOTO ARCHIVE (20)"

  18. Slide 18 — Using SQLite database journals in the investigation of digital incidents
    Page 1800:55:17

    Slide text

    TRACES OF MALWARE

    INCIDENT B

    The SberBank Online threats.db-wal log retained a record for base.apk, detected by the built-in

    antivirus as

    HEUR:Trojan- Banker.AndroidOS.Mamont.bc. The file was absent, but the log retained its identifier: com.example.application

    Q Fatite Carving Tool

    Export

    threats.db-wal

    threat info'

    'threat type

    K/bEZCY13w-m/com exapl applicas

    Cell contents: threat_ info.txt - Notepad

    File

    Edit

    Format

    View

    Help

    ("virusName": "HEUR Trojas-

    ndex threats, threat, type threat inlo"

    Banker AndroidOS Mamont be", "objectName":"/data/app/--YNSWYmy02X1tk7hE2cY33w

    /com.examplc.application-

    ț"fileFullPath":"/data/app/——YNSWYnуO¿XШkZhE2cX33

    8WJ34JPXcXcFxl/MA6v35g

    /com.example.apphcation-

    _FREELST

    8Wj34JPXcXcFx1:MA6v35g

    basc.apk"

    "filcHash" mull. "packageNamc" com.example application

    ,"severityl.evel": "HIGH". "applic

    _SQliteMester

    ation"-truc "admin Tlucat" fals

    kFailed" false)

  19. Slide 19 — Using SQLite database journals in the investigation of digital incidents
    Page 1900:55:32

    Slide text

    APP CAPABILITIES

    INCIDENT B

    Analysis of FileLog1.log confirmed that on 13.01.2025 at 05:59:20, the app com.example.application was set as the default SMS application.

    FileLog1.l0g - Notepad

    File Edit Format View

    Help

    25-01-13 05:59:20.444 ORC/CF(15010): getCOA = 0 25-01-13 05:59:20.452 ORC/CF(15010): getCWA = 0 25-01-13 05:59:20.609 SDK/MCS(15010): cmcEnable = false 25-01-13 ORC/DefaultMessageManager(15010): refreshDefaultSmsApp refreshDefaultSmsApp: com.example.application

  20. Slide 20 — Using SQLite database journals in the investigation of digital incidents
    Page 2000:56:01

    Slide text

    CONFIRMING APP REMOVAL

    INCIDENT B

    Analysis of pm_debug_info.txt

    confirmed that

    com.example.application

    was removed on

    31.01.2025 at 17:20:22.

    pm_debug_info.txt - Notepad

    File Edit Format View Help

    2025-01-31 17:20:22.528: START DELETE PACKAGE: observer (98976705)

    pkg {com.example.application), user {0}, caller {10112} flags (2} 2025-01-31 17:20:29.859: Removing prefs while replacing

  21. Slide 21 — Using SQLite database journals in the investigation of digital incidents
    Page 2100:56:19

    Slide text

    DIGITAL FINGERPRINT AND APP NAME SOURCE OF THE APK FILE

    INCIDENT B

    • The gass.db system database retained the SHA-256 checksum of the installation file for com.example.application.

    • The antivirus service database adaptivity.db retained the app display name: "Photo Archive (20)".

    • Telegram's cache4.db contained a record of "Photo Archive (20).apk" being received in a chat.

    SQLiteStudio (3.1.1) - [app_info (gass)]

    Database Structure View Tools Help

    fx

    Databases

    Filter by name

    gass (SQLite 3) • Tables (3)

    1] ad_attestation android_metadata app_info

    Indexes

    Grid view

    Triggers

    Form

    Data

    Constraints

    DDL

    digest_sha256

    id

    pb

    package_name

    version_code

    4152

    1co...

    com.example.application

    SQLiteStudio (3.1.1) - [application_rule (adaptivity)]

    Tools Help

    View

    Database

    Structure

    Databases

    Filter by name

    L adaptivity (SQLite 3)

    Tables (7) android metadata application_rule history room_master_table

    Indexes Triggers

    Grid view

    Form

    Data

    Constraints

    DOL

    packageName

    applicationName

    com.example.application

    Photo Archive (20)

  22. Slide 22 — Using SQLite database journals in the investigation of digital incidents
    Page 2200:56:49

    Slide text

    INCIDENT C:

    "VIDEO.INCIDENT(3)"

  23. Slide 23 — Using SQLite database journals in the investigation of digital incidents
    Page 2300:56:56

    Slide text

    TRACES OF MALWARE

    INCIDENT C

    The virusdetect.db-wal log contained a record for chimera.top.panel, classified by the built-in

    antivirus as Android: Evo-gen [Tril. The log also warned of possible confidential data leakage and fraudulent debits.

    Q FoLite Carving Tool

    File

    Export Analyze

    Info

    # virusdetect.db-wal

    al android metadata

    i apk_cache # infected_app # risk_app

    # room master table

    ! scan_record 1] sqlite_sequence

    All Columns (filtered) -

    No.

    app_identity

    virus detail

    virus_name

    chimera.top.panel Android:Evo-gen [Trj]

    Using this application may result in confidential data leakage and frauduient debits. Immediate removal is recommended.

    Using this application may result in confidential data leakage and fraudulent debits. Immediate removal is recommended.

    chimera.top.panel Android:Evo-gen [Tri

    Cell contents: virus_detail.bxt - Notepad

    File

    Edit Format View Help

    Using this application may result in confidential data leakage and fraudulent debits. Immediate removal is recommended.

  24. Slide 24 — Using SQLite database journals in the investigation of digital incidents
    Page 2400:57:30

    Slide text

    CONFIRMING APP INSTALLATION AND REMOVAL

    INCIDENT C

    • The log-1 file recorded installation of chimera.top.panel on 25.01.2026 at 23:56 and its display name, "video incident(3)".

    • LogToDump.log

    confirmed removal of

    the app on 28.01.2026 at 14:13:30.

    log-1 - Notepad

    File

    Edit

    Format

    View

    Help

    25.01.2026 23:56 SessionCommitReceiver Adding package name to install gueue PiSS nAme AMMen ODIn has app icon: false, has app label: false 25.01.2026 23:56 IteminstallQucue Adding PendinginstallShortcutinfo to queue. Attached info: Workspacciteminfo(id--1 type-APP container-# com android launcher3, logger Launcher Ar

    Containerinfo @ Zbc6f targetComponent Componentinfo (chimera top.panel/) screen--1 cell(-1.-1) span(1.1)

    minSpan(1.1) rank-0 user=Userilandle(0 title=video.incident(3)

    I1769609610986PersistedStoragePackageU/ninstalledReceiver:dReceived android.intent action.PACKAGE FULLY REMOVED for shimera.top.panel for uo

    • DCode v5.5

    Tools

    Theme

    File

    Help

    Tine Decodng

    Time Encoding

    © Unix Milseconds (lava Time)

    ) Unx Maseconds (Java Tire) (ITC)

    2026-01-28 14:13:30.98600002

    Value Input

    Numeric

    1769609610986

  25. Slide 25 — Using SQLite database journals in the investigation of digital incidents
    Page 2500:57:44

    Slide text

    INCIDENT C

    DIGITAL FINGERPRINT AND SOURCE OF THE APK FILE

    • The gass.db system database

    retained the SHA-256 checksum of the installation file for chimera.top.panel.

    ¿ SQLiteStudio (3.1.1) - [app_info (gass)]

    Database Structure View Tools

    Help

    HIRTSRO

    Tables (3) ad_ attestation

    Structure

    Constrainte

    Grid view

    package_name

    version_code

    digest_sha256

    chimera.top.panel

    • Telegram's cache4.db

    recorded receipt of "video.incident(3).apk"

    in the chat identified as "3****" on 25.01.2026 at 15:28:14.

    Fier try name

    Grid view

  26. Slide 26 — Using SQLite database journals in the investigation of digital incidents
    Page 2600:57:59

    Slide text

    WHAT THE INVESTIGATION ESTABLISHED

    PRESENCE OF MALWARE

    INSTALLATION AND

    REMOVAL TIMES

    APP DISPLAY NAME

    SQLITE + SYSTEM

    ARTIFACTS

    SHA-256 FOR IDENTIFICATION

    POTENTIAL CAPABILITIES

    APK

    MALWARE

    SOURCE OF THE APK FILE

    LINKS BETWEEN EVENTS AND DATES OF FRAUD

  27. Slide 27 — Using SQLite database journals in the investigation of digital incidents
    Page 2700:58:45

    Slide text

    THANK YOU

    CONTACTS:

    +7 (495) 909-92-78

    support@mko-systems.ru

    + mko-systems.ru