Skip to content

Instantly share code, notes, and snippets.

@chowder

chowder/README.md

Last active September 16, 2024 12:13
Show Gist options
  • Save chowder/2ead734d60d84d4d15034fcce81aaaf9 to your computer and use it in GitHub Desktop.
Save chowder/2ead734d60d84d4d15034fcce81aaaf9 to your computer and use it in GitHub Desktop.
Download ZIP
Exporting Microsoft Authenticator TOTP secrets
Raw
README.md

Background

Workplaces may enforce TOTP 2FA to be enabled Office 365 accounts, which require the Microsoft Authenticator app to be installed.

Regular TOTP applications (such as Aegis, Authy, or LastPass) cannot be used as Microsoft uses a proprietary scheme called phonefactor. Furthermore, the application requires Google Services Framework (GSF) to be installed (likely to provide device notifications), and will refuse to work when it is not present on the device.

Forunately, after the registration is complete, the underlying mechanism the app uses to generate TOTP codes is regular otpauth, and its secrets can be exported with a little bit of effort.

Extracting the keys

  1. To extract the keys, a complete registration must first be done with a rooted Android device. I used a virtual Android device created with Android Studio's Device Manager.

  2. Once complete, an SQLite database storing the keys can be found on the device at:

    /data/data/com.azure.authenticator/databases/PhoneFactor

    (accessing the /data partition is what requires root)

  3. ADB can then be used to connect to the device/emulator, using its bundled sqlite3 tool to view the database:

    $ adb root  # Ensure we run as the root user 
$ adb shell  # Launch a shell as the root user 
emu64xa:/ # whoami
root 
emu64xa:/ # sqlite3 /data/data/com.azure.authenticator/databases/PhoneFactor  # Connect to the database file
sqlite> SELECT name, username, oath_secret_key from accounts;
GitHub|Chowder@github.com|w0swofa8wl02vqml0pkbzphvp54zyx5x

    The 32-length string in the oath_secret_key column can then be imported into any TOTP application.

@zsrv
Copy link

zsrv commented May 16, 2024

Thanks for this. My account_type was "2" and I had to construct an otpauth URI that set the algorithm to SHA256:

otpauth://totp/MY_ISSUER:MY_EMAIL?secret=MY_SECRET&algorithm=SHA256

@ChrisIdema
Copy link

ChrisIdema commented Jul 21, 2024 •
edited
Loading

Thank you for this guide. It gave he hope there was a way to export the codes.
I was eventually able to do it, but not exactly this way.

First I needed an emulator image with a play store that was rooted too.
It turned out that the images without play store were rooted by default and the ones with play store are not.
I tried adding a play store to a rooted one, but that failed.
I tried installing the apk image of the MS Authenticator app on an image without play store and that failed.
Eventually I decided to use a non-rooted image and root it using this tool: https://gitlab.com/newbit/rootAVD
That worked and gave me a rooted image with play store that allowed installing the MS Authenticator app.
This was the Pixel_3a with API_33-ext5.

I installed the MS Authenticator app and had to select recover from backup right from the beginning, because you cannot do it afterwards (it will just overwrite a backup instead of syncing). I had to delete my account first (or clear data of the app) in order to see that option again.

I copied the database to a different folder:

cd C:\Users\user\AppData\Local\Android\Sdk\platform-tools
adb shell
su
cat /data/data/com.azure.authenticator/databases/PhoneFactor> /mnt/sdcard/Download/PhoneFactor

But this was not needed.

Then I discovered my image did not come with sqlite3. I tried various ways of installing, but instructions were unclear or outdated.
I ended up installing the app "SQLite Editor" which gave me access to the database.

One code in the database were not base32, but base64. I have to convert it. I used python for that:

a = base64.decodebytes(b'<my base64 code>')
base64.b32encode(a)

This was the entry for the Microsoft account and also the only one with 8 digit code instead of 6.

They were all transferred Aegis which can also import Google Authenticator QR codes directly and can export regular QR codes. Some codes were exported from Aegis to an airgapped hardware TOTP as a backup.

@diffs
Copy link

diffs commented Aug 3, 2024

I was trying to go down the route of intercepting Authenticator's web requests with Fiddler and disabling SSL with Frida to try to get the keys as they're being synced into the emulator.. but turns out this is way easier lol.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment