Octoberfest7 / TeamsPhisher

Send phishing messages and attachments to Microsoft Teams users
998 stars 129 forks source link

Fetching Bearer token for Teams #16

Open Stanitsas opened 1 year ago

Stanitsas commented 1 year ago

Always get the following error message. Tried multiple tenants, any idea?

Fetching Bearer token for Teams............................................[-] AADSTS50034: The user account {EmailHidden} does not exist in the 03ba08ac-c27d-4d87-8d6b-6f3e22c9aXXX directory. To sign into this application, the account must be added to the directory. Trace ID: 3aad7c3f-3d6f-4477-801e-ce719deb5XXX Correlation ID: 813571dc-e6fb-427c-8f53-8179de047XXX

charybe commented 1 year ago

Hi, I fixed this problem by going to my Tenant and creating a new email address to have an email that looks like this: test@MyDomain.onmicrosoft.com

Or if you want to keep your main user you have to go to your Tenant and correct the address so that it gives example: admin@MyDoamine.onmicrosoft.com.

I am stuck on the Skype token part, I have the error: fetching Skype token: 403.

The tool is not well adapted, when I tested with another account I got stuck on Fetching seander info.

Octoberfest7 commented 1 year ago

Always get the following error message. Tried multiple tenants, any idea?

Fetching Bearer token for Teams............................................�[31m[-] AADSTS50034: The user account {EmailHidden} does not exist in the 03ba08ac-c27d-4d87-8d6b-6f3e22c9aXXX directory. To sign into this application, the account must be added to the directory. Trace ID: 3aad7c3f-3d6f-4477-801e-ce719deb5XXX Correlation ID: 813571dc-e6fb-427c-8f53-8179de047XXX

Have you logged into teams/SharePoint with that account the normal way at least once before using teamsphisher?

Stanitsas commented 1 year ago

Always get the following error message. Tried multiple tenants, any idea? Fetching Bearer token for Teams............................................�[31m[-] AADSTS50034: The user account {EmailHidden} does not exist in the 03ba08ac-c27d-4d87-8d6b-6f3e22c9aXXX directory. To sign into this application, the account must be added to the directory. Trace ID: 3aad7c3f-3d6f-4477-801e-ce719deb5XXX Correlation ID: 813571dc-e6fb-427c-8f53-8179de047XXX

Have you logged into teams/SharePoint with that account the normal way at least once before using teamsphisher?

yes, but it didn't do anything

Stanitsas commented 1 year ago

Hi, I fixed this problem by going to my Tenant and creating a new email address to have an email that looks like this: test@MyDomain.onmicrosoft.com

Or if you want to keep your main user you have to go to your Tenant and correct the address so that it gives example: admin@MyDoamine.onmicrosoft.com.

I am stuck on the Skype token part, I have the error: fetching Skype token: 403.

The tool is not well adapted, when I tested with another account I got stuck on Fetching seander info.

also tried with a newly created account; no success

Octoberfest7 commented 1 year ago

Unfortunately not a whole lot I can do to help when I can't replicate the problem on my end. There are a million and one tenant configuration settings and tweaks that could be impacting it

charybe commented 1 year ago

In your Tenant, what does the email address look like, it must be the same when you run the script

Example, if it's just test@MonDomiane.com you have to use it like that on the script without the onmicrosoft.com at the end.

itsmv commented 1 year ago

Hi, I fixed this problem by going to my Tenant and creating a new email address to have an email that looks like this: test@MyDomain.onmicrosoft.com Or if you want to keep your main user you have to go to your Tenant and correct the address so that it gives example: admin@MyDoamine.onmicrosoft.com. I am stuck on the Skype token part, I have the error: fetching Skype token: 403. The tool is not well adapted, when I tested with another account I got stuck on Fetching seander info.

also tried with a newly created account; no success

Did you make any progress on that part? (With the skype token)

leber2 commented 1 year ago

Hi, I fixed this problem by going to my Tenant and creating a new email address to have an email that looks like this: test@MyDomain.onmicrosoft.com Or if you want to keep your main user you have to go to your Tenant and correct the address so that it gives example: admin@MyDoamine.onmicrosoft.com. I am stuck on the Skype token part, I have the error: fetching Skype token: 403. The tool is not well adapted, when I tested with another account I got stuck on Fetching seander info.

also tried with a newly created account; no success

Did you make any progress on that part? (With the skype token)

Any updates on the Skype token error? Having the same issue.

itsmv commented 12 months ago

Hi, I fixed this problem by going to my Tenant and creating a new email address to have an email that looks like this: test@MyDomain.onmicrosoft.com Or if you want to keep your main user you have to go to your Tenant and correct the address so that it gives example: admin@MyDoamine.onmicrosoft.com. I am stuck on the Skype token part, I have the error: fetching Skype token: 403. The tool is not well adapted, when I tested with another account I got stuck on Fetching seander info.

also tried with a newly created account; no success

Did you make any progress on that part? (With the skype token)

Any updates on the Skype token error? Having the same issue.

I now have the suspicion (after further investigation) that there is a problem with my Teams Licence. Do you have a valid Teams Licence on the account you are using for the Phisher @leber2 ?

kpomeroy1979 commented 11 months ago

I was able to address this by using the -s parameter and specifying the tenant name. I also just used username@domain.com and not @domain.onmicrosoft.com in for the -u parameter. I got all the way to "uploading file" but received the error "Error Uploading File: 401" so obviously permission denied but not sure where.

Freccia commented 10 months ago

I had the same Skype token error and I solved by getting a Microsoft 365 trial license, then I added the license to the user I used for the test.

loulax commented 10 months ago

Hi, i have an issue to retrieve the tokens too. The script fails at this point, perhaps it caused due to the mfa activated on my account admin@mydomain.onmicrosoft.com ?