Is it possible to unpack a pkg compiled execute?

[Extamov]

No description provided.

[J05HI]

@ExtendLord
I think you can't decompile an exe

[Extamov]

@J05HI It depends

You can decompile a .NET exe

And also you can do the same to executes that were created by pkg.

It is possible to view pkg(exe) files using a hex editor and you will be able to see the source code.

[J05HI]

@ExtendLord
Oh really. I can't see the real source if doing that. Only hex...

[Extamov]

@J05HI If you go to a specific line, you will see the js code(Make sure that you use a hex editor that translate to letters :|)

So the JS is still visible.

You can try to search to get to that section(Where the JS code is).

[J05HI]

@ExtendLord
Which line 😅

[Extamov]

@J05HI You need to find that line, it is different for each pkg(exe)

You can do that by searching(Ctrl+F)

For example search "dependencies": { . (There are more package.json's than one because the modules are also inside the pkg but the first result should be the right json)

The code itself is somewhere around.

[J05HI]

@ExtendLord
Okay thanks! :)

[dcerisano]

Only public package source is included in the binary.

According to issue #194 you need to privatize your package manifest in order prevent your source from being included in the binary.

AFAIK, private packages are stored as tokenized V8 compilations (no source, but stack-tracing is supported).

For extra security maybe also include an obfuscator in your pre-build automation. A pirate would have to be very determined to reverse engineer tokenized obfuscation from a binary.

Also encrypting any included content/media/assets is good practice.

[hipstersmoothie]

Duplicate of #328