Jump to content
Tuts 4 You

Obsidium v1.6.9


CodeExplorer

Recommended Posts

CodeExplorer

Obsidium v1.6.9


This is just one of my program protected
The objective is unpack it.
 


  • Submitter
    CodeExplorer
  • Submitted
    08/09/2024
  • Category

 

Link to comment
Share on other sites

  • The title was changed to Obsidium v1.6.9
jackyjask

@CodeExplorer  the GUI opens up for a second then app exits

is it expected?

 

hold on, its crashing... dozens of crash dump after each run - 

image.png.88bd8a3c4628bd11fb29a3dade302700.png

image.png.83d641f40de53747b7a546cce00c4111.png

  • Like 1
Link to comment
Share on other sites

CodeExplorer
Posted (edited)
2 minutes ago, jackyjask said:

@CodeExplorer  the GUI opens up for a second then app exits

is it expected?

 

Notice the same thing in my computer. This comes after protecting the exe: a protection bug.
Hopefully can be solved after unpacking.
 

Edited by CodeExplorer
  • Like 1
  • Haha 1
Link to comment
Share on other sites

  • 4 weeks later...
CodeExplorer

Added WINENUM.zip to "Obsidium v1.6.9" - a file which is full working.
but now I can't even hide my debugger from Obsidium, the process exist after some time.
 

Edited by CodeExplorer
  • Like 1
Link to comment
Share on other sites

jackyjask

what is the issue with winenum protected binary?

confirming - I"m able to run it and it doesn't crash as previous protected one,

also seems no any new anti-dbg used, all as usually - 

 you could see in Logs window that it is contantly doing some anti-dbg crap ;)

 

image.png

Link to comment
Share on other sites

CodeExplorer
1 hour ago, jackyjask said:

what is the issue with winenum protected binary?

There is no issue, just that I can't debug properly. It exist after some time while debugging that file.
 

Link to comment
Share on other sites

TRISTAN Pro
16 hours ago, jackyjask said:

what is the issue with winenum protected binary?

confirming - I"m able to run it and it doesn't crash as previous protected one,

also seems no any new anti-dbg used, all as usually - 

 you could see in Logs window that it is contantly doing some anti-dbg crap ;)

 

image.png

Like this one 

It can be debugged and unpacked easily.

So there are no antidebugger .

we can enable drx and debugge it as normal app.

 

Annotation.png

Edited by TRISTAN Pro
  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...