// HackTheBox  ·  writeup

RomCom

HackTheBox Very Easy MFTECmdqemu-img7-ZipPython
DFIR

Scenario

In this Sherlock, Players will analyze a system that was the target of an exploit in the Winrar application and was abused by groups like RomCom and Paper WereWolf in 2025.

Executive Summary

A user opened a booby-trapped RAR archive that exploited a WinRAR path traversal flaw, the same bug RomCom and Paper Werewolf used in 2025. Within about fourteen seconds of the archive opening, the exploit wrote a decoy document next to the archive, a backdoor into the user’s local AppData, and a shortcut into the Startup folder so the backdoor would relaunch at every logon. The user then opened the decoy, believing it was a legitimate lab result, while the backdoor was already in place. The only evidence is the NTFS $MFT and $J journal, so the whole chain is rebuilt from creation timestamps and USN records; no file contents are available.

Artifacts

Gotcha: 7-Zip extracts 0 bytes from the VHDX, so convert it with qemu-img instead. The NTFS boot sector inside has a zeroed jump field, so neither 7-Zip nor ntfs-3g will mount the partition. Walk the $MFT data runs yourself to carve out $MFT and $J.

Timestamp note: Answers need YYYY-MM-DD hh:mm:ss, so drop the fractional seconds from the MFT and USN values.

qemu-img convert -O raw evidence.vhdx work/disk.raw
MFTECmd -f MFT_C.bin --csv work --csvf mftc.csv
MFTECmd -f J_C.bin --csv work --csvf j.csv

Initial Access

Q1 — What is the CVE assigned to the WinRAR vulnerability exploited by the RomCom threat group in 2025?

Reference lookup, no evidence needed. ESET’s research on RomCom and others exploiting a WinRAR zero-day in 2025 (welivesecurity.com) names the CVE.

Click flag to reveal CVE-2025-8088
Q2 — What is the nature of this vulnerability?

Same ESET article. The flaw abuses NTFS alternate data streams in archive entry names so files are extracted to an attacker-chosen path instead of the folder the user picked, which is what lets the payloads land in Startup and AppData.

Click to reveal answer Path Traversal
Q3 — What is the name of the archive file under Susan's documents folder that exploits the vulnerability upon opening the archive file?

Search the parsed $MFT for .rar entries under Susan’s profile. Only one archive sits in \Users\susan\Documents (MFT entry 117119), and its name reads like a lure aimed at a medical or lab worker.

grep -i 'susan' work/mftc.csv | grep -i '\.rar'
Click flag to reveal Pathology-Department-Research-Records.rar
Q4 — When was the archive file created on the disk?

From Q3, take entry 117119 and read the $STANDARD_INFORMATION created time (Created0x10 in the MFTECmd output). It reads 08:13:50.519; truncate to the second.

grep 'Pathology-Department-Research-Records.rar' work/mftc.csv
Click to reveal answer 2025-09-02 08:13:50

Execution

Q5 — When was the archive file opened?

Opening a file makes Explorer drop a shortcut in the user’s Recent items. Look for the Recent LNK named after the archive in Susan’s profile; its creation time is the first open. It lands at 08:14:04.996, about 14 seconds after the archive hit the disk.

grep -i 'Recent' work/mftc.csv | grep 'Pathology-Department-Research-Records'
Click flag to reveal 2025-09-02 08:14:04
Q6 — What is the name of the decoy document extracted from the archive file, meant to appear legitimate and distract the user?

Filter the USN journal for FileCreate records in the seconds after the Q5 open. A PDF appears in Susan’s Documents folder at 08:14:18.79, a burst that only an extraction could produce. Its name fits the lure from Q3.

grep FileCreate work/j.csv | grep '2025-09-02 08:14:1'
Click to reveal answer Genotyping_Results_B57_Positive.pdf
Q10 — When was the decoy document opened by the end user, thinking it to be a legitimate document?

Same Recent items trick as Q5, this time for the decoy from Q6. The LNK for the PDF was created at 08:15:05.61, about 47 seconds after the PDF was dropped. The backdoor had been in place for most of a minute by then.

grep -i 'Recent' work/mftc.csv | grep 'Genotyping_Results_B57_Positive'
Click to reveal answer 2025-09-02 08:15:05
Q7 — What is the name and path of the actual backdoor executable dropped by the archive file?

Same USN window as Q6. An executable is created under \Users\susan\AppData\Local at 08:14:18.85, a few hundredths of a second after the decoy. Nothing else in that burst is an executable, and the evidence holds no file contents, so the attribution rests on timing and location rather than analysis of the binary. The directory is a classic spot for a user-writable implant, and the name imitates a helper process.

grep FileCreate work/j.csv | grep -i '\.exe'
Click flag to reveal C:\Users\susan\AppData\Local\ApbxHelper.exe

Persistence

Q8 — The exploit also drops a file to facilitate the persistence and execution of the backdoor. What is the path and name of this file?

Search the $MFT for anything under Susan’s Start Menu\Programs\Startup folder. A single .lnk with a harmless name (MFT entry 117404) sits there, created inside the same burst as the backdoor from Q7. Anything in Startup runs at logon, so the shortcut relaunches the backdoor.

grep -i 'Startup' work/mftc.csv | grep -i 'susan'
Click to reveal answer C:\Users\susan\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\Display Settings.lnk
Q9 — What is the associated MITRE Technique ID discussed in the previous question?

Reference lookup against ATT&CK, no evidence needed. A shortcut planted to run at logon maps to the shortcut-specific sub-technique under Boot or Logon Autostart Execution.

Gotcha: The generic Startup folder sub-technique (T1547.001) is the obvious pick and it is wrong here. The file is a .lnk, so the shortcut sub-technique is the one that matches.

Click flag to reveal T1547.009

Attack Summary

PhaseAction
Initial AccessSusan receives Pathology-Department-Research-Records.rar and it lands in her Documents folder
ExecutionArchive opened in WinRAR; the path traversal flaw fires
ExecutionDecoy PDF extracted beside the archive
ExecutionBackdoor ApbxHelper.exe written to AppData\Local
PersistenceDisplay Settings.lnk written to the Startup folder
ExecutionUser opens the decoy PDF, unaware of the backdoor

Forensic Timeline

TimestampEvent
2025-09-02 08:13:50Pathology-Department-Research-Records.rar created on disk
2025-09-02 08:14:04Recent items LNK for the archive created (archive opened)
2025-09-02 08:14:18.79Decoy PDF created in Documents
2025-09-02 08:14:18.85ApbxHelper.exe created in AppData\Local
2025-09-02 08:15:05Recent items LNK for the decoy created (decoy opened)

IOCs

TypeValue
File (archive)C:\Users\susan\Documents\Pathology-Department-Research-Records.rar
File (decoy)C:\Users\susan\Documents\Genotyping_Results_B57_Positive.pdf
File (backdoor)C:\Users\susan\AppData\Local\ApbxHelper.exe
File (persistence)C:\Users\susan\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\Display Settings.lnk
CVECVE-2025-8088

MITRE ATT&CK

TechniqueIDDescription
Exploitation for Client ExecutionT1203WinRAR path traversal (CVE-2025-8088) triggered by opening the archive
User Execution: Malicious FileT1204.002Archive and decoy PDF opened by the user
Ingress Tool TransferT1105ApbxHelper.exe written to the user’s AppData\Local folder
Boot or Logon Autostart Execution: Shortcut ModificationT1547.009Display Settings.lnk in the Startup folder

Defender Takeaways

Patch WinRAR. CVE-2025-8088 needs nothing more than the user opening an archive, and the fixed release closes the traversal. Archive tools rarely sit in patch-management scope, so they stay vulnerable long after the OS is current.

Alert on executables and shortcuts written to AppData and Startup right after an archive is opened. Here the archive open, the backdoor and the persistence shortcut all happened within about 15 seconds. A rule that correlates an archiver process with file creates in those paths catches it.

Watch the Startup folder. A .lnk named Display Settings is easy to miss by eye. New files under Start Menu\Programs\Startup are rare enough to alert on directly.

Keep $MFT and $J in triage collections. With no other artifacts, creation times and the USN journal were enough to rebuild the full timeline. They are small, and they survive when LNKs and prefetch are not collected.

Conclusion

A single archive open gave the actor a backdoor and logon persistence with no further user action, and the decoy PDF hid it by giving the user something to read. Filesystem metadata alone was enough to reconstruct the whole chain, which makes new-file monitoring in AppData and Startup the cheapest detection for this exploit.