├── README.md ├── antispam_device.md └── mssdk.md /README.md: -------------------------------------------------------------------------------- 1 | # xlog, ttencrypt/applog, mssdk (info) 2 | # All files written in python 3 | xlog api fully decrypted from TIKTOK/DOUYIN 4 | People are selling xlog for ridiculous prices please be careful as this api can be blocked any time by the backend engineers themselves 5 | 6 | Do not pay over price somewhere else! 7 | #You need to have gorgon/khronos algorithm for ttencrypt 8 | + only accepting bitcoin from now 9 | + $50 usd, for gorgon,khronos (algorithmic generation due to how it is stored in the data when sending a request) 10 | + $50 usd, xlog/encryption/decryption (can be blocked anytime!!) 11 | + $50 usd, applog/ttencrypt utils (will always be up to date) 12 | + $25 usd for automatically generating devices params (if needed) 13 | proof can be shown below 14 | 15 | These files mean that these files are only for educational purposes only! any other use is not my concern! 16 | add me on telegram 17 | https://t.me/Yengchipi 18 | 19 | #XLOG ACTIVATION BELOW 20 | 21 | 22 | ![xlog](https://user-images.githubusercontent.com/111660587/185773160-f87825d7-5f7b-46b8-945c-a19604e8c161.png) 23 | 24 | ![device generation](https://user-images.githubusercontent.com/111660587/185766158-7000cb13-72d3-46f4-b157-bc4ea347d77c.png) 25 | ![device validation process](https://user-images.githubusercontent.com/111660587/185766151-b1efa06c-a2fd-45c4-8c1c-8e33c4465394.png) 26 | ![khronosgorgon](https://user-images.githubusercontent.com/111660587/185766153-aaa126b9-2aec-42dc-bc46-9a0dbee2a1bb.png) 27 | ![validated](https://user-images.githubusercontent.com/111660587/185766566-0691c781-ab97-48aa-926b-8447234f9bc2.png) 28 | -------------------------------------------------------------------------------- /antispam_device.md: -------------------------------------------------------------------------------- 1 | since xlog validates device so you can use more functions for the device such as logging in, liking,commenting, etc... 2 | We can also make the device so the device doesnt get blocked after a certain period 3 | We do not have to use xlog 4 | 5 | 6 | ![anti_spam](https://user-images.githubusercontent.com/111660587/186225654-ec836c4d-05a9-4d69-af17-0bded9ba12a0.png) 7 | 8 | parameters to generate are as,cp,mas 9 | are needed 10 | -------------------------------------------------------------------------------- /mssdk.md: -------------------------------------------------------------------------------- 1 | we will be doing some analysis here with updates 2 | 3 | Newest douyin/tiktok encryption for validating devices... 4 | Necessary for new devices being validated through newest apk version 5 | Can be encrypted/decrypted. 6 | mssdk 7 | 8 | ![MSSDK_ENDPOINT](https://user-images.githubusercontent.com/111660587/187089624-ced03b4f-6717-45c1-b893-07263e0f9cb9.png) 9 | 10 | 11 | Encryption in hex format... 12 | 13 | 14 | ![HEX](https://user-images.githubusercontent.com/111660587/187089684-158fd031-7736-4388-8424-de85b8e1c279.png) 15 | 16 | 17 | we can inject straight into some dynamic library / shared object 18 | 19 | first decompile latest tiktok apk using jadx 20 | 21 | after searching around for a bit we stumble upon hashmap values... 22 | in function LIZIZ() mostly obfuscated funcs to prevent snooping. 23 | 24 | ![dbebada1bc4f3a49cff69206628a7da9](https://user-images.githubusercontent.com/111660587/187262250-bfa4db7d-a630-45d1-bca0-5833419d0681.png) 25 | 26 | #investigating web mssdk encryption we see that the response is base64 encoded 27 | 28 | #we will investigate in depth both encryptions should be the same 29 | 30 | ![mssdk web](https://user-images.githubusercontent.com/111660587/187497024-570d0c51-bfdd-4951-97a1-5c64aeb02164.png) 31 | 32 | After going through many requests in web we sift through some js files and we have found obfuscated functions 33 | 34 | or follow this link and inspect source 35 | https://sf16-secsdk.ttwstatic.com/obj/rc-web-sdk-gcs/webmssdk/1.0.0.412/webmssdk.js 36 | 37 | 38 | After looking at each function we can see this from this file in formatted version... 39 | 40 | 41 | Time to go through each obfuscated function one by one this can be the confusing/tricky part but it can be done through this file... 42 | ![mssdk obfuscation](https://user-images.githubusercontent.com/111660587/187560756-0143d37a-a15d-489a-97f1-13808f9f545f.png) 43 | 44 | 45 | we take a look at some functions in this file... and found 46 | ![js file mssdk](https://user-images.githubusercontent.com/111660587/187560875-52e37b7e-ddd8-4aa5-9efb-c308bec9cdb6.png) 47 | 48 | 49 | Try and follow the obfuscated function...no more updates for now.... 50 | 51 | 52 | 53 | 54 | --------------------------------------------------------------------------------