mythicagents / atlas Goto Github PK

Atlas is a .NET 3.5 and .NET 4.0 compatible agent that is designed as an initial payload offering only the bare essentials before loading upa more fully-featured agent. This payload is updated for Mythic 2.2 and will update as necessary. It is not compatible with Mythic 2.1 and below.

s/b

Atlas is a .NET 3.5 and .NET 4.0 compatible agent that is designed as an initial payload offering only the bare essentials before loading up a more fully-featured agent. This payload is updated for Mythic 2.2 and will update as necessary. It is not compatible with Mythic 2.1 and below.

I am not sure if I insert the issue in the right place. I have installed latest mythic with HTTP C2 profile and Atlas. When running Atlas I see that it called back, but right after the initial reply I get errors in mythic server:

[ERROR] crypto.py: MAC check failed
Traceback (most recent call last):
  File "/Mythic/app/crypto.py", line 52, in decrypt_message
    decrypted = await decrypt_AES256(
  File "/Mythic/app/crypto.py", line 127, in decrypt_AES256
    h.verify(mac)
  File "/usr/local/lib/python3.8/site-packages/Crypto/Hash/HMAC.py", line 165, in verify
    raise ValueError("MAC check failed")
Value Error: MAC check failed

so Atlas tries to call back, but the message is not understood, not sure why.

Hello,

I'm actually using Mythic C2 and try to use Atlas agent. My infrastructure involve "Caddy2" server for redirectors, this solution doesn't accept anymore TLSv1 / 1.1 for security reason (as mention here : https://stackoverflow.com/a/65018830)
Apollo agent can use TLS1.2 and it's working fine with this configuration.

Here a sample of Atlas TLS traffic with the version used in wireshark :

Is there a way to configure TLS version in Atlas agent ? I tried to "diff" Atlas and Apollo code, but they are very different.

Thanks a lot

Seems that upload command is not working!
When i issue upload command its freeze agent and seems that agent disconnects as no callbacks is made! From proccess hacker on windows machine i can see that proccess is running but no callbacks made! Command itself does not produce any error output and agent built itself works fine