VP-06 · Computer and disk forensics

Ransomware on an accounting workstation: from an attachment to 295 locked files

2,276 rows of the USN change journal, Sysmon, the Security log, Microsoft Defender events, a mail gateway log in local time and the ransom note. Sixteen questions lead from a disk-image attachment to the shortcut that started the chain, the antivirus detection that did not stop it, the elevation, the deleted shadow copies, the count of encrypted files and what the workstation cannot say about the shared folder.

Synthetic training data. The organisation, people, devices, serial numbers and times are invented.

01Brief

Kuzey Lojistik A.S. runs a Windows 11 accounting workstation, KZL-MUH07 (192.0.2.57), used by d.ercan, who is also a member of the local Administrators group. On Tuesday 16 June 2026, back from lunch, the user found a new wallpaper, a note called OKU_BENI.txt on the desktop and documents whose names ended in .kilit, and called the IT desk at 10:21 UTC. IT disabled the workstation's switch port at 10:27 UTC. An incident response examiner collected the files in this pack the same afternoon, before the workstation was shut down for imaging. The mail gateway log was exported separately and is in local time.

Internal audit asks:

  1. How did the chain start, when, and is anyone else exposed to the same attachment?
  2. Why did the antivirus not stop the encryption, and how did the tool get administrator rights?
  3. What was encrypted on this computer, by which process, over what period, and what can be said about the share?

Answer from the files only. Name accounts, addresses, hosts, files and processes; do not name people or a criminal group. The file server KZL-FS02 and the share \\KZL-FS02\Muhasebe were not collected: say what this workstation shows about them and stop there.

02Evidence files

FileContentsSHA-256
README.txtScenario and file listThe brief in English and Turkish, the rules and the file list.bcc4f780cf7b8ac36feca1acb4effa300f488da72b43366b88d86b3a577d5f58
acquisition-log.txtCollection logWhat was collected, when and how, when the network port was disabled, and the clock check of each source.aa6d2ae60cd81dc62c563791f3e87bcde04c146a45c3953a9495a97296821622
export-metadata.txtExport parametersWindow, row count, time basis and scope of the six exports, and what the pack does not contain.404b498924ad3fccd7a5693f7e4057b5149883fd68cf6fd5e38e073d847b46f3
usn-journal.csvUSN change journal2,276 rows of $UsnJrnl:$J of C: in UTC: Prefetch, browser cache, Outlook and Office saves around the encryption burst. $UsnJrnl:$J (USN change journal) →19403d7026f18684b4acfa25ba880c3b03710a51085027ab135a6ba957996a4b
sysmon-events.csvSysmon eventsProcess creation, network connection, file creation and registry events, with integrity level and logon ID, in UTC. Windows XML Event Log (EVTX) →1efc9a0b5cd550a94f834e52014aed86b1017148caf048d63fefa8acc3f9dfbe
security-events.csvSecurity eventsThe user's sign-in with two linked logon IDs, workstation lock and unlock, service and management logons, in UTC. Windows XML Event Log (EVTX) →efe52646afb94591e6cee4dccc5ec2730a077bc83bd9f01d536e2338a9e24e04
defender-events.csvMicrosoft Defender eventsDetection, quarantine, configuration change and real-time protection events of Microsoft Defender Antivirus, in UTC. Windows XML Event Log (EVTX) →389fcac5ce97e81aa529268c9e798670e70af885dd329a5bc2a86a5bbc8e2a7f
mail-gateway.csvMail gateway message logEvery message to or from the company that day, with attachment name and SHA-256, in LOCAL time (UTC+3). E-mail header fields (Received, Date, From, Message-ID) →9332c6b039588197c95a7ee10f3df14b6a7fde65a99d6f35014e7b1400127249
OKU_BENI.txtRansom noteThe note copied from the desktop. Its deadline is written in local time.22f715a2dcd283c5dbf0caef8006400ad3e65297e36381e0495388b817228547
manifest.txtHash manifestSHA-256 of every file above except itself. Verify before you start.(the manifest itself)

The hashes above are copied from manifest.txt. Recompute them yourself, for example with the hash tool or sha256sum.

You can also examine these files on the examination workbench: hashes, one UTC timeline, sessions and a findings draft in the browser.

03Before you start

  • Verify every file against manifest.txt and write the result in your examination log before you read anything else.
  • Write the time basis next to every time you copy out. The mail gateway and the ransom note are local time; everything else is UTC.
  • Count files, not rows. Write the filter you used next to every number.
  • The USN journal says what changed, not who changed it. Tie a change to a process only through another source.

Keep your notes in F-02 Evidence intake form and F-04 Examination log.

04Questions

Answer from the files only. Each answer is checked in this browser; nothing is sent anywhere, and your answers are kept on this device until you clear them. 16 questions, 26 points.

  1. Q011 pointusn-journal.csvmanifest.txt

    8 hex characters

  2. Q022 pointsmail-gateway.csvusn-journal.csv

    YYYY-MM-DD HH:MM:SS, UTC

  3. Q031 pointmail-gateway.csv

    A whole number

  4. Q041 pointsysmon-events.csv

    An IPv4 address

  5. Q052 pointsdefender-events.csvsysmon-events.csv

    YYYY-MM-DD HH:MM:SS, UTC

  6. Q062 pointsdefender-events.csvsysmon-events.csvusn-journal.csv

    Defender detected and quarantined a ransomware file at 09:20. Why did encryption still begin twenty minutes later?

  7. Q071 pointsysmon-events.csv

    A full Windows path

  8. Q082 pointssysmon-events.csvsecurity-events.csv

    The implant ran at Medium integrity, but vssadmin.exe and igfx.exe ran at High. Which reading do the files support?

  9. Q091 pointsysmon-events.csv

    A file name, e.g. program.exe

  10. Q102 pointsusn-journal.csv

    YYYY-MM-DD HH:MM:SS, UTC

  11. Q112 pointsusn-journal.csv

    A whole number

  12. Q121 pointusn-journal.csvsysmon-events.csv

    A whole number

  13. Q132 pointsusn-journal.csvsysmon-events.csv

    The USN journal does not record which process made a change. What ties the .kilit renames to igfx.exe?

  14. Q142 pointssysmon-events.csvusn-journal.csv

    A whole number of minutes

  15. Q152 pointssysmon-events.csvexport-metadata.txtOKU_BENI.txt

    The note says files on connected shares were encrypted too. What can this pack say about \\KZL-FS02\Muhasebe?

  16. Q162 pointsusn-journal.csvsysmon-events.csvsecurity-events.csvdefender-events.csvmail-gateway.csv

    Which sentence could the examiner sign from these files alone?

Score 0 / 26

05Your finding

Last step: write one paragraph that answers the three audit questions as a finding. Your instructor marks it against four criteria:

  • Every time carries its basis; the gateway time and the note's deadline are converted from local time.
  • Files are counted, not rows, and Excel's own renames are kept out of the count.
  • The link between the journal and the process is stated as an inference from timing and Sysmon, not as something the journal shows.
  • The report says the protection was switched off, names how, and does not call it a detection failure.
  • The report names the three other mailboxes and asks for the file server to be examined.

How findings are phrased →

Contact and service requests

Contact us about examination services related to this page, support for expert witnesses, or collaboration. Please do not attach evidence files or personal data to your email.

Contact page →