[-] Failed loading module at /tmp/_MEIlp1XZ1/nxc/modules/wam.py: No module named 'jwt'

[0xGreen]

Describe the bug
Manually compiled the binary from the source code but getting the error: wam.py. No module named 'jwt'

Steps to reproduce the behavior i.e.:

Command: nxc nfs -L

Resulted in:

[-] Failed loading module at /tmp/_MEIlp1XZ1/nxc/modules/wam.py: No module named 'jwt'
LOW PRIVILEGE MODULES

HIGH PRIVILEGE MODULES (requires admin privs)

Expected behavior
Version: 1.3.0 / Codename: NeedForSpeed / Commit : 05ad3c6 works fine.

[Adamkadaban]

jwt is listed as a requirement in pyproject.toml, so this shouldn't be the case.

How did you install it? The precompiled binary works for me and so does installation via pipx

[0xGreen]

I have manually compiled it from the source code (https://www.netexec.wiki/getting-started/installation/manually-building-the-binary).

The precompiled binary works fine for me as well but this binary is from Oct. jwt was added to pyproject.toml last week.

I did see jwt added into pyproject.toml that's why i complied it from the latest source code but it still complains about missing jwt for wam.

[NeffIsBack]

Yep, the stable binaries are only supported on each release.
It is highly recommended to use pipx if you don't really have to use the binaries. However, if you still need to use them, try adding 'jwt' to the spec file, that should resolve at least this import error.

[0xGreen]

Yep, the stable binaries are only supported on each release. It is highly recommended to use pipx if you don't really have to use the binaries. However, if you still need to use them, try adding 'jwt' to the spec file, that should resolve at least this import error.

Thank you!!

Adding jwt and dploot.triage.wam under netexec.spec => hiddenimports worked.

without jwt:

./nxc nfs -L
[-] Failed loading module at /tmp/_MEIA3DpOK/nxc/modules/wam.py: No module named 'jwt'

with jwt but no dploot.triage.wam:

./nxc nfs -L
[-] Failed loading module at /tmp/_MEIA3DpOK/nxc/modules/wam.py: No module named 'dploot.triage.wam'

with jwt and dploot.triage.wam added to netexec.spec

./nxc nfs -L
LOW PRIVILEGE MODULES

HIGH PRIVILEGE MODULES (requires admin privs)

Shouldn't jwt and dploot.triage.wam be added to the source netexec.spec?

My working netexec.spec

hiddenimports=[                                                                                                                                                        
        'aardwolf',                                                                                                                                                         
        'aardwolf.connection',                                                                                                                                              
        .....SNIP.......                                                                                                                                              
        'impacket.tds',                                                                                                                                                     
        'impacket.version',                                                                                                                                                 
        'impacket.ldap.ldap',                                                                                                                                               
        'jwt',  
        'dploot.triage.wam',
        .....SNIP.......                                                                                                                                              

[NeffIsBack]

Yes. Usually we just update the spec files when we do a release and build the binaries or if someone wants to build them manually.

[mpgn]

Feel free to make a quick pr 😄