Tear or Dare Malware

Maybe I’m just bad at disassembly… but I found some startling things in this challenge. And I did NOT write this code.

I attempted the challenge with the decompiler dotPeek, but I moved into Visual Studio to debug the process to see if I could circumvent some of the obfuscation. When I opened it, I found a VERY interesting piece of code shown in these screenshots and this pastebin:

That’s clearly a Windows 7 privilege escalation exploit along with malicious shellcode. I sincerely hope I somehow found my way into random malware on my computer, and not malware embedded in a reversing challenge…

Very interesting.

The code is from this exploit: https://www.exploit-db.com/exploits/40039/

Can you send us back checksums of the file you have? In my decompiler I get the following:

// Decompiled with JetBrains decompiler
// Type: TearORDear.Program
// Assembly: TearORDear, Version=, Culture=neutral, PublicKeyToken=null
// MVID: FAD666A4-4959-43F0-9D38-7FD79F826579
// Assembly location: C:\TearORDear.exe
// Compiler-generated code is shown

using System;
using System.Windows.Forms;

namespace TearORDear
  internal static class Program
    private static void Main()
      Application.Run((Form) new LoginForm());

I get the same thing, the code only showed up when debugging the process. I have a side-by-side picture as well with the JetBrains decompiler and VS: Imgur: The magic of the Internet

SHA-256: D419ADCAEE5D77143E3537F558A6CDDD6BCD7AC9CD6C6783A02B8C67ACBFEA9F

As I see in your screenshot, right side shows on top Program.cs* (Star denoting file was changed).

Furthermore, check line:


It seems to me like you accidentally pasted an exploit there while trying to debug the file :expressionless:

Even if there was malware on the file (that i cannot rule out) It would not be an exact exploitdb copy (including comments!!)

Hashes are correct.

I ran it again, and I did NOT add anything to the code, but it’s still there. I’m talking to Arrexel about it in Discord, but it’s just weird. And I know how this looks, but I swear, I didn’t add anything to the code.

I know you didn’t do it in purpose, what I believe is that you added it by mistake. Did you try opening a new debug instance? Rename the exe to something else and open it again from debugger. Let me know how it goes.

I figured out the problem… It was a combination of user error (me) and Visual Studio having a stupid layout, sorry for the wasted time.

I apologize for any inconvenience I caused the moderators, it was my mistake.

No worries.